Windows WMI Repository Errors — WMI Corruption and Repair Guide
About Windows WMI Repository Errors
Fix Windows Management Instrumentation (WMI) repository corruption causing Group Policy failures, SCCM issues, and system management tool errors. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: WMI (Windows Management Instrumentation) provides system management data to tools and scripts. A corrupted WMI repository can break Group Policy, SCCM, monitoring tools, and PowerShell Get-WmiObject. Symptoms: Event ID 10, WMI errors in Event Viewer, Get-WmiObject returning errors. The WMI repository is stored in C:\Windows\System32\wbem\Repository. Microsoft discourages manual repository rebuilds as they can cause more problems. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: WMI repository corruption from improper shutdown or disk errors. Conflicting WMI providers installed by third-party software. Failed Windows Update modifying WMI components. Antivirus quarantining WMI-related files. Manual deletion of files in the wbem\Repository folder. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Verify WMI health: winmgmt /verifyrepository in elevated Command Prompt. If inconsistent: winmgmt /salvagerepository (attempts to salvage what it can). If salvage fails: winmgmt /resetrepository (resets to initial state — last resort). Restart WMI service: net stop winmgmt && net start winmgmt. Re-register WMI DLLs: for %i in (%windir%\system32\wbem\*.dll) do RegSvr32 -s %i. Check Event Viewer for Event ID 10 (WMI errors) to identify specific failing queries. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
What breaks when WMI is corrupted?
Many things: Group Policy processing, SCCM management, hardware monitoring, PowerShell system queries, and any application using WMI for system information. The impact is wide.
Overview
Fix Windows Management Instrumentation (WMI) repository corruption causing Group Policy failures, SCCM issues, and system management tool errors.
Key Details
- WMI (Windows Management Instrumentation) provides system management data to tools and scripts
- A corrupted WMI repository can break Group Policy, SCCM, monitoring tools, and PowerShell Get-WmiObject
- Symptoms: Event ID 10, WMI errors in Event Viewer, Get-WmiObject returning errors
- The WMI repository is stored in C:\Windows\System32\wbem\Repository
- Microsoft discourages manual repository rebuilds as they can cause more problems
Common Causes
- WMI repository corruption from improper shutdown or disk errors
- Conflicting WMI providers installed by third-party software
- Failed Windows Update modifying WMI components
- Antivirus quarantining WMI-related files
- Manual deletion of files in the wbem\Repository folder
Steps
- 1Verify WMI health: winmgmt /verifyrepository in elevated Command Prompt
- 2If inconsistent: winmgmt /salvagerepository (attempts to salvage what it can)
- 3If salvage fails: winmgmt /resetrepository (resets to initial state — last resort)
- 4Restart WMI service: net stop winmgmt && net start winmgmt
- 5Re-register WMI DLLs: for %i in (%windir%\system32\wbem\*.dll) do RegSvr32 -s %i
- 6Check Event Viewer for Event ID 10 (WMI errors) to identify specific failing queries