WMI is a comprehensive and versatile system for monitoring nearly all aspects of a Windows computer. However, as it is very complex and based on a complex communications protocol (DCOM) it tends to be more error-prone than everyone would like it to be. Here is what you can do if you keep getting errors that indicate problems with the WMI system itself.
As WMI is primarily a Windows function set, the problems described here should be solved by Microsoft - however, we know how frustrating a search for solutions for WMI problems can be so we offer you these suggestions here. Although these procedures are tested and used successfully in many cases we by no means take any responsibility for their outcome and/or negative side effects.
A very good start to approaching WMI problems is the use of Microsoft's very own diagnosis tool, WMIDiag, of course. You can find it in Microsoft's download center (or search Microsoft's website for "WMIDiag", should the download ID have been altered in the meantime).
Apparently performance counters can be disabled via the Windows registry. Should this happen after a Windows Update or the installation of some software package, search in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services branch for "Disable Performance Counters". If you find one or more entries set to "1", set them to "0".
One case where this has helped is the WMI Process sensor, where setting this key in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PerfProc\Performance branch brought red sensors back online.
NOTE: Working with the registry is for advanced users only. See here for details
This will probably fix many problems concerning performance data and is much less intrusive than almost every other suggested method.
Full details about the WMIADAP command here:
The /f switch still forces an update of the WMI classes from the performance libraries.
The /r switch to parse the Windows Driver Model drivers to create performance objects.
The winmgmt console program offers another way of getting corrupted performance counters back on track.
1. Open a command prompt window (Run as Administrator) and enter the following lines.
2. On older Windows systems up to 2003 you have to clear earlier resnyc attempts (on newer systems this will not work):
3. Then do the resynchronization:
As pointed out in this technet article, you can reload the performance counters if you run the following command in a administrator-run command line:
lodctr /r for both folder %WINDIR%/System32 and %WINDIR%/SysWOW64
This tool will repair WMI on the system. See Repair WMI article on my site.
Recommended content with Google's ADs