How to repair or rebuild the WMI Repository on Windows 10

Many a fourth dimension the WMI Repository gets corrupted which results inwards Provider Load Failure. In this guide, nosotros volition portion how to repair or rebuild the WMI Repository on Windows 10. Those who aren’t aware, Windows Management Instrumentation or WMI is a laid of specifications from Microsoft to consolidate the administration of devices too applications inwards a network. It is a database which stores meta-information too definitions for WMI classes. Only using these, the weather of the systems tin move known.

The repository is available hither –

%windir%\System32\Wbem\Repository

In brief, it provides halt users the status of the local or remote estimator system.

Note: Do non role this on Server 2012 Cluster machine

Repair or rebuild the WMI Repository on Windows

There are ascendence work tools to ready or restore the WMI repository. However, Microsoft suggests that its best that yous verify if in that place is corruption.

Below is a listing of errors too permission issues yous mightiness see-

1. Unable to connect to rootage default or rootcimv2 namespaces. It fails amongst the fault code “0x80041002” pointing to “WBEM_E_NOT_FOUND.”
2. When yous opened upwards Computer Management too Right Click on Computer Management (Local) too pick out Properties, yous become the next error: “WMI: Not Found” or it hangs trying to connect
3. 0x80041010 WBEM_E_INVALID_CLASS
4. Trying to role wbemtest, too it hangs
5. Schemas/Objects missing
6. Strange connection/operation errors (0x8007054e).

The ultimate means to banking concern stand upwards for is to run this ascendence inwards an elevated Command Prompt.

winmgmt /verifyrepository

If the repository has an issue, it volition reply “repository is non consistent,” if non too thence its something else causing the issue. Now that yous are certain the corruption exists let’s follow these tips to repair or rebuild the WMI repository.

1] Reset WMI Repository

Open Command Prompt amongst elevated privileges.

Run the command:

winmmgmt /salvagerepository

Then execute the ascendence to come across if it instantly comes dorsum every bit consistent-

winmgmt /verifyrepository

If it says that Repository is non consistent, too thence yous demand to run:

winmgmt /resetrepository

It volition aid yous ready the WMI repository. Here is what each of the WMI commands mean:

• salvagerepository: This alternative when used amongst winmmgmt ascendence performs a consistency check. If an inconsistency is detected, it rebuilds the repository.
• verifyrepository: Performs a consistency banking concern stand upwards for on the WMI repository.
• resetrepository: The repository is reset to the initial state when the operating arrangement is commencement installed

Hope that explains what happens when yous execute the commands.

2] Force Recover WMI

WMI comes amongst an inbuilt self-recovery process. When the WMI service restarts or detects whatever corruption, the self-recovery physical care for volition trigger automatically. It happens inwards ii ways:

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

AutoRecovery: In this, the rebuilding physical care for volition generate fresh images of Repository based on registered MOFs. The MOFS is available inwards the registry here:

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

Note: Autorecover MOFs is a key. Double-click on it to banking concern stand upwards for the value.

WMI Self-recovery does non work

If the self-recovery doesn’t work, yous tin e'er role the force-recovery process.

Check regkey value is empty or not here:

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

If the above regkey is empty, copy-paste the regkey value from unopen to other machine. Make certain it’s from System which is equivalent to the estimator inwards question.

Next, execute the command-

Winmgmt /resetrepository

If yous become an fault “WMI repository reset failed. Error code:0x8007041B. Facility: Win32”, too thence halt all Dependency Services on the WMI service past times running the next commands:

net halt winmgmt /yWinmgmt /resetrepository

If both of the suggested fixes don’t work, its fourth dimension yous endeavour an automated tool.

3] WMI Fixer Tool

This tool volition ready Server’s WMI Repository when they’re corrupted or experiencing related issued. You tin download the WMI Fixer Tool from Technet.

Related read: WMI is causing High CPU usage.

Source: https://www.thewindowsclub.com/

Share This :