Skip navigation

JSI Tip 2874. More on WinMgmt performance counter errors.

We described some WinMgmt performance counter errors and resolutions in tip 2194 and tip 2526.

Event IDs 37, 41, and 61 are either the result of a counter problem, or may be due to the Performance Library Dredger incorrectly determining that the library is invalid, even though the counter works correctly.

These events may also be caused by slow response during startup. Try using Regedt32 to navigate to:


NOTE: As an example, see HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Spooler\Performance.

NOTE: Use Regedit to find Performance, checking only Keys.

NOTE: Some Performance key value names are WbemAdapFileSize, WbemAdapFileTime, and WbemAdapStatus.

On the Edit menu, Add Value name Collect Timeout. Set this REG_DWORD value to a Decimal 10000 and restart your computer. If you continue to get the error, try setting WbemAdapStatus to 0. Then, navigate to:


Double-click ADAPPerflbTimeout and set it to Decimal 180. Restart your computer.

You can also disable the a performance counter by using Exctrlst.exe or by navigating to:


Edit or Add Value name Disable Performance Counters, as a REG_DWORD data type. Setting the data value to 1 will disable the counter.

Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.