Skip to documentation

Vigilante Endpoint Protection · v1.0.9

Install Vigilante Endpoint Protection

Install the signed Windows desktop endpoint and verify the protection services are present.

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

Overview

Vigilante Endpoint Protection is the full Windows desktop distribution. The signed 1.0.9 installer installs the desktop console together with the Vigilante Agent Service and Vigilante Privileged Helper as Windows services.

Scope note. This page describes the external x64 endpoint installer. The Microsoft Store package is a console-only package; it does not install the protection services by itself.

Verified requirements

  • Windows x64 desktop hardware and OS support are the target of the signed artifact `VigilanteEDR-Setup-1.0.9-x64.exe`.
  • Administrator elevation is required. The build sets the Windows execution level to `requireAdministrator`.
  • An interactive Windows user must be discoverable during service registration so the agent pipe can be bound to the correct user SID.

The release evidence does not establish a Windows version floor, disk/RAM minimum, or clean-machine compatibility matrix. Those values are intentionally not specified here.

Download and install

  1. Download the signed x64 installer from the Scalewidth-approved distribution channel. Use the file named VigilanteEDR-Setup-1.0.9-x64.exe.
  2. Open the file and review the Windows publisher and security prompt before continuing.
  3. Accept the installer terms, choose the installation directory if prompted, and select Install.
  4. Approve the administrator prompt. The installer copies the application payload, configures protected ProgramData state, registers the helper first and agent second, then starts both services.
  5. Launch Vigilante Endpoint Protection from the Start menu or desktop shortcut created by the installer.

Common installation problems

  • If the installer cannot resolve a unique interactive user, service registration stops and the installation cannot continue safely.
  • If either service binary is missing from the payload, registration stops before the services are created.
  • If a service action fails, the installer logs the service exit value and aborts the operation. See installer exit codes and troubleshooting.