Identify the package
There are two separate products in the deployment model. The full desktop endpoint installer installs the two protection services and machine-level components. The Microsoft Store package is the console UI and does not install a Windows service or request administrator rights by itself.
Installer fails to launch
- Confirm the file is the signed x64 `VigilanteEDR-Setup-1.0.9-x64.exe` artifact.
- Use the Windows file properties and security prompt to inspect the publisher before running it.
- Capture the Windows event or security-product message if execution is blocked. Do not bypass a security warning without validating the publisher and download source.
Administrator privileges are required
The installer is configured with `requireAdministrator`, and the service registration script also checks for an elevated context. A standard-user launch is expected to trigger UAC or fail closed; this is not the same as an installer-specific exit code.
Application does not start or services are missing
Check both service names and their state:
Get-Service -Name VigilantePrivilegedHelper, VigilanteAgentService -ErrorAction SilentlyContinueIf a service is absent, review the installer log for missing service binaries, interactive-user SID resolution, or service registration errors. The installer starts the helper and then the agent only after registration and protected-state preparation complete.
Installation was interrupted
Do not assume a partial install is healthy. Re-run the signed installer interactively as an administrator and then verify both services. If the issue repeats, keep the installer log and process exit code for support.
Files or configuration appear missing
The installer creates and protects machine state under `C:\ProgramData\VigilanteEDR`. Upgrades preserve endpoint identity, protected secret, quarantine, policy, and telemetry according to the installer module. Do not delete this directory while diagnosing an installation.