Updates: back up, verify, install, then check
Update Center verifies and installs the package. You take the backup first, read the verification result before you approve the install, and check the system once the service is back. Only an Owner on a writable license can start the install.
- Managed package
- VaultPilot Windows MSI
- Prerequisite
- Full server backup
- Trust checks
- Ed25519 manifest, SHA-256, size
Which package Update Center manages
Update Center manages only the main Windows MSI. The browser extension is installed and updated through the Chrome Web Store. The Offline Share Decrypter and the DC Agent are separate components with their own versions.
Back up first, then read the notes
Before the update, take a full backup with the Backup Tool and store it off the server disk. A Quick Recovery package is not enough for this; you need the full server backup. Record the current version and service health, then read the release notes for the server and the tracked components.
Checks before Windows Installer runs
Check for updates in Update Center, then read the displayed version, notes, and checksum before you start. VaultPilot downloads the MSI on the server and verifies it. The published v3.0.3 MSI is unsigned, so VaultPilot accepts it only from the allowed release host, and only when the host, the SHA-256 hash, and the file size match a valid manifest exactly.
After the service restarts
The service restarts while the quiet Windows Installer flow runs. Open the console again once it is reachable. Confirm the points below before you call the update finished.
When the update waits at 76 percent
The 76 percent stage usually means the manifest and the MSI passed verification and the quiet install has started. The service can restart at this point, so the browser may lose contact even during a healthy update. Update Center reconciles the job after the service comes back.
Limits to know
- A live check needs Owner or Admin, and repeated checks in a short time are refused for a while.
- The unsigned-MSI exception covers only the manifest-led update path from the official release; local or staged packages still need a signature.
- A new version number alone does not show the update worked; the health and workflow checks do.
Check step by step
Read more in the guides: Update Center guide, Updates screen guide, Update stalled troubleshooting