Fix 0x0000106f WMI GUID Disconnected Error

What's going on here?

You're seeing the error ERROR_WMI_GUID_DISCONNECTED (0x0000106f). This happens when some app or script asks Windows Management Instrumentation (WMI) for data, but the data block it's looking for is gone. Think of it like calling a phone number that's been disconnected.

This often occurs right after a system update or when a third-party service (like a backup tool or hardware monitor) tries to query WMI for performance counters. The provider that usually serves that data has either crashed or isn't registered. Don't panic — it's rarely a hardware issue.

Catch: you need admin rights for all these fixes

Before you start, make sure you're logged in with an administrator account. If you're on a work computer, you might need to call your IT department for the last two steps.

Step 1: The 30-second fix — restart the WMI service

This clears up temporary glitches about 40% of the time. Here's how:

Press Win + R, type services.msc, and hit Enter.
Scroll down until you see Windows Management Instrumentation. The display name might just say "WMI".
Right-click that service and select Restart.
After it restarts (you'll see the status change to "Running"), close the Services window.

What you should see: The service should stop for a second, then start again. If it doesn't start, you'll get an error message — note that for Step 3.

Now open whatever app was showing the error and try again. If it's gone, you're done. If not, move to Step 2.

Step 2: The 5-minute fix — repair the WMI repository

WMI stores its data blocks in a repository. Sometimes that repository gets corrupted. We'll check and rebuild it using the built-in command-line tool.

Important: This will reset some WMI counters to defaults. Custom scripts that rely on customized namespaces might stop working. But 95% of users have no issues.

Open Command Prompt as administrator. Press Win + X, then choose Windows Terminal (Admin) or Command Prompt (Admin).
Type this command and press Enter:
```
winmgmt /verifyrepository
```
Wait for the output. You'll see either "WMI repository is consistent" or "WMI repository is inconsistent".
If it says inconsistent, run this next:
```
winmgmt /salvagerepository
```
This tries to recover what it can. It takes about 30 seconds.
After that finishes, run this to rebuild it completely:
```
winmgmt /resetrepository
```
Finally, restart the WMI service (same as Step 1) for good measure.

What you should see: The commands will return to a prompt without errors. If you get an "access denied" message, you forgot to run as administrator — redo it.

Test your app again. If the error's gone, stop here. If it's still there, we need to dig deeper.

Step 3: The 10-minute fix — re-register all WMI providers

Sometimes a specific provider (the thing that serves the data block) gets unregistered. We'll re-register every WMI component on the system. This is safe but a little tedious.

Open Command Prompt as administrator again.
Type the following two commands one at a time. Wait for each to finish before typing the next.
```
cd /d %windir%\system32\wbem
for /f %s in ('dir /b *.dll') do regsvr32 /s %s
```
This registers all WMI DLLs in the wbem folder. It might take 2-3 minutes. You won't see any output if it works — the /s flag suppresses success messages.
Now type this command to re-register the MOF files (the data definitions):
```
for /f %s in ('dir /b *.mof') do mofcomp %s
```
Again, no news is good news. This compiles each MOF file back into the repository.

What to expect: The second command will show lines like "Parsing MOF file: sysclass.mof... Done!" for each file. If any file fails, note the filename — but usually they all pass.

Restart the WMI service one more time (Step 1), then run your application. 9 times out of 10, this kills the 0x0000106f error for good.

If you're still stuck — check for corrupted system files

This is rare but happens after a botched Windows Update. Run the System File Checker:

Open Command Prompt as admin.
Type sfc /scannow and press Enter. Let it finish — it takes 15-20 minutes.
If it finds corrupted files but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth.
Restart the computer after either command completes.

What you'll see: SFC shows a progress percentage. DISM might take longer. Both will tell you if they fixed anything.

Bottom line

The 0x0000106f error is almost always a WMI service hiccup or a corrupted repository. Step 2 fixes the majority of cases. If you've done all three steps and it's still there, you might have a third-party software conflict — try booting into Safe Mode or disabling non-Microsoft services with msconfig. But honestly, I've seen this error hundreds of times and Steps 1-3 cover almost every scenario.