Your SICK ID gives you access to our extensive range of services. This includes direct online orders, price and availability checks, and access to our digital services.
During the upgrade from version 1.3.3 to 1.3.4, customers encountering installation issues. This document outlines the probable cause, background context, and recommended resolution steps.
Issue Description
While performing the upgrade, the installer failed due to inconsistencies in existing installer metadata. This prevented the upgrade process from completing successfully.
Root Cause
The issue is primarily caused by residual or corrupted ZeroG installer metadata from previous installations or uninstallations. These remnants may occur due to:
- Incomplete or failed previous installations - Improper or partial uninstallations - Corruption in ZeroG registry structure
The installer assumes that previous install/uninstall processes completed successfully. When this assumption fails, upgrade operations may encounter conflicts or incorrect state references.
Known Limitation
This behavior is a known limitation of the current installer framework. The installer relies on the integrity of existing metadata.
Resolution / Workaround
The issue can be resolved by removing the existing ZeroG installer metadata and allowing the installer to recreate it.
Note: The folder is hidden by default. User need to turn on “Show hidden folder” on windows
Follow the steps below:
Take Backup of ZeroG Installer Metadata - Navigate to: C:\Program Files (x86)\Zero G Registry (path may vary depending on system architecture). - If the folder exists, take a complete backup. - Example backup location: C:\Backup\ZeroG_Backup
Delete Existing Metadata - Delete the folder: C:\Program Files (x86)\Zero G Registry
Re-run the Patch Installer - Right-click on the 1.3.4 installer - Select: Run as Administrator - The installer will recreate fresh metadata and proceed normally
Important Notes
- This workaround is most reliable when the application was installed using default installation paths.
- If the application was installed in a custom directory, removing metadata may cause the installer to lose track of the original installation location.
- In such cases, the installer may attempt to install or repair components in the default path instead of the actual installation directory.
