Frequently Asked Question

Current CICB releases use a signed installer workflow rather than the legacy server-update script.

Standard Connected Configuration: start the signed CICB AppUpdater from the Server Check Update action. Verify that app_updater/AppUpdater.exe is present and signed by ARKSOFT INC, that approved GitHub release endpoints are reachable, and that the operator has permission to stop CICB processes and install software.

Air-Gapped Isolated LAN: transfer an approved local EXE or MSI through the organization's offline process and verify it with install-airgap-update.ps1, the expected SHA-256 digest, and the ARKSOFT INC publisher signature. The Server does not require public Internet access for this path.

After upgrade, verify the installed version, signatures, required runtime files, service or startup state, listener, and Client connectivity. If validation fails, collect a privacy-safe CICB Diagnostics package for support.