1. Home
  2. Product Guides
  3. APM
  4. Agent installation
  5. Windows

Windows

The current Raygun APM installer supports 64-bit Windows Server 2016 or newer. One x64 MSI installs the x64 Agent, both x64 and x86 profilers, and the managed ASP.NET Core startup hook. The included x86 profiler supports 32-bit applications running on 64-bit Windows. The installer does not support 32-bit Windows or Windows on ARM64.

Open an elevated PowerShell prompt and run:

Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1 | Invoke-Expression

The bootstrap script:

  1. resolves the latest production release;
  2. verifies its manifest, SHA-256, and Authenticode signature;
  3. installs the signed MSI without restarting Windows;
  4. starts the RaygunAgent Windows service; and
  5. verifies the installed files and http://127.0.0.1:18100/status health endpoint.

Use -Interactive to show the MSI user interface:

& ([ScriptBlock]::Create((Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1))) -Interactive

Pin an immutable release for a repeatable deployment:

& ([ScriptBlock]::Create((Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1))) -Version 3.1.3

To repair an existing installation without changing its version, specify that version and add -Reinstall. This restores all MSI payload files and repeats the service and health checks:

& ([ScriptBlock]::Create((Invoke-RestMethod https://downloads.raygun.com/apm/install.ps1))) `
  -Version 3.1.3 -Reinstall

Using -Reinstall without -Version selects the latest production release. It upgrades an older installation before running the repair checks.

The x64 MSI supports major upgrades from earlier x64 Raygun APM Agent releases, including the 1.0 release family.

Legacy x86 MSI packages cannot be upgraded in place. If setup reports a legacy x86 installation, manually uninstall the x86 Raygun APM Agent from Apps & features, restart Windows if requested, and then run the current x64 installer.

The installer creates the automatic RaygunAgent Windows service, installs the Configuration Utility, and includes the managed startup hook used for automatic ASP.NET Core request correlation. Application configuration uses these stable paths:

C:\Program Files\Raygun\RaygunAgent\Agent3\RaygunAgent.exe
C:\Program Files\Raygun\RaygunAgent\Agent3\Config\RaygunConfigurationUtil.exe
C:\Program Files\Raygun\RaygunAgent\Agent3\Raygun.Apm.StartupHook.dll
C:\Program Files\Raygun\RaygunProfiler\latest\x64\RaygunProfiler.dll
C:\Program Files (x86)\Raygun\RaygunProfiler\latest\x86\RaygunProfiler.dll

Do not configure an application with a version-specific profiler path. The installer switches the latest selector during an upgrade. When Raygun configures a CoreCLR application, it adds the stable hook path to DOTNET_STARTUP_HOOKS, preserves non-Raygun startup-hook entries, and replaces an older Raygun hook path.

Get-Service -Name RaygunAgent
Invoke-RestMethod http://127.0.0.1:18100/status

The service must be running and the health response must report that the Agent is running.

For IIS, open the Configuration Utility, select each application pool, enter its Raygun application API key, and apply the configuration. For supported Windows services, use the Raygun Agent command line. Restart or recycle the application so its CLR loads the profiler and, for CoreCLR, the startup hook.

See .NET on Windows profiler setup for the Configuration Utility, Server Core command line, and manual IIS configuration methods.

Uninstalling the Agent removes Raygun-owned application configuration for future process starts, deregisters the profiler, and removes the latest selectors. It does not stop or recycle IIS application pools or profiled customer Windows services.

A process that already loaded a profiler DLL can continue running until you restart it. Windows may defer deletion of that versioned DLL until the process or machine is restarted.

If traces do not appear, see Windows troubleshooting.

On this page: