The 76 percent stage usually means VaultPilot has verified the release manifest and MSI package, then entered the quiet Windows Installer phase. The server may restart during this step, so the browser can temporarily lose contact even when the update is healthy.
Triage
- Open Updates and leave the job detail visible before refreshing.
- Let the expected service restart finish before retrying.
- Reopen VaultPilot and check the running version from the UI or server status.
- Review the update job detail for final state, MSI path, SHA-256 and signer status.
- Inspect Windows Installer event log and verbose MSI log only if the job does not reconcile.
- Confirm the latest release manifest still points to the expected MSI and SHA-256 hash.
What to check
| Evidence | Healthy signal | Problem signal |
|---|---|---|
| Release manifest | Signature, version and package URL match the intended release. | Manifest changed unexpectedly or cannot be verified. |
| Package hash | SHA-256 matches the manifest. | Hash mismatch, missing package or partial download. |
| Signer | When the manifest pins a signer, the signer thumbprint matches it; the unsigned 3.0.3 MSI pins none. | Unknown signer or untrusted local-only signer where a signer is pinned. |
| Windows Installer | Service restart and install completion event appear. | Installer error, rollback or missing completion event. |
| Job state | Job reconciles after service restart. | Job remains stale after the server is reachable again. |
Safe evidence
- VaultPilot version before and after the update.
- Update job id placeholder, state, percentage and final error category.
- MSI filename, SHA-256 and signature status.
- Redacted Windows Installer event id and timestamp.
- Whether the service restarted and came back online.
Do not do
Do not bypass manifest verification, replace the MSI manually, alter signer trust, edit the database job row, or share raw logs that include local paths, user names or secrets.
Related
Still stuck?
Check the troubleshooting guide, then write to support@vaultpilot.io with the version, the steps you took and the exact redacted error. Never attach passwords, vault exports or private keys.