How to Rebuild the WMI Repository. (4040113)

The Windows Management Instrumentation (WMI) Repository, located at "%windir%System32\Wbem\Repository," stores meta-information and definitions for WMI classes. In some cases, it also stores static class data. If the WMI Repository becomes corrupted, the WMI service will not function correctly.

Rebuilding the WMI Repository should be a last resort, as it can cause system or application damage. Other troubleshooting steps should be taken first to eliminate other possibilities or confirm repository corruption. A large WMI Repository may cause issues that resemble corruption but are not. If this is the case, rebuilding is the only method to reduce the repository size.

It is advisable to capture a WMIDiag report for any WMI-related issues.

Symptoms

If the WMI Repository is corrupted, you may encounter various errors depending on the activity being performed. Examples include:

• Core console showing agent's disks as empty
• Unable to protect agent due to issues getting agent metadata
• Errors in agent logs indicating issues with metadata summary retrieval

Trying to protect an agent you may see the following error in the agent logs:

ERROR 2023-10-26T21:57:16 Replay.ServiceHost.Implementation.Hosting.ServiceHost (RequestUri=https://AgentName:8006/apprecovery/api/agent/metadata/summaryMetadata ClientAddress=xxx.xxx.xxx.xxx:55248)

Service Host Error: Service error while handling request [PUT https://AgentName:8006/apprecovery/api/agent/metadata/summaryMetadata]: Not found

Request Uri: https://AgentName:8006/apprecovery/api/agent/metadata/summaryMetadata

Client Address: xxx.xxx.xxx.xxx:55248

Identity: DOMAIN\UserName

Service: Replay.Agent.Management.Metadata.AgentMetadataManagement

Method: GetCurrentSummary

System.Management.ManagementException depth 0: Not found  (0x80131501)

WMI Repository corruption can be indicated by the following scenarios/errors:

• Unable to connect to root\default or root\cimv2 namespaces using wbemtest (error code 0x80041002, WBEM_E_NOT_FOUND)
• Errors when opening Computer Management and selecting Properties (e.g., "WMI: Not Found" or connection hangs)
• Error code 0x80041010 (WBEM_E_INVALID_CLASS)
• wbemtest hangs
• Error "Provider not found" when protecting an agent

How to Test WMI

You can test WMI using wbemtest or a PowerShell command. Refer to Knowledge Article Using WBEMTEST to test DCOM and WMI connections to remote Windows systems (4033088) (quest.com) for step-by-step instructions on testing WMI locally and remotely.

Actions to Try First

1. Re-register DLLs and Recompile MOFs
   • Open Notepad and save the following script as a .bat file and run it from an elevated command prompt in the directory C:\Windows\System32\Wbem:
   • :: Start of WMI reset
     @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
     dir /b *.mof *.mfl | findstr /v /i uninstall > moflist.txt & for /F %%s in (moflist.txt) do mofcomp %%s
     :: End of WMI reset
2. Reboot the Machine and Test WMI

Checking the WMI Repository

1. Verify Repository Consistency

   • Run the following command from an elevated command prompt:
     winmgmt /verifyrepository

2. Salvage Repository

   • If the WMI Repository is inconsistent, run:
     winmgmt /salvagerepository
   • This command merges the content of the inconsistent repository into the rebuilt repository if it is readable.

3. Reset Repository

   • If salvaging doesn't work, run:
     winmgmt /resetrepository
   • This resets the WMI Repository to its initial state when the OS was first installed.
   
    
4. If /salvagerepository or /resetrepository does not resolve the issue, then proceed to rebuild the WMI repository or ask Microsoft Support to troubleshoot WMI.

1. Open services.msc and change the startup type to Window Management Instrumentation (WMI) Service to 'Disabled'.
2. Open an elevated command prompt: Click on the Start menu, search for "cmd," right-click on "Command Prompt," and choose "Run as administrator."
3. 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. To stop the service, type the following command and press Enter: net stop winmgmt
4. Rename the WMI repository folder: Type the following command and press Enter: ren %windir%\System32\wbem\Repository Repository.old
5. Change to the wbem directory. Type the following command and press Enter: cd windows\system32\wbem
6. Re-register dll's. Type the following command and press Enter: for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
7. Open services.msc and set the WMI Service type back to 'Automatic' and start WMI Service
8. Change directory to the root of the C: drive (this is important)). Type the following command and press Enter: cd /d c:\ 
9. Re-compile WMI components. Type the following command and press Enter: for /f %s in ('dir /s /b *.mof *.mfl') do mofcomp %s
10. Close Command Propmt and Reboot the server.

Final Steps

• Install the latest hotfixes for WMI to prevent recurrence.
• If issues persist, engage a Microsoft Support Engineer for further troubleshooting.

Notes

Rebuilding the WMI Repository may require reinstalling third-party applications and re-adding their MOF files to the repository.