1. If the WMI service is not started, try to start it. Then test to see if the issue is resolved.
2. Troubleshoot the WMI issue. For more information about how to do this, visit the following Microsoft Web site:
http://www.microsoft.com/technet/scriptcenter/topics/help/wmidiag.mspx Workaround:A workaround to this is to rebuild the WMI Repository.
Warning: This is not suitable if there is critical data stored in the WMI namespace because rebuilding will lose the data. Also, the namespaces of non-Windows products are not rebuilt using the steps below. For example, Exchange WMI namespaces would not regenerate after rebuilding, and this may require a reinstallation of Exchange.
1. Back up the WBEM folder (%windir%\system32\wbem) and then copy the WBEM folder from a freshly installed computer with the same version and service pack level.
2. Run the following steps in a command prompt:
cd %windir%\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /u /s %s
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
wmiprvse /regserver
winmgmt /regserver