SolarWinds Platform 2026.1 upgrade fails with “Check for running applications – SolarWinds Orion Service Manager (StopNetPerfMon.exe)” and MSI error 1602

4/21/2026 10:39 PM

4/21/2026 10:39 PM

Exact error messages

During upgrade or install, you may see one or both of the following messages:

• Installer UI / pre-check
  Check for running applications - The following applications should be closed: SolarWinds Orion Service Manager (StopNetPerfMon.exe)

• Installer dialog
  The following applications/services must be closed before installation can continue: StopNetPerfMon (Process Id: xxxxx)

In Windows Application logs (Source MsiInstaller / RestartManager) you may see entries like:

• Application 'C:\Program Files (x86)\SolarWinds\Orion\StopNetPerfMon.exe' (pid XXXXX) cannot be restarted - 1.
• Product: SolarWinds Platform -- Installation failed.
• Installation success or error status: 1602.

symptoms

• Attempting to upgrade SolarWinds Platform (for example, 2025.4 → 2026.1) using the offline ISO.
• The installer stops with a “Check for running applications” / “SolarWinds Orion Service Manager (StopNetPerfMon.exe) must be closed” message.
• In Task Manager:
  • StopNetPerfMon.exe and/or SolarWinds Administration Client are visible.
  • Ending the process causes it to reappear immediately, even after several server reboots.
• The installer eventually fails with MSI error 1602.
• Windows Application log shows Restart Manager events referencing StopNetPerfMon.exe and MsiInstaller events with status 1602.

What this article covers (How-to / Problem–Resolution)

• Explains why the installer blocks on StopNetPerfMon.exe and returns error 1602.
• Shows how to:
  • Positively identify this condition from the UI and Windows logs.
  • Stop and prevent StopNetPerfMon.exe from auto-starting long enough for the upgrade to complete.
  • Run the installer again and verify resolution.

Network Performance Monitor

• StopNetPerfMon.exe is the SolarWinds Platform Service Manager UI, not a Windows service.
• During upgrade, the installer and Windows Restart Manager check for running applications that could block file replacement.
• If **`StopNetPerfMon.exe` is running** (or immediately restarts after being killed), Restart Manager logs:
  • Application '...\StopNetPerfMon.exe' (pid XXXXX) cannot be restarted - 1.
  • Often along with Machine restart is required.

• Because Restart Manager cannot safely close/restart this application, the MSI:

  • Presents a “Check for running applications – SolarWinds Orion Service Manager (StopNetPerfMon.exe)” message, and
  • Ultimately terminates with error 1602.

In some environments, StopNetPerfMon.exe is additionally:

• Automatically relaunched at logon by:
  • Startup entries, Startup folders, Windows “restart apps” feature, or
  • Scheduled tasks or custom services pointing to StopNetPerfMon.exe.
• This causes the process to reappear immediately after End Task, making it appear “unstoppable” and repeatedly blocking the upgrade.

Use these steps during a maintenance window on the SolarWinds Platform primary server.

1. Stop SolarWinds services and close all UI tools

   • Stop all SolarWinds services on the primary server.
   • Close:
     • SolarWinds Platform Service Manager window.
     • SolarWinds Administration Client window.
   • Open Task Manager → Details and:
     • End task on StopNetPerfMon.exe.
     • End task on SolarWinds.Administration.Client.exe.

2. Disable obvious auto-start mechanisms

   a. Startup folders

   • Press Win + R → type shell:startup → Enter.
     
     • Remove any shortcuts to StopNetPerfMon.exe or SolarWinds Administration Client.
   • Press Win + R → type shell:common startup → Enter.
     
     • Remove any similar shortcuts.

   b. Windows “Restart apps”

   • Go to Settings → Accounts → Sign-in options.
   • Turn off options like:
     • “Restart apps” / “Automatically save my restartable apps”.

   c. Task Scheduler (if used)

   • Open Task Scheduler → Task Scheduler Library.
   • Look for tasks whose Action launches:
     • C:\Program Files (x86)\SolarWinds\Orion\StopNetPerfMon.exe, or
     • the SolarWinds Administration Client.
   • Temporarily Disable those tasks.

   d. Custom services (if any)

   • Run services.msc.
   • Look for any custom service whose Path to executable is StopNetPerfMon.exe or the Administration Client.
   • For such a service:
     • Stop it.
     • Set Startup type = Manual.
     • On the Recovery tab, set all failures to Take no action during the upgrade.

3. Ensure StopNetPerfMon.exe is not running (and does not auto-restart)

   • Open Task Manager → Details.
   • End any remaining:
     • StopNetPerfMon.exe
     • SolarWinds.Administration.Client.exe
   • Watch for several seconds:
     • Confirm they do not automatically re-appear.
   • If they still restart immediately, proceed to step 4.

4. Last-resort workaround: temporarily rename StopNetPerfMon.exe

   If StopNetPerfMon.exe continues to restart even after the above:

   • Ensure all SolarWinds services remain stopped.
   • In File Explorer or PowerShell, go to:
     C:\Program Files (x86)\SolarWinds\Orion\
   • Find StopNetPerfMon.exe and rename it to:
     StopNetPerfMon.exe.bak
   • Return to Task Manager → Details:
     • End any StopNetPerfMon.exe processes still in memory.
     • Confirm that the process no longer restarts (the EXE has been renamed).

   Note: Renaming the existing StopNetPerfMon.exe does not break the installer; the upgrade will lay down or repair its own copy as needed. The rename simply prevents the old binary from relaunching during the install.

5. Run the 2026.1 (or later) installer

   • Mount the offline ISO (for example, Solarwinds-OOA-2026.1.0-OfflineInstaller.iso).
   • Start the SolarWinds Platform 2026.1 installer.
   • If a “StopNetPerfMon (Process Id: xxxxx) must be closed” dialog appears:
     • Leave the installer dialog open.
     • In Task Manager → Details, kill the StopNetPerfMon.exe with that PID.
     • Click Retry in the installer.
   • With the process no longer running or auto-restarting, the installer should proceed past the check and complete.

6. Post-upgrade cleanup

   • After the installer and Configuration Wizard finish:
     • If needed, rename StopNetPerfMon.exe.bak back to StopNetPerfMon.exe.
   • Start SolarWinds services.
   • Verify:
     • Web console accessibility.
     • Correct SolarWinds Platform version (for example, 2026.1).

7. If the installer still fails

   • Immediately after the failure, collect a fresh Diagnostics bundle and:
     • Confirm no StopNetPerfMon.exe was running during the failure.
     • Capture updated Application/System event logs.
   • If possible, provide:
     • Exact timestamps.
     • Full error text.
     • The fact that StopNetPerfMon.exe was definitively not present when the installer failed.