Skip to documentation

Vigilante Endpoint Protection · v1.0.9

Silent installation and enterprise deployment

Deploy the x64 NSIS endpoint installer with the verified quiet switch and validate the result.

Last updatedOctober 30, 2026
AudienceCustomers, IT administrators, and certification testers

Verified silent switch

The final 1.0.9 artifact uses the standard NSIS quiet switch /S. The product source also uses `/S` when re-running a previously staged trusted installer during rollback.

PowerShell — quiet install
$installer = 'C:\Path\VigilanteEDR-Setup-1.0.9-x64.exe'
$process = Start-Process -FilePath $installer -ArgumentList '/S' -Wait -PassThru
if ($process.ExitCode -ne 0) { throw "Vigilante installer failed with exit code $($process.ExitCode)" }

Elevation remains required. `/S` suppresses the NSIS user interface; it does not remove the administrator requirement. Run the deployment tool in an elevated context and ensure an interactive user is available for service registration.

Deployment considerations

  • Use the signed x64 endpoint installer for Intune, GPO, SCCM, or another administrator-managed channel.
  • Do not treat the Store console-only package as a replacement for the endpoint installer in a fleet rollout.
  • The installer registers `VigilantePrivilegedHelper` before `VigilanteAgentService`, configures automatic service start, and starts both services.
  • Allow the operation to finish before launching the console or starting a second installer process.

Installation verification

PowerShell — service check
Get-Service -Name VigilantePrivilegedHelper, VigilanteAgentService |\n  Select-Object Name, Status, StartType

For deployment logging, capture the installer process exit code and the deployment tool's stdout/stderr. The embedded registration script writes service-operation failures to the installer log and returns an internal PowerShell status of `1` on exception.

Silent uninstall

The source verifies `/S` for silent NSIS execution, but the final release was not executed on a clean machine. Use the standard Windows uninstall entry or an approved enterprise uninstall workflow, and validate the result in your management system before broad rollout. See uninstallation for the cleanup scope.