Keep your Windows agent up to date

Before you begin

Use an always-on Windows 11 x64 computer and an administrator account. Keep it awake, online and signed in. Your existing monitoring task must already be enabled and running, with a recent normal saved dashboard check. Stopped, disabled, incomplete or uncertain installations need support review first.

For a new network location, follow the separate Windows installation guide first. Do not create a replacement agent or enter another token just to enable updates. This controller does not ask for a token. Find the existing installation ID, beginning agent_, in the original installer record; it is an ID, not the connection token.

1. Download and verify

Extract the complete ZIP. Keep 777pinger-windows-setup.ps1 beside its native folder, and read README.txt. Do not run from inside the ZIP. Verify the script’s signature is valid and its publisher is 777 Easy LLC. The controller also verifies its native program and inventory before placing files.

Stop on an unexpected publisher, altered-file or security-policy warning. Do not bypass execution policy, SmartScreen, antivirus, endpoint protection or your administrator’s rules.

2. Set up with updates off

Open 64-bit Windows PowerShell 5 as administrator in the extracted folder. Replace the placeholder below with your existing installation ID:

powershell.exe -NoProfile -File .\777pinger-windows-setup.ps1 -InstallationId "agent_YOUR_EXISTING_INSTALLATION_ID"

Do not enter a token in this command. The first confirmation installs only the verified updater backend into a protected Program Files folder; it does not enable updates or change monitoring.

Select 10 — Reviewed setup, read the installation-specific confirmation, and type its displayed confirmation word only if you agree. Monitoring briefly stops and is restored. Setup registers the updater disabled and leaves updates off. Press Enter to cancel without approving the action.

Wait for a new saved check on the normal dashboard schedule. Do not force a check or start an update to shorten the wait. A local status screen or running task alone is not proof that results reached the dashboard.

3. Choose whether to enable updates

Reopen the same signed controller with the same installation ID for another action. Each invocation handles one selected menu action; viewing status does not enable updates.

If desired, choose 7 — Set update window before enabling. Enter a named time zone such as America/New_York, distinct days such as Mon,Tue,Wed, and 24-hour times such as 22:00 and 02:00. Overnight windows belong to the day they start. The schedule does not wake or reboot your PC.

2 — Enable updates requires separate explicit consent for the displayed installation and saved schedule. It does not install an update immediately. On its normal schedule, the updater verifies signed release metadata and program files before switching versions. Your connection and monitoring settings are preserved. Confirm a fresh saved dashboard check after an update.

Pause or turn updates off

• 1 — Refresh status: view this installation’s recorded version and update mode.
• 3 — Turn updates off: keep monitoring and retained recovery evidence.
• 4 or 5 — Pause: pause updates for 24 hours or 7 days; monitoring continues.
• 6 — Resume: clear the pause; updates that are off stay off.
• 8 — Clear update window: remove the time restriction without enabling updates.
• 0 — Close: exit without selecting another action.

If setup or recovery needs attention

Keep all files, receipts and failure evidence, and contact support before trying again. Do not reset state, overwrite a partial installation, rerun an old confirmation, delete recovery records or stop unrelated programs such as Herd. An unconfirmed child outcome is not automatically retried. Never paste an agent token into support chat.

9 — Review recovery reviews a recorded interrupted attempt before separate consent. Installed acceptance covers only the reviewed synthetic previous-running-before-future-switch boundary, followed by normal saved monitoring. This does not qualify all real interrupted updates, running-candidate recovery or inactive-agent recovery. Missing or ambiguous evidence, stale review and already-used confirmations require support.

Reviewed recovery leaves updates off: it durably saves updates off in notify mode and preserves your saved pause, update window and time zone, along with the installation’s enabled, running monitoring state. Obtain support review before enabling again, and separately verify a new normal saved dashboard check. “Setup incomplete” is not “Automatic updates off”; Enable cannot finish interrupted setup.

Supported scope and removal

The unchanged signed customer entry passed protected install cancellation, installation and reviewed setup, default-off monitoring, real controls and opt-in, normal scheduled updating to 0.3.2, and the narrow reviewed recovery boundary above. This is not a new reboot, pre-login, signed-out, sleep/wake, running-candidate or inactive recovery qualification.

For an updater-enabled installation, turn updates off and contact support for reviewed removal. Do not use the original manual uninstaller as the removal procedure for an updater-enabled installation. Removing local files does not revoke the cloud token or delete cloud monitors; review those separately. The manual installer, Maintenance tools and their support limitations remain separate.