WMI: Rebuilding the WMI Repository

[CraigMarcho]

First published on TECHNET on Apr 13, 2009

UPDATE 3/8/2017

This BLOG is no longer valid. Please see this one instead:

WMI: Repository Corruption, or Not? - Microsoft Tech Community

REBUILDING THE WMI REPOSITORY

Scenario Windows Management Instrumentation fails due to repository corruption or the repository is too large

The WMI Repository "%windir%System32\Wbem\Repository" is the database that stores meta-information and definitions for WMI classes; in some cases the repository also stores static class data as well. If the Repository becomes corrupted, then the WMI service will not be able to function correctly.

If you suspect WMI or repository corruption, rebuilding repository is the last thing you should do. Deleting and rebuilding the repository can cause damage to the system or to installed applications. Other steps should be taken first to eliminate other possibilities or to confirm we have repository corruption. An extremely large Repository also creates problems and can sometimes be interpreted as a corrupt repository, which is not always the case. If issues are due to a large repository, rebuilding the repository is currently the only method available to reduce the repository size.

It's a good idea to alwasy capture a WMIDiag report for any WMI related issues:

If WMI is corrupted, you can receive various errors depending on what activity was being accomplished at the time.

Below are a few scenarios/errors that indicate repository corruption:

• Unable to connect to root\default or root\cimv2 namespaces thru wbemtest. Fails returning error code 0x80041002 pointing to WBEM_E_NOT_FOUND

• When we open Computer Management and Right Click on Computer Management(Local) and select Properties, you get the following error: "WMI: Not Found" or it hangs trying connect

• 0x80041010 WBEM_E_INVALID_CLASS

• Trying to use wbemtest, it hangs

Actions to try

First try the following actions to see if they resolve your issue:

a. Re-register all of the dlls and recompile the .mofs in the wbem folder and re-registering WMI Service and Provider. You can use the following script by saving to txt file then renaming to .bat and running from command prompt with admin right and changing focus to following directory: C:\Windows\System32\Wbem.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

b. Reboot the machine and test WMI

Next, check the repository for consistencies:

For Windows Vista , Windows 7 , Windows Server 2008, and Windows Server 2008 R2 , you can run winmgmt /verifyrepository from a command prompt.
For Older OS like Windows XP and Windows Server 2003 run: WmiDiag tool with the checkconsistency option. For example: WmiDiag checkconsistency

If repository is found to be inconsistent:

a. For Vista and newer, run from elevated command prompt:

Winmgmt /salvagerepository

Note this command will take the content of the inconsistent repository and merge it into the rebuilt repository if it is readable

If the above doesn’t work, then run:

Winmgmt /resetrepository

Note this will reset repository to the initial state when the OS was first installed

For Windows XP and Windows Server 2003, there are no built in switches to rebuild the Repository, so you must do it manually.

Warning: Rebuilding the WMI repository has resulted in some 3rd party products not working until their setup is re-run & their MOF re-added back to the repository.

If /salvagerepository or /resetrepository does not resolve the issue, then manually rebuild repository:

1. 
   
   Change startup type to Window Management Instrumentation (WMI) Service to disabled

1. 
   
   Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service

1. 
   
   Rename the repository folder:  C:\WINDOWS\system32\wbem\Repository to Repository.old

1. 
   
   Open a CMD Prompt with elevated privileges

1. 
   
   CD windows\system32\wbem

1. 
   
   for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s

1. 
   
   Set the WMI Service type back to Automatic and start WMI Service

1. 
   
   cd /d c:\  ((go to the root of the c drive, this is important))

1. 
   
   for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

1. 
   
   Reboot the server

Finally, install latest hotfixes for WMI as they can help prevent issue from recurring. If you continue to have recurring WMI repository corruption issues on same machine, please engage a Microsoft Support Engineer for further troubleshooting and assistance.

[joeperpetua]

[02/02/2021]

Updated link for "WMI: Repository Corruption, or Not?" is: https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-repository-corruption-or-not/ba-... 

[webneticos]

Craig,

of the dozens, almost a hundred blog posts, site articles and YouTube videos that I tried, your solution was the only one that worked.

THANK YOU!

[HermanGB]

Rebuilding WMI in this way will break Hyper-V and HGS.
This is because some crucial mof-files are not located in the wbem directory.

%systemroot%\system32\WindowsVirtualization.V2.mof
%systemroot%\system32\en-us\WindowsVirtualization.V2.mfl
%systemroot%\system32\wbem\HgsClientWmi.mof

I recommend filtering out any .mof or .mfl file that contains the word "uninstall" and "remove". 
If not this will break some Hyper-V stuff such as Get-NetAdapter (missing MSFT_NetAdapter class)

SET "MOF_DIR=%windir%\system32\wbem"

REM Exclude files containing "uninstall" or "Remove"
FOR /F %%s IN ('DIR /B "%MOF_DIR%\*.mof" "%MOF_DIR%\*.mfl" ^| FIND /I /V "uninstall" ^| FIND /I /V "Remove"') DO (
    mofcomp "%%s"
)

[LaPeche]

It is written "This BLOG is no longer valid." but

Do you state it for recents Windows ?

Still relevant for W7 ?