8/23/2018 WMIDiag 2.2 is here!

| Ask the Performance Team Blog

Server & Tools Blogs > Server & Management Blogs > Ask the Performance Team Blog
Sign in

Ask the Performance Team Blog

Thoughts from the EPS Windows Server Performance Team

WMIDiag 2.2 is here!

★
★★★★
★★
★★★★★
★★★

May 12, 2015 by Blake Morrison // 7 Comments

Share 0 0 0

Hello AskPerf blog readers! Jeff here from the Windows Performance Team once again. I am happy to announce
that the new version of WMIDIAG is finally here. It’s now compatible for Windows 8/8.1 as well as Sever
2012/2012R2. Some of you may have been aware that the previous version used to also show a lot of errors and
that majority of them were erroneous or false positives simply due to wmi class name changes between OS
versions. That has been all cleaned up and all errors have been corrected. When you run the new version it
should look a lot cleaner and what errors you do see should be accurate and deserving of attention.

The WMI Diagnosis Tool is a VBScript based-tool for testing, validating, and analyzing WMI installation/issues.
The tool collects data from WMI installations on all Microsoft Operating Systems at any or no service pack level.

WMI Diagnostics 2.2 requires you to have Local Administrator rights as well as Windows Script Host (WSH)
enabled.

To download this tool, please click here.

After you download WMIDiag.exe, run it and extract the files to a local folder. If you double-click WMIDiag.vbs,
the following message will appear:

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 1/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

If you want to see its activity, then you would run “cscript WMIDiag.vbs” from the command prompt, or you can
change the default script host to the command line by running “cscript //H:CScript”.

Note: By default WMIDiag does not check repository consistency and you would need to run manually from
command prompt using “cscript WMIDiag.vbs checkconsistency”

WMIDIAG can be run from Windows Explorer, or from the command line. Each time it runs, the WMI Diagnosis
Tool creates the following three files in the %TEMP% directory:

.LOG file containing all the WMI Diagnosis Tool activity as well as a WMI report at the end

.TXT file containing the WMI Diagnosis Tool report

.CSV file containing statistics that can be used to measure trends and issues

When the WMI Diagnosis Tool terminates, the ERRORLEVEL environment variable is set to one of the following
values:

0 = SUCCESS

WSH has a script execution timeout setup (in machine or system environment)
Machine reports suspicious improper shutdowns
User Account Control (UAC) status is reported (Vista and above)

Local account token filter policy is reported (Vista and above)

Unexpected binaries in the WBEM folder
The Windows Firewall is enabled

