The WMIDIAG tool runs a\ndiagnostic test against a system's WMI configuration and working status,\nreports any errors, and explains the configuration settings. The WMIDIAG tool is available from the Microsoft website. The download is an exe file that will\nextract 3 files. Run the wmidiag.vbs script to start the diagnostics\nscan. If you receive a warning about “Your Default scripting engine is\nWSCRIPT.EXE”, it may appear that’s not happening, but the scan will still run\nin the background. After it’s completed scanning it will automatically open a\ntext file with the results.
\n\n
If you scroll through\nthe file, you’ll see a lot of information about the state of your system, and\nvarious performance counters used by WMI. It’s fairly common to see a few\nERRORS/WARNINGS in the log, especially for things like “(WBEM_E_NOT_FOUND)\nObject cannot be found.” At the end of text file you’ll see the overall status\nfor your system. This will either be:
\n\n- SUCCESS: WMIDiag\ndetermined that WMI works CORRECTLY.
- ERROR: WMIDiag detected\nissues that could prevent WMI to work properly!. Check 'C:\\USERS\\USERNAME\\APPDATA\\LOCAL\\TEMP\\WMIDIAG-V2.1_WIN7_.CLI.SP1.64_CSS-USER_2012.10.16_12.52.59.LOG'\nfor details.
If you see the status\nasking you to check the other log file, check that, as it will contain\nadditional details about your system’s WMI performance.
\n\n\n\n
After running the tool,\nreview the configuration for indications of conditions that will prevent\nup.time from communicating with the WMI system. If errors are reported,\nas a first troubleshooting step, you should try refreshing the performance counters\nwith the below commands. As they will\nfix most of the common WMI issues that interfere with up.time’s ability to\ngather performance metrics.
\n\n\n\n
winmgmt\n/resyncperf
wmiadap /f
\n\n
After refreshing the\ncounters, run the WMIDIAG tool again to see if the errors have been fixed. If\nyou require further assistance resolving the issue after running the scan and\nperformance counter reset commands, then send the WMIDIAG results before\nrefreshing the counters and then again after refreshing the counters, as well\nas the additional .LOG mentioned above to [email protected].