Use the approved 4.1.0 installer for your edition and confirm the version shown in the installed application. Published package availability is shown in Downloads & beta access.
Prepare a recovery set
Record the current server/client build, enabled frameworks, database endpoint and service settings. Take a consistent database backup together with application-managed evidence, reports, configuration and protected key material. Check that the backup can be read and restored in an isolated approved environment. Preserve the previous installer and its documentation.
Upgrade the server
Use the approved Server Setup workflow and verify that it identifies the intended existing installation. Review the saved database/network selections before proceeding. The managed-database adoption checks must not silently take ownership of an unrelated PostgreSQL installation. Keep installation and validation logs when a stage fails; do not delete existing data to force completion.
Publish Windows client updates
In Server Administration > Client Updates, select the genuine platform package, enter its four-part file version and publish it. The server records package size and SHA-256 and exposes an authenticated catalog/download path. Update-aware Windows clients compare versions and verify both recorded size and hash before offering the package.
Compatible older API 8 clients may remain able to connect, but clients built before the update feature cannot display an update prompt they do not implement. The update catalog can hold a macOS package; this does not mean a macOS client is included in 4.1.0.
Validate after the upgrade
Confirm server/API health, database access, stored clients/programs, license status, evidence access, current connection security, pilot collection and exported reports. Compare the installed version with the selected package. Test on the Windows hosts that will run the product; a build result alone does not verify an installation.
Recovery and cleanup
Roll back with the matching software, data and protected keys if an approved recovery is necessary. Use Preview Cleanup before Safe Cleanup. Respect legal holds and retention decisions. Keep audit records of removals and do not treat cleanup as database repair.