Use this checklist if the VaultPilot MSI does not complete or the service does not start after installation.
Checks
- Confirm the MSI was launched as Administrator.
- Confirm the configured port is not already in use.
- Check the
VaultPilotServerWindows service state; upgraded hosts may still exposePassManServeras a legacy alias. - Review installer logs under
C:\ProgramData\VaultPilot\logs; upgraded hosts may still have legacyC:\ProgramData\PassMan\logsevidence. - Re-run only after the previous service state is understood.
Safe data for support
- VaultPilot version, plus the legacy PassMan version only for upgraded installs.
- Windows version.
- MSI file name and signature status.
- Redacted installer log excerpt.
- Port number and service state.
Do not send database files, master passwords, secret values, license private keys, certificates or screenshots showing 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.