Updating

6.6 Updating

6.6.1 Preparation

Read release notes and confirm supported versions, installation target, maintenance window, and affected clients. Record both applications' versions and layout state and create verified database/configuration backups. Updating is not backup or business acceptance.

Stop/finish printing, writing, imports, and photo batches; disable automatic output and reconcile submitted Windows jobs. Prepare authorized installer access. Never overwrite runtime DLLs while users work.

6.6.2 Check, Download, Save, and Close

Use the normal Check for Updates entry and the official signed EXE installer, not unknown archives or assembled files.

1. Confirm release, target directory, and maintenance approval.
2. Download and wait for integrity verification; preserve failure messages and do not run rejected files manually.
3. The updater requests normal save/closure from CDPS/COC in the target directory. Save each window and accept only when ready.
4. If any window cancels, remains open, or times out, resolve it normally or cancel the update, not by discarding work through forced termination.
5. After closure, continue in the launched installer.

Other installation roots are not necessarily targets, but shared business effects still matter. Download cancellation does not uninstall the product. Handle trusted Windows elevation prompts locally.

6.6.3 Installation and Acceptance

The installer handles directory, upgrade relationships, permissions, data preservation, and result. Confirm the original target rather than accidentally creating another copy while shortcuts still launch the old one. Follow required restart prompts.

The updater exits after handing off to the installer. This is not proof of successful installation. Wait for explicit completion and do not clean its temporary files or reopen products mid-install.

Then check both versions in About, license/login, defaults, data, photos, personal settings, and approved sample writes/output. A newer version number without usable database/devices is not accepted completion.

6.6.4 Failure, Cancellation, and Recovery

Do not copy old EXEs/DLLs over a new release, especially after schema changes. A rollback needs compatible program/configuration/data and approval for any lost changes. Historical .CREVIAUpdate.recovery markers require completing the old transaction under support guidance, not deletion. The current EXE workflow does not imply a general-purpose automatic ZIP rollback backup.

After interruption, check for an existing installer/prompt before starting another. Record stage/full error. Before installation, cancellation may leave old programs usable; after handoff, do not assume intact old files. Wait for installer rollback/restart, then compare both versions. If programs start but business fails, keep automatic work off and inspect defaults/paths/photos/devices before restoring old personnel data. If versions are mixed or startup fails, preserve evidence/backups and use official complete repair. For approved downgrade, retain post-upgrade business changes, check schema compatibility, and reconcile physical issuance before any data rollback.

Without a validated compatible recovery point, stop overwriting and submit 6.7 evidence rather than trying multiple packages or bypassing protection.

6.6.5 Staged Client Updates

Pilot a noncritical station through login/data/photo/permission/layout/device checks, then update during maintenance in recorded batches. Coordinate shared schema/interface compatibility before mixing versions. Enable automatic work only after all affected stations pass; retain the pre-upgrade point through the observation period.