Frequently Asked Question

Current CICB releases do not use the legacy Updater.ps1 and shared-drive package workflow.

Standard Connected Configuration: start the signed CICB AppUpdater from the Client or Server Check Update action. Confirm that the installed app_updater/AppUpdater.exe package is present, has a valid ARKSOFT INC signature, and can reach the approved GitHub release endpoints. Close CICB applications when prompted and run the installer with the permissions required by your organization.

Air-Gapped Isolated LAN: do not enable the online updater. Import an approved local EXE or MSI with install-airgap-update.ps1, the independently supplied SHA-256 digest, and a valid ARKSOFT INC Authenticode signature.

If the upgrade still fails, collect a CICB Diagnostics package and include the installer type, current version, target version, and failure time in a support ticket. Do not include license files, private keys, databases, or credentials.