Some WMI service installed in the machine are dependent on the WMI service (i.e. "SMS Agent)
WMI ADAP has a status different than 'running'
Some WMI namespaces require a packet privacy encryption for a successful connection

Some WMI permanent subscriptions or timer instructions are configured

Some information about registry key configurations for DCOM and/or WMI was reported

1 = ERROR

System32 or WBEM folders are not in the PATH

WMI system file(s)\ repository is/are missing

WMI repository is inconsistent (XP SP2, 2003 SP1 and above)

DCOM is disabled
WMI service is disabled

The RPCSS and/or the WMI service(s) cannot be started

WMI DCOM setup issues

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 2/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

Expected default trustee or ACE has been removed from a DCOM or WMI security descriptor
The ADAP status is not available
One or more WMI connections failed

Some GET operations\WMI class MOF representations\WMI qualifier retrieval operations failed
Some critical WMI ENUMERATION operations\WMI EXECQUERY\WMI GET operations failed
Some WRITE operations in the WMI repository\PUT\DELETE operations failed

One of the queries of the event log entries for DCOM, WMI and WMIADAPTER failed
Some critical registry key configurations for DCOM and/or WMI were reported

2 = WARNING

System32 or WBEM folders are further in the PATH string than the maximum system length
System drive and/or Drive type reporting are skipped

DCOM has an incorrect default authentication level (other than 'Connect')

DCOM has an incorrect default impersonation level (other than 'Identify')
WMI service has an invalid host setup

WMI service (SCM configuration) has an invalid registry configuration

Some WMI components have a DCOM registration issue
WMI COM ProgID cannot be instantiated

Some WMI providers have a DCOM registration issue

Some dynamic WMI classes have a registration issue
Some WMI providers are registered in WMI but their registration lacks a CLSID

Some WMI providers have a correct CIM/DCOM registration but the corresponding binary file cannot be
found
A new ACE or Trustee with a denied access has been modified to a default trustee of a DCOM or WMI
security descriptor
An invalid ACE has been found for an actual DCOM or WMI security descriptor

WMI ADAP never ran on the examined system

Some WMI non-critical ENUMERATION operations failed\skipped
Some WMI non-critical EXECQUERY operations failed\skipped

Some non-critical WMI GET VALUE operations failed

Some WMI GET VALUE operations were skipped (because of an issue with the WMI provider)

The WRITE operations in the WMI repository were not completed

The information collection for the DCOM, WMI and WMIADAPTER event log entries was skipped
New event log entries for DCOM, WMI and WMIADAPTER were created during the WMI Diagnosis Tool
execution

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 3/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

Some non-critical registry key configurations for DCOM and/or WMI were reported

3 = Command Line Parameter errors

4 = User Declined (Clicked the Cancel button when getting a consent prompt)

WMIDiag is started on an unsupported build or OS version

WMIDiag has no Administrative privileges

WMIDiag is started in Wow environment (64-bit systems only)

When you run the WMI Diagnosis Tool via command line:

C:\>CSCRIPT WMIDiag.vbs

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 4/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

The generated report “%TEMP%\WMIDIAG-V2.2_WIN8.1_CLI.RTM.64_MYPC_2015.05.11_15.02.30-REPORT.TXT“

contains two types of figures:

WARNING – Information that is useful if certain actions are executed

ERROR – Problems that need to be solved to avoid errors reported by WMI

WMI DIAG 2.2 FAQ:

1. Where can I get the WMI Diagnosis Tool?

The WMI Diagnosis Tool can be downloaded from the Microsoft Download Center at
http://www.microsoft.com/en-us/download/details.aspx?id=7684. More information about the WMI Diagnosis
Tool usage can be found in the document (WMIDiag.doc) which comes along with the download.

2. Is the tool supported?

There is no official support for WMI Diagnosis Tool.

3. Can the WMI Diagnosis Tool diagnose a remote computer?

The WMI Diagnosis Tool is not designed to diagnose remote computers. This is due to the fact that WMI remote
access is mainly based on the WMI infrastructure. Because the aim of WMI Diagnosis Tool is to diagnose WMI,
the WMI Diagnosis Tool does not use WMI to perform its core operations. That’s why the WMI Diagnosis Tool
must be run locally. However, the WMI Diagnosis Tool can be deployed remotely using Group Policy, Systems
Management Server (SMS), or Microsoft Operations Manager (MOM) via a Management Pack. With Windows
Vista, the WMI Diagnosis Tool can also be remotely executed through WinRM/WinRS, provided you configure
and enable these features (WinRM/WinRS are not enabled by default). Microsoft SysInternals tool PSEXEC.EXE on
Technet can also be used.

4. Does the WMI Diagnosis Tool fix problems it discovers?

No. The WMI Diagnosis Tool executes in read-only mode. Even though the WMI Diagnosis Tool diagnoses the
situation and provides procedures to fix problems, at no time does the tool automatically fix a problem. This is by
design, because the correct repair procedure depends on the context, the usage, and the list of applications
installed on the computer.

I hope this new tool will help you identifying potential WMI issues in your environment. Don’t forget to read the
support document (WMIDiag.doc) included in the WMIDIAG 2.2 download.

-Jeff

Search MSDN with Bing

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 5/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog
g

Search this blog Search all blogs

Top Server & Tools Blogs

ScottGu's Blog
Brad Anderson’s "In the Cloud" Blog

Somasegar's Blog
Brian Harry's Blog

Steve "Guggs" Guggenheimer's Blog

Live Map

Click to enable Adobe Flash Player

Useful Microsoft Blogs

IE Blog
Terminal Server Blog

PowerShell Blog
NT Debugging Blog
MSRC (Security) Blog

Exchange Team Blog

IIS Site
LATAM (Portugese / Spanish)

OEM Team Blog

MS HotFix and Hot Issues Blog

Platforms Blogs

CORE (Setup / Cluster)

Directory Services
LATAM (Latin America)
Manageability (Configuration Mgr)
https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 6/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

Manageability (Mobile Device Mgr)

Manageability (Operations Mgr)
Manageability (SoftGrid)

Manageability (SUS)
Networking
Small Business Server

Windows Essential Business Server

Manageability (SCVMM)

Recent Posts

WOW…are folks still reading this blog??? March 5, 2018

AskPerf Blog transition… March 28, 2016

Office Applications only print 1-2 pages September 25, 2015
Remote Desktop Licensing Service Stopping September 24, 2015

Tags

Application Compatibility Applications and Services Architecture

Debugging DST General GPO Internet Explorer Leak Memory
Management Networking Pages Performance PowerShell PrintBRM
Print fixit Printing Print Migration RDS Remote Desktop Services Remote Desktop
Services Deployment Remote Desktop Services Installation Search Security Server Core Server

Manager Shell Support Center Task Scheduler Team Bios Terminal Server
Troubleshooting Two Minute Drill Windows 7 Windows 8 Windows 10
Windows Server 2008 Windows
Windows Installer Windows Server 2003

Server 2008 R2 Windows Server 2012 Windows Vista Windows XP WMI

WMIseries

Archives

March 2018 (1)

March 2016 (1)
September 2015 (2)
https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 7/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

August 2015 (1)

July 2015 (1)
June 2015 (1)
May 2015 (6)
April 2015 (5)
All of 2018 (1)
All of 2016 (1)
All of 2015 (24)
All of 2014 (21)
All of 2013 (31)
All of 2012 (53)
All of 2011 (29)
All of 2010 (53)
All of 2009 (191)
All of 2008 (123)
All of 2007 (93)
All of 2006 (1)

Tags WMI

Join the conversation Add Comment

adam 3 years ago

Is it possible to run this tool via remote command-prompt started through PSEXEC? It
appears to work.

Bryan 2 years ago

The generated statistics CSV doesn’t work in the WMIDiag.xls DATA tab. Has anyone
noticed this? Maybe I am doing something wrong.

GDeans 1 year ago

‘RepositorySize (MB) – AFTER WMIDiag’ and ‘Disk freespace (MB) – AFTER WMIDiag’
(AD & AE respectively) no longer have data from the v2.2 script. To keep the file functional just insert the data
from the before columns becuase the calculations used look to these values not the before value that it still
captures.

There is also serious logic issues on the main report sheet but I ended up modifying them all to include an If
IsError condition to output a 0 on divide by zero errors.
https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 8/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

I’ve also modified the formula on the DATA sheet in B2 to simply use a Count function rather than CountIf and
check for the older script version since that isn’t used in any way for the calculations.

Maybe I’ll post these as issue to their GitHub page at https://github.com/eladkarako/WMIDiag.vbs?

bob 2 years ago

One thing I noticed is OS reported as 8.1 while it was in truth 10.0 (upgraded from 8.1)
nice to know it was originally 8.1 but should report as 10.0

Donna Sander 1 year ago

That’s because the tool was only designed for Windows 8/8.1 …not windows 10. It
seems to work, but how accurate it is in 10, no one seems to know.

Nagorg 1 year ago

Nice, helpful post Perf Team!

AR Duncan-Jones 1 year ago

I have posted a note on the Technet page (https://technet.microsoft.com/en-

us/library/ff404265.aspx) feedback, and e-mailed the team at WMIDiag@microsoft.com; but am posting here as
maybe a better way to get an answer (the invitation to e-mail said I was not guaranteed a reply).

A. This Technet page refers to version 2.0 – the Download page (https://www.microsoft.com/en-
us/download/details.aspx?id=7684) indeed has version 2.2 which you unveil in this post.

B. The instructions on the Download page say that the .exe file will bring a package including a readme file and
sample spreadsheets. All I get is the .exe file: WMIDiag.exe of 588 KB – no zip, no readme, nothin’ else – OK,so run
it and it will itself produce the goodies.

C. But running the .exe file, even as an administrator, still produces the response:
“The version of this file is not compatible with the version of Windows you’re running. [Check if 32- or 64- bit,
and] contact the software publisher.”
D. I am therefore addressing myself to the wonderful software publisher (that’s you), and I would be grateful if you
could provide me with a working WMIDiag package for Windows 7 Ultimate 32-bit.

Many thanks for your help.

A.R. Duncan-Jones

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 9/10
8/23/2018 WMIDiag 2.2 is here! | Ask the Performance Team Blog

© 2018 Microsoft Corporation.

Terms of Use Trademarks Privacy & Cookies

https://blogs.technet.microsoft.com/askperf/2015/05/12/wmidiag-2-2-is-here/ 10/10