How to repair or rebuild the WMI Repository on Windows 11/10

Many a fourth dimension the WMI Repository gets corrupted which results in Provider Load Failure. In this guide, we will share how to repair or rebuild the WMI Repository on Windows eleven/10. For those who aren't aware, Windows Management Instrumentation or WMI is a prepare of specifications from Microsoft to consolidate the direction of devices and applications in a network. It is a database that stores meta-data and definitions for WMI classes. Only by using these, the conditions of the systems tin can be known.

The repository is available here –

%windir%\System32\Wbem\Repository

In brief, it provides end users the status of the local or remote computer system.

Note : Practice not use this on Server 2022 Cluster auto

Repair or rebuild the WMI Repository on Windows

Repair or rebuild the WMI Repository

There are command line tools to fix or reset or restore the WMI repository. All the same, Microsoft suggests that its best that you verify if there is corruption.

Below is a listing of errors and permission issues you might run into-

Unable to connect to root default or rootcimv2 namespaces. Information technology fails with the error lawmaking "0x80041002" pointing to "WBEM_E_NOT_FOUND."
When you open Calculator Management and Correct Click on Computer Management (Local) and select Properties, you get the following error: "WMI: Not Found" or information technology hangs trying to connect
0x80041010 WBEM_E_INVALID_CLASS
Trying to use wbemtest, and it hangs
Schemas/Objects missing
Strange connexion/operation errors (0x8007054e).

The ultimate way to check is to run this command in an elevated Control Prompt.

winmgmt /verifyrepository

If the repository has an upshot, information technology will answer "repository is not consistent," if not so its something else causing the issue. Now that y'all are sure the corruption exists allow's follow these tips to repair or rebuild the WMI repository.

one] Reset WMI Repository

Open up Command Prompt with elevated privileges.

Run the control:

winmgmt /salvagerepository

Then execute the command to see if it now comes dorsum equally consistent-

winmgmt /verifyrepository

If it says that Repository is not consistent, then yous demand to run:

winmgmt /resetrepository

It volition assistance y'all fix the WMI repository. Here is what each of the WMI commands mean:

salvagerepository: This option when used with winmmgmt control performs a consistency check. If an inconsistency is detected, information technology rebuilds the repository.
verifyrepository:Performs a consistency check on the WMI repository.
resetrepository:The repository is reset to the initial country when the operating arrangement is start installed

Hope that explains what happens when you execute the commands.

2] Force Recover WMI

WMI comes with an inbuilt self-recovery process. When the WMI service restarts or detects whatever corruption, the cocky-recovery procedure will trigger automatically. It happens in ii ways:

AutoRestore : Here it will use the backup images if the VSS (Volume Shadow copy) backup is turned on.

AutoRecovery : In this, the rebuilding process will generate fresh images of Repository based on registered MOFs. The MOFS is bachelor in the registry here:

HKLM\Software\Microsoft\WBEM\CIMOM: Autorecover MOFs

Note: Autorecover MOFs is a key. Double-click on it to check the value.

WMI Self-recovery does not work

If the self-recovery doesn't work, you tin can always use the forcefulness-recovery process.

Check regkey value isemptyor non here:

HKLM\Software\Microsoft\WBEM\CIMOM\Autorecover MOFs

If the above regkey is empty, copy-paste the regkey value from some other automobile. Make sure it's from System which is equivalent to the computer in question.

Next, execute the command-

Winmgmt /resetrepository

If you become an fault "WMI repository reset failed. Error code:0x8007041B. Facility: Win32", and so stop all Dependency Services on the WMI service by running the following commands:

net end winmgmt /y  Winmgmt /resetrepository

If both of the suggested fixes don't work, its fourth dimension you try an automated tool.

3] WMI Fixer Tool

repair or rebuild the WMI Repository

This tool will fix Server's WMI Repository when they're corrupted or experiencing related issues. Y'all can download the WMI Fixer Tool from Technet. This tool has at present been taken down, but y'all can download its PowerShell version from Github.com.

Advanced troubleshooting is available here on microsoft.com.

Related: WMI Repository reset failed, Error 0x80070005, 0x8007041B, 0x80041003

How practise I know if my WMI is corrupted?

If WMI is corrupted, you will receive some errors and permission bug with WMI. In such a case, you lot volition see the following errors and symptoms on your computer:

Unable to connect to rootdefault or rootcimv2 namespaces. Fails returning error code 0x80041002 pointing to WBEM_E_NOT_FOUND.
When y'all receive the "WMI. Not Found" error or your computer hangs on opening the properties of Computer Management (Local).
0x80041010 WBEM_E_INVALID_CLASS.
Schemas/Objects missing.
Strange connexion/operation errors (0x8007054e).
Your system hangs every time y'all use the wbemtest utility.

The above errors are the symptoms of WMI abuse. Therefore, to confirm the WMI corruption, you accept to run the following command in an elevated Control Prompt.

winmgmt /verifyrepository

After running the above command, if you receive the message "repository is not consistent," WMI is corrupted. If y'all receive the message "repository is consequent," the repository does not take an issue. In this instance, there is something else causing the consequence.

Related read: WMI is causing High CPU usage.

repair or rebuild the WMI Repository