WMIDiag.vbs and the Missing WMI Files

WMIDiag.vbs and the Missing WMI Files

  • Comments 16
  • Likes

Last year, we discussed using the WMI Diagnosis Utility in a post on Basic WMI Testing.  We’ve certainly noticed that more than a few of our customers are running the utility before contacting us, which certainly helps us in our troubleshooting.  However, in the last couple of months, we’ve had a few customers call in reporting that the utility is reporting several missing core WMI files on Windows Vista and Windows Server 2008 systems and this is creating concern for the administrators.  When reviewing the log file of the WMIDiag.vbs output, they see entries such as the ones below:

..167 07:09:07 (1) !! ERROR: WMI System file 'C:\WINDOWS\SYSTEM32\WBEM\FRAMEDYN.DLL' is MISSING or is access DENIED.
..168 07:09:07 (2) !! WARNING: WMI System file 'C:\WINDOWS\SYSTEM32\WBEM\FRAMEDYNOS.DLL' is MISSING or is access DENIED but it is an OPTIONAL component.
..177 07:09:07 (1) !! ERROR: WMI System file 'C:\WINDOWS\SYSTEM32\WBEM\PROVTHRD.DLL' is MISSING or is access DENIED
..193 07:09:07 (1) !! ERROR: WMI System file 'C:\WINDOWS\SYSTEM32\WBEM\WBEMCOMN.DLL' is MISSING or is access DENIED.

Naturally, when running any sort of diagnostic report on a system, you would get concerned about the fact that core files are reported as missing.  However, in this particular instance, this is not a problem with the OS – but rather, an issue with the current version of the WMI Diagnosis Utility.  Several WMI core files, such as the ones listed above (FRAMEDYN.DLL, FRAMEDYNOS.DLL, PROVTHRD.DLL and WBEMCOMN.DLL) have been moved from the C:\WINDOWS\SYSTEM32\WBEM folder into the C:\WINDOWS\SYSTEM32 folder.  However, the WMIDiag utility hasn’t been updated to reflect that, which is why you’ll see these errors in the WMI Log.

So what’s the way forward?  As with many tools, change sometimes comes slowly.  For those of you who have run into these problems with WMIDiag, rest assured that we are working on a new version of WMIDiag.

- CC Hameed

Share this post :
Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • What about update\quick fix for Windows XP Professional x64 SP2?

  • Are there also Windows 2008 issues with the WMI CONNECTIONS section of the reports?  I receive a pair of WBEM_E_NOT_FOUND errors listing classes that don't exist.  It seems that similarly, but slightly differently, named classes do exist:

    Reported Missing: Win32_PerfFormattedData_TermService_TerminalServices

    Exists on system:

    Win32_PerfFormattedData_TermService_TerminalServicesSession

    Reported Missing:

    Win32_PerfRawData_TermService_TerminalServices

    Exists on system:

    Win32_PerfRawData_TermService_TerminalServicesSession

    I ran 'WINMGMT.EXE /SYNCPERF' successfully, but it didn't resolve the error message.  Thanks!

  • Your post above states that the files are not missing because they are in the C:\WINDOWS\SYSTEM32 folder.  What if they aren't anywhere on the system?

    "Several WMI core files, such as the ones listed above (FRAMEDYN.DLL, PROVTHRD.DLL and WBEMCOMN.DLL) have been moved from the C:\WINDOWS\SYSTEM32\WBEM folder into the C:\WINDOWS\SYSTEM32 folder."

  • Your post above states that the files are not missing because they are in the C:\WINDOWS\SYSTEM32 folder.  What if they aren't anywhere on the system?

    "Several WMI core files, such as the ones listed above (FRAMEDYN.DLL, PROVTHRD.DLL and WBEMCOMN.DLL) have been moved from the C:\WINDOWS\SYSTEM32\WBEM folder into the C:\WINDOWS\SYSTEM32 folder."

  • Is there any chance of there being a version compatible with 2008 R2 any time soon?  The original post is over a year and a half old now, and I can't find a newer download anywhere that works with R2.  I have some WMI issues and was hoping this could help track down what the problem is.

  • any update on a new version that supports Windows 7 and Windows Server 2008?

    greg.colucci@bldr.com

  • I am getting an error that MOF is not able to connect to the WMI Server.  I am running on Windows 7, but I'm not able to run diagnostics for WMI.  Is there a new Utility for Windows 7?

  • So no problem with those dlls... is it also a false positive this behaviour?

    On Vista 32bit Italian I'm getting a lot of security errors like "Default trustee 'NT AUTHORITY\NETWORK SERVICE' has been REMOVED!" but I have an user named "SERVIZIO DI RETE" with the same significance and permissions (it's just the translation of the name NETWORK SERVICE), is WMIDIAG supposed to work only with English language OS?

  • We're now May 2011. Where is the new utility?

  • I am also looking for the new version. Is that available for server 2008 64 bit?

  • Hi, I would like to kindly ask if there is a compatible version available for Windows Server 2008 R2 and Windows 7.

  • Hello Roland/All, we are currently working on it and should be available in Q1 of this year.  Thanks for being so patient with us while we get it ready for availability.

  • WMIDiag 2.1 is now available!

    www.microsoft.com/.../details.aspx

    Supported Operating Systems: Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP

  • ERROR: The following WMI system file(s) is/are missing

    C:\Windows\System32\WBEM\framedyn.dll

    C:\Windows\System32\WBEM\provthrd.dll

    C:\Windows\System32\WBEM\wbemcomn.dll

    still exist in version 2.1

  • Jevgenijs, those files were moved to "%windir%\system32", however WMIDiag 2.1 is still looking for them in the "%windir%\system32\wbem" folder.  You can safely ignore this.  This should be corrected in the next release.

    Thank you.