How to Rebuild the WMI Repository in Windows

This guide walks you through verifying and rebuilding the Windows Management Instrumentation (WMI) repository when it becomes corrupted, which can break system tools, third-party software, and event logging. You will learn how to check its health, re-register components, and, if needed, force a rebuild using built-in commands — no third-party tools required.

What You’ll Need

An account with Administrator privileges (local admin is fine).
Command Prompt or PowerShell opened as Administrator.
About 10–15 minutes; the rebuild process may take a few minutes.
Optional: a backup of the current repository if you want to restore it later (the process creates one automatically, but manual backup is safer).

Step-by-Step

Open an elevated Command Prompt. Press Windows+X and select “Command Prompt (Admin)” or “Windows PowerShell (Admin)”. Click “Yes” if prompted by UAC.
Check the current WMI status. Run winmgmt /verifyrepository. If it returns “WMI repository is consistent”, the repository is likely fine — try other fixes before rebuilding. If it says “inconsistent”, proceed.
Stop the WMI service. Run net stop winmgmt. This also stops dependent services; they will restart automatically.
Back up the repository (optional but recommended). Rename the folder to keep a copy: ren C:\Windows\System32\wbem\Repository Repository.old. If the rename fails, ensure no other process is using the folder (close WMI-related tools).
Rebuild the repository. Run winmgmt /resetrepository. This recreates the repository from scratch using default MOF files. Wait for it to complete; it may take a few minutes.
Restart the WMI service. Run net start winmgmt.
Verify the rebuild. Run winmgmt /verifyrepository again. It should now report “consistent”.
Re-register WMI components (if issues persist). In the same elevated prompt, run these commands one by one:
1. cd /d C:\Windows\System32\wbem
2. for /f %s in ('dir /b *.dll') do regsvr32 /s %s
3. for /f %s in ('dir /b *.exe') do %s /RegServer
This re-registers all WMI DLLs and executables. Ignore any “module not found” errors — they are normal.
Reboot the computer. Restart to ensure all services and dependent components load fresh.

Common Mistakes

Skipping the verification step. Rebuilding when the repository is actually fine can cause more harm than good — you lose custom WMI settings.
Not running as Administrator. The commands will fail with “Access denied” if your prompt isn’t elevated.
Deleting the Repository folder instead of renaming. If you delete it and the rebuild fails, you have no backup. Always rename first.
Forgetting to stop the service. The rebuild may fail with “The WMI service is already running”.
Interrupting the reset. Closing the window during winmgmt /resetrepository can leave the repository half-built. Let it finish.

Tips

Run a full system file check first. Corrupted system files can cause WMI issues. Run sfc /scannow in an elevated prompt, then DISM /Online /Cleanup-Image /RestoreHealth before rebuilding the repository.
Use the built-in backup. The winmgmt /backup command creates a backup to a file (e.g., winmgmt /backup C:\wmi_backup.bak). You can restore with winmgmt /restore.
Check event logs. After the rebuild, look in Event Viewer under “Applications and Services Logs > Microsoft > Windows > WMI-Activity” for errors that might indicate lingering issues.
Update Windows. Sometimes WMI corruption is fixed by a cumulative update. Install all pending updates before attempting a rebuild.

Troubleshooting

If the rebuild fails with “The WMI service could not be stopped”: Force stop it with taskkill /f /im WmiPrvSE.exe and then net stop winmgmt. If that still fails, reboot into Safe Mode (with Networking) and repeat the steps there.

If winmgmt /resetrepository returns “Access denied”: Make sure your prompt is truly elevated. Right-click the Command Prompt icon and select “Run as administrator”.

If the repository still shows “inconsistent” after the rebuild: The problem may be with a third-party WMI provider. Check the WMI-Activity event log for the provider name, then uninstall or update that software. You can also try re-registering the provider’s DLL manually.

If services that depend on WMI (like Windows Firewall or System Restore) fail to start: Run winmgmt /verifyrepository again — if it’s consistent, reboot and try again. If it’s still inconsistent, you may need to do a full repair install of Windows (using the “Reset this PC” option that keeps your files).

Frequently Asked Questions

Will rebuilding the WMI repository delete my personal files?

No. The repository only stores WMI configuration data, not user files. Your documents, photos, and other personal data are untouched.

Do I need to reinstall software after a rebuild?

Usually not. Most software will recreate its WMI entries automatically when it runs. If a specific program still reports WMI errors, reinstall that program to restore its provider.

How often should I rebuild the WMI repository?

Only when it’s corrupted. Rebuilding unnecessarily can remove custom WMI namespaces or settings that you or your software rely on. Always verify first.

Can I rebuild the WMI repository on Windows 10 and Windows 11?

Yes, the steps are identical for Windows 10, Windows 11, and Windows Server 2016 and later. The commands are the same.

What causes WMI repository corruption in the first place?

Common causes include improper shutdowns, disk errors, malware, or bugs in third-party WMI providers. A failing hard drive can also corrupt the repository, so check disk health with chkdsk if problems persist.

Is there a way to repair the WMI repository without using Command Prompt?

No, the built-in repair tools are command-line only. However, you can use PowerShell with the same commands (e.g., winmgmt /verifyrepository works in PowerShell). Some third-party tools offer a GUI, but they are not necessary.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →