Fix ERROR_WMI_SERVER_UNAVAILABLE (0x00001070)

What triggers this error

This error pops up when management tools (like Server Manager, Configuration Manager, or PowerShell scripts using Get-WmiObject) can't connect to WMI. You'll usually see it after a Windows Update, a failed service stop, or disk-full condition on the system drive.

The real fix depends on why WMI went down. Let's work through it from easiest to hardest.

First fix: Restart the WMI service (30 seconds)

1. Open Command Prompt or PowerShell as Administrator.
2. Type net stop winmgmt and press Enter. Wait—it might take 10 seconds. You should see The Windows Management Instrumentation service was stopped successfully.
3. Then type net start winmgmt. You should see The Windows Management Instrumentation service started successfully.
4. Now test your management tool again. If the error is gone, you're done. If not, move to the next fix.

Why this works sometimes: A temporary glitch or stuck process can freeze WMI. Restarting the service clears that state.

Second fix: Check WMI dependencies and re-register providers (5 minutes)

If the service starts but errors come back, dependencies are likely missing or a provider is corrupt.

Step 1: Verify dependencies

1. Run services.msc.
2. Find Windows Management Instrumentation, right-click, choose Properties.
3. Check the Dependencies tab. It lists services that must be running: RPC Endpoint Mapper and Remote Procedure Call (RPC). Both should be Running.
4. If either is stopped, start it and set it to Automatic.

Step 2: Re-register core WMI components

1. Open an elevated Command Prompt.
2. Run these commands one at a time:

   regsvr32 /s wmi.dll
   regsvr32 /s wbemprox.dll
   regsvr32 /s wbemcomn.dll
   regsvr32 /s wbemsvc.dll

3. You shouldn't see any errors. Each should return DllRegisterServer succeeded silently.
4. Restart the winmgmt service: net stop winmgmt then net start winmgmt.

Step 3: Reset the WMI repository without losing data

This re-reads all MOF files and providers. It's safe and often fixes partial corruption.

1. As Administrator, run winmgmt /resetrepository.
2. Wait for the message: WMI repository is consistent. No action taken. or Repository successfully reset.
3. Restart the service again: net stop winmgmt then net start winmgmt.

Test your tool. Still broken? The repository itself is probably corrupt—time for the heavy fix.

Third fix: Rebuild the WMI repository from scratch (15+ minutes)

This wipes the repository and recompiles it from MOF files. Run this only if the first two fixes failed—it resets custom WMI namespaces and can break third-party tools that store data in WMI (like antivirus or backup software). Back up the repository first if possible.

Step 1: Stop WMI and disable it temporarily

1. Open Command Prompt as Administrator.
2. Run:

   net stop winmgmt /y

   The /y flag stops dependent services. You might see a warning—that's fine.
3. Rename the repository folder to preserve it:

   rename %windir%\System32\wbem\Repository Repository.old

Step 2: Recompile the repository

1. Change to the wbem folder:

   cd /d %windir%\System32\wbem

2. Re-register all DLLs and recompile MOF files with this one-liner:

   for /f %i in ('dir /b /s *.dll') do regsvr32 /s %i

   Important: This takes 2–5 minutes. Let it finish—don't close the window.
3. Then compile the core MOF files:

   mofcomp.exe cimwin32.mof
   mofcomp.exe cimwin32.mfl
   mofcomp.exe rsop.mof
   mofcomp.exe wmi.mof

   You should see MOF file has been successfully parsed for each.

Step 3: Verify the repository is clean

1. Start the WMI service:

   net start winmgmt

2. Check the Event Viewer under Applications and Services Logs > Microsoft > Windows > WMI-Activity > Operational for Event ID 10 or 11—those indicate a problem. If none appear, you're good.
3. Run a quick test:

   wbemtest

   Click Connect, leave the namespace as root\default, and click Connect. If it connects without error, WMI is working.

Still not working? Check if the Windows Management Instrumentation service is set to Automatic and not Disabled by group policy. Also verify that the WMI Performance Adapter service is running. On Server 2019, I've seen a missing hotfix cause this—check your Update history for KB5009624 or later.

When to call it quits and restore

If you rebuilt the repository and still see the error, the system files themselves might be corrupt. Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth before giving up. Only restore from backup if you're sure the corruption isn't caused by a faulty driver or third-party tool that keeps re-corrupting the repo.