Update Center

VaultPilot Update Center manages the main Windows MSI package. The browser extension is installed and updated through Chrome Web Store, while Offline Share Decrypter and VaultPilot DC Agent Service are tracked as component release notes and refreshed by the MSI or their own release assets.

Before installation, confirm the published asset name, file size, SHA-256 and source host, plus the signer when the manifest pins one; do not rely on an example filename or checksum.

Secure update model

Before installing an update, VaultPilot verifies:

  • Ed25519-signed update manifest.
  • Package URL and filename.
  • SHA-256 checksum.
  • MSI Authenticode signer evidence when the manifest pins a signer.
  • File size and release metadata.

For the published 3.0.3 MSI, the package is intentionally unsigned: VaultPilot accepts it only from the allowed release address carried by a valid Ed25519-signed manifest after its exact SHA-256 and file size match. MSI files placed on the server by hand still need a signature, and any manifest that names a signer still requires that signer. CA-backed or trusted-signing certificates remain recommended for Windows SmartScreen reputation and broad OS-level trust.

For network and firewall planning: the server downloads the signed manifest and the MSI over HTTPS from the allowed release host github.com; allow that outbound HTTPS path from the server.

Normal update flow

  1. Export a backup.
  2. Open Update Center.
  3. Check for updates.
  4. Review version, notes and checksum; review signer evidence when the manifest pins one.
  5. Start the update.
  6. VaultPilot downloads and verifies the MSI on the server.
  7. The quiet Windows Installer flow runs.
  8. The VaultPilot service restarts.
  9. Reopen the console and confirm version and health.

Release assets

The official 3.0.3 release contains:

  • VaultPilot-3.0.3-x64.msi
  • vaultpilot-update.json
  • vaultpilot-update-public.pub
  • vaultpilot-browser-vault-extension.zip, an emergency fallback only
  • vaultpilot-extension-update.json
  • vaultpilot-share-decrypter.zip
  • vaultpilot-share-decrypter.json
  • vaultpilot-dc-agent.ps1
  • vaultpilot-dc-agent.json

Users install the browser extension from Chrome Web Store; see Browser extension for the listing and extension ID.

For manual verification, use release asset verification before installing or forwarding assets internally. Compare asset names, sizes and SHA-256 values against the published v3.0.3 values, not against copies received through other channels.

Component notes

Update Center does not install the browser extension; Chrome Web Store handles extension installs and updates. It has no separate installer for the DC Agent or Offline Share Decrypter either: their version notes stay visible, and the MSI refreshes the support files shipped with the server. For manual installation or recovery, download the component from the official release.

Troubleshooting

SymptomFirst check
Update stops around 76 percentManifest/hash verification state and Windows Installer event log.
Checksum mismatchDelete the downloaded MSI and retry from the release asset.
Service does not restartQuery VaultPilotServer and review installer logs. On upgraded hosts, also check the older PassMan service name.
Version did not changeConfirm the MSI completed, then restart the service.

Back to Documentation