How to re-register S2D performance counters

Question

How to re-register S2D performance counters

Olivia Gonzalez 0

My S2D health service monitoring stopped updating after a host crash. The performance counters for Cluster Storage Spaces Direct were unregistered during the crash and are no longer reporting. How do I re-register the S2D performance counters using lodctr?

0 comments

1 answer

Your answer

Answer 1

You can re-register and rebuild all extensible and system performance counters—including Storage Spaces Direct (S2D)—from an elevated command prompt by running the global lodctr /R command.

Re-registering the Counters

Open Command Prompt or PowerShell as an Administrator.
Run the following commands one by one to rebuild the 64-bit and 32-bit counter libraries from the system backup store:

cmd

cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R

Use code with caution.

Resynchronize the performance counters with Windows Management Instrumentation (WMI):

cmd

winmgmt.exe /resyncperf

Use code with caution.

Restart the required monitoring and WMI services to force them to reload the refreshed counter definitions: cmd
```
   net stop pla && net start pla
```

net stop winmgmt && net start winmgmt

   
   Use code with caution.
   
(Note: If you are running a clustered environment, you may need to perform these steps on the affected cluster node or fail over the node if the registry strings fail to update immediately.) []

If the counters still do not report after rebuilding, let me know:

- **The exact error message** returned by `lodctr /R`

- Whether you see the S2D objects when running **Performance Monitor (`perfmon`)** locally on that hostYou can re-register and rebuild all extensible and system performance counters—including Storage Spaces Direct (S2D)—from an elevated command prompt by running the global [lodctr /R](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/rebuild-performance-counter-library-values) command. 

- **Re-registering the Counters**

  1. Open **Command Prompt** or **PowerShell** as an **Administrator**.
  
  1. Run the following commands one by one to rebuild the 64-bit and 32-bit counter libraries from the system backup store:
  
     cmd
     
     ```yaml
     cd c:\windows\system32
lodctr /R
cd c:\windows\sysWOW64
lodctr /R
     ```
     
     Use code with caution.
     
  1. Resynchronize the performance counters with Windows Management Instrumentation (WMI):
  
     cmd
     
     ```dockerfile
     winmgmt.exe /resyncperf
     ```
     
     Use code with caution.
     
  1. Restart the required monitoring and WMI services to force them to reload the refreshed counter definitions:
  
     cmd
     
     ```haskell
     net stop pla && net start pla
net stop winmgmt && net start winmgmt
     ```
     
     Use code with caution.
     
  *(Note: If you are running a clustered environment, you may need to perform these steps on the affected cluster node or fail over the node if the registry strings fail to update immediately.)* []
  
  If the counters still do not report after rebuilding, let me know:
  
  - **The exact error message** returned by `lodctr /R`
  
  - Whether you see the S2D objects when running **Performance Monitor (`perfmon`)** locally on that host