Fix WMI Error 0X0000106D Quickly

WMI error 0X0000106D means a provider's instance set isn't registered. Usually happens after a bad driver install or corrupted repo. Here's the fix, fastest first.

The Short Version (30 Seconds)

Open Command Prompt as admin and run:

winmgmt /verifyrepository

If it says inconsistent, run:

net stop winmgmt
winmgmt /salvagerepository
net start winmgmt

Then restart the WMI service. That fixes about 70% of these errors. If it still fails, move to the next step.

The Moderate Fix (5 Minutes)

The culprit here is almost always a corrupted WMI repository. The salvage command above works when the damage is shallow. For deeper corruption, you need a full rebuild.

First, stop WMI and its dependents:

net stop winmgmt /y

Rename the repository folder — don't delete it, you might need it for recovery:

ren C:\Windows\System32\wbem\Repository Repository.old

Force a fresh repository:

winmgmt /resetrepository

Then register all the MOF files — this is where most guides skip a step. You need to recompile them:

cd /d C:\Windows\System32\wbem
for %i in (*.mof) do mofcomp %i

That loops through every MOF and registers it. Don't bother with selective MOF files unless you know exactly which provider broke — the error text doesn't tell you which one. After the loop finishes, restart the computer. If the error persists, you've got a deeper issue.

The Advanced Fix (15+ Minutes)

Okay, the repository rebuild didn't cut it. That means the problem isn't the repository itself — it's a missing or broken WMI provider binary. The provider that's supposed to register that instance set isn't loading at all.

Open Event Viewer and go to Applications and Services Logs > Microsoft > Windows > WMI-Activity > Operational. Look for events with ID 63 or 64 right around the time the error pops. They'll show you the exact provider DLL or executable that failed. Write down the path.

Once you have the provider path, check if the file exists:

dir "C:\path\to\provider.dll"

No file? Reinstall the software or driver that owns that provider. For example, if it's vmms.exe or vmswitch.sys, you're looking at Hyper-V — run a repair on Hyper-V via Server Manager or reinstall the Hyper-V role.

File exists but error persists? The DLL might be unregistered. Run:

regsvr32 "C:\path\to\provider.dll"

Then restart WMI. Still broken? The provider might be a 32-bit DLL running on a 64-bit system — that's rare but happens with ancient management tools. Use Process Monitor from Sysinternals to see if the DLL is being loaded or blocked.

One more thing — check for antivirus interference. I've seen McAfee and Symantec (yes, still in the wild) quarantine WMI provider DLLs. Check your AV quarantine logs. Restore the file and add an exception for the WMI provider folder.

That's it. Start with the verify command, escalate to the repo rebuild, and only dive into provider hunting if the first two fail. You'll have it fixed within 15 minutes.