What's Running 3.0 uses a Windows technology called Windows Management Instrumentation (WMI) that has been around for more than 10 years for Windows operating systems.

In rare cases, the WMI subsystem, or parts of it components can become corrupt in certain Windows installations. The most common WMI problem is that certain classes (WMI classes) can't be instantiated, resulting for example in an WBEM_E_INVALID_CLASS:Win32_PerfFormattedData_PerfProc_Process exception. This problem affects all applications using WMI, not only What's Running.

Fortunately, Microsoft has put together a Diagnostic utility which helps in pinpointing the problem. In order to understand what is wrong, run Microsofts WMI diagnostic utility. This tool will output a report, scan the report for the string "error" and you will find the errors your installation has.

There are a few descriptions on the web about how to diagnose and fix WMI problems. Please note that WhatsRunning.net can NOT guarantee the results of trying to fix the WMI problems with the approaches described below.

• Troubleshooting WMI With WMIDiag
• Technet Blogs - WMI Troubleshooting tips
• TechNet Webcast: Troubleshooting Windows Management Instrumentation with the New Diagnosis Utility (Level 200)
• TechNet Webcast: Roadmap and Best Practices for Windows Management Instrumentation (WMI) Troubleshooting and Scripting (Level 300)

I would be happy to hear from users who have successfully fixed WMI problems and create a troubleshooting guide here on WhatsRunning.net.