Self Install Span Coding Hooks on Windows

Last updated: June 16, 2026

Before you start

  • A PC running Windows 10 or Windows 11

  • Administrator access on the machine

  • Your Span auth token (provided by your Span administrator)

  • Your work email

Step 1: Download the files

Save both files into the same folder on your PC (e.g. %USERPROFILE%\Downloads\):

💡 When downloading, Windows SmartScreen might warn that the files are not commonly downloaded. This is normal for a new internal tool. The script’s only function is to install, e.g., coding-hooks-1.12.2.msi and save your auth token and work email locally. Click More info → Run anyway (or Keep in the browser) to continue.

Step 2: Run the install

Open the Start menu, search for PowerShell, right-click Windows PowerShell, and choose Run as administrator.

In the elevated PowerShell window, cd into the folder where you downloaded the files, then paste the command below. Replace <VERSION> with the version number from your downloaded MSI filename, and <TOKEN> and <EMAIL> with your values:

cd <path\to\folder>    # e.g. cd $HOME\Downloads
powershell -ExecutionPolicy Bypass -File .\windows-with-admin-access.ps1 `
  -Msi   .\coding-hooks-<VERSION>.msi `
  -Token <TOKEN> `
  -Email <EMAIL>

Approve the UAC prompt if Windows asks.

âś… Done when you see: Result: 11/11 checks OK

Step 3: Clean up (optional)

Once the health check passes, the downloaded files are no longer needed. From the folder where you saved them, run:

Remove-Item coding-hooks-*.msi, windows-with-admin-access.ps1

(If you cd’d into the folder in Step 2, you are already there.)

Verify anytime

& "$env:LOCALAPPDATA\Span\bin\hook-dispatcher.exe" span-health

Updating your token later

If your Span administrator gives you a new token, run from an elevated PowerShell:

powershell -ExecutionPolicy Bypass `
  -File "C:\Program Files\Span\CodingHooks\1.11.1\install\windows-with-admin-access.ps1" `
  -Token <NEW_TOKEN>

Your work email is preserved automatically; no need to re-enter it.

Uninstall

From an elevated PowerShell:

Get-Package -Name "Span IDE Hooks" | Uninstall-Package -Force

Troubleshooting

  • Error: must run as Administrator. Close the PowerShell window, re-open it via right-click → Run as administrator, then re-run the command.

  • Error: -Msi path not found: … The MSI is not in the current folder. Make sure you cd’d into the folder where you saved it (run Get-ChildItem coding-hooks*.msi to confirm), then re-run the command.

  • Error: -Email does not look like an email address: … Provide a valid email address like you@yourcompany.com.

  • Error: -Token (or SPAN_AUTH_TOKEN env) is required. Re-run with the Span auth token provided by your Span administrator.

  • span-health shows delivery_log: no log yet. This is expected on a fresh install, no hook events have flowed through yet. Use Claude Code, Cursor, or Codex briefly, then re-run the verify command; the warning will clear.

  • span-health shows delivery_log ... error(s). Usually clears within a few minutes. If the count continues to grow, contact the Span team.

  • PowerShell says “running scripts is disabled on this system”. Your machine has a restrictive execution policy. The ExecutionPolicy Bypass in the command above only applies to that one invocation; the policy on your machine is unchanged.

If you are stuck on an issue not listed here, please share the full PowerShell output, plus C:\ProgramData\Span\CodingHooks\self-install-msiexec.log and C:\ProgramData\Span\CodingHooks\install-msi.log, with the Span team.