Network Management

Average CPU and Memory Metrics Are Not Displayed for a Windows Server Node in the SolarWinds Platform

Average CPU Load and Memory Statistics, Average Memory, and Average CPU metrics are not displayed for an agent-monitored Windows Server 2019 node.

First published date

10/19/2026 6:48 PM

Last published date

10/19/2026 6:48 PM

Overview

Environment

  • SolarWinds Platform

  • Windows Server 2019

  • Node monitored through the SolarWinds agent

Symptoms

The node is shown as up, but the following values are blank or unavailable:

  • Average CPU Load

  • Memory Used

  • Memory Available

  • Total Memory

  • Average Memory Usage

  • Average CPU performance data

Product section

Orion Platform

Cause

WMI is not returning the performance-counter data required by the SolarWinds CPU and memory collectors. In this case, WMI repository corruption or an associated WMI infrastructure problem on the monitored server prevented the query from completing.

The WinRM error alone does not prove that the WMI repository is corrupted. Verify the repository and rule out provider, namespace, permission, or connectivity issues before rebuilding or resetting it.

Resolution

Have a Windows server administrator perform the following steps on the affected server.

1. Reproduce the WMI query with WBEMTest

  1. Sign in to the affected Windows Server 2019 server.

  2. Open WBEMTest.exe with administrative privileges.

  3. Select Connect and connect to the local root\CIMV2 namespace.

  4. Select Query.

  5. Use WQL and run the following query:

SELECT PercentProcessorUtility
FROM Win32_PerfFormattedData_Counters_ProcessorInformation
WHERE NOT Name LIKE "%Total%"

  1. Confirm whether WBEMTest returns the same WMI or WinRM error. If it does, the problem is on the Windows server's local WMI path rather than in the SolarWinds dashboard display.

2. Verify the WMI repository

Open an elevated Command Prompt and run:

winmgmt /verifyrepository

  • If the result is WMI repository is consistent, do not reset the repository. Continue troubleshooting WMI providers, the root\CIMV2 namespace, permissions, or local connectivity.

  • If the result is WMI repository is inconsistent, continue to the salvage step.

3. Salvage the repository

Run:

winmgmt /salvagerepository

After the command completes, run the verification command again:

winmgmt /verifyrepository

4. Reset the repository only if salvage does not resolve the inconsistency

If the repository remains inconsistent, coordinate with the Windows server administrator and run:

winmgmt /resetrepository

Restart the server if required by the Windows administrator's recovery procedure. Because a repository reset can affect applications that use WMI, take an appropriate backup and change-control precautions before running it.

Do not manually delete the C:\Windows\System32\wbem\Repository folder or blindly recompile every MOF file. Those actions can remove provider registrations, damage installed applications, or make root-cause analysis more difficult. Use Microsoft-supported recovery guidance or engage Microsoft Support for advanced recovery.

5. Validate SolarWinds polling

  1. Confirm that WBEMTest now returns PercentProcessorUtility data.

  2. In the SolarWinds Platform, open the affected node.

  3. Select Poll Now or wait for the next polling cycle.

  4. Confirm that Average CPU Load, Average Memory Usage, Memory Used, Memory Available, and Total Memory are populated.

  5. Review Core.CpuMemory.Wmi.log to confirm that the WMI query is no longer failing for the node ID.

Result

After the WMI repository was repaired on the node, the CPU and memory metrics populated normally.