0XC00D1B7D

Fix NS_E_NOSTATSAVAILABLE (0XC00D1B7D) on Windows

Windows Errors Intermediate 👁 2 views 📅 Jun 6, 2026

Windows can't grab network stats? This error usually means the WMI stats service is hung or corrupt. Here's how to kick it back to life.

What's actually happening here

The error NS_E_NOSTATSAVAILABLE (0XC00D1B7D) pops up in Windows Media Player when it tries to fetch network statistics—like buffering status or connection speed—from the underlying system. Windows uses the Windows Management Instrumentation (WMI) service to provide those real-time metrics. If that service is hung, corrupted, or the repository it reads from is borked, you get this error instead of data.

I've seen this most often on Windows 10 22H2 and Windows 11 23H2 after a Windows Update that didn't fully reset the WMI provider, or after third-party optimization tools nuked parts of the repository. You might also see it in event logs as a 0xC00D1B7D source from WMP. The fix chain goes from a 30-second service restart to a 15-minute repository rebuild. Stop when it works.

Step 1: Restart the WMI service (30 seconds)

This is the quickest fix and resolves about 40% of cases. The service is probably just stuck in a bad state.

  1. Open an admin Command Prompt. Hit Win+X, select Terminal (Admin) or Command Prompt (Admin).
  2. Run:
    net stop winmgmt && net start winmgmt
  3. Wait 5 seconds, then open Windows Media Player and try to play a network stream.

Why this works: Stopping and starting the WMI service forces it to reload its provider DLLs and re-read the repository. If a provider was holding a lock or timing out, this clears it. If you still see the error, move on.

Step 2: Re-register WMI components (5 minutes)

If the service restarts happily but the error persists, the WMI provider DLLs themselves might be unregistered (common after a bad .NET update).

  1. In the same admin terminal, run these commands one by one:
    regsvr32 /s wbemupgd.dll
    regsvr32 /s wbemcore.dll
    regsvr32 /s wbemcons.dll
    regsvr32 /s wbemdisp.dll
    regsvr32 /s wbemprox.dll
    regsvr32 /s wbemsvc.dll
    regsvr32 /s wbemtran.dll
    regsvr32 /s wmidc.dll
    regsvr32 /s wmiutils.dll
  2. Run this to recompile the managed WMI assemblies:
    mofcomp.exe wbemcore.mof
  3. Restart the WMI service again: net stop winmgmt && net start winmgmt
  4. Test Windows Media Player.

What you're doing here: regsvr32 tells each DLL to register its COM interfaces and entry points in the registry. The mofcomp command recompiles the core WMI schema. Without these, WMI can't answer queries for network stats—so Media Player gets nothing. This fixes maybe another 30% of cases.

Step 3: Reset the WMI repository (15 minutes)

This is the nuclear option. If neither of the above works, the repository itself—the file where WMI stores its data—is corrupt. You'll need to rebuild it from scratch. This doesn't affect your system stability, but it will reset any custom WMI namespaces third-party apps might have installed (rare outside enterprise environments).

  1. Open admin Command Prompt.
  2. Stop the WMI service:
    net stop winmgmt /y
  3. Rename the repository folder—keeps a backup in case you need to revert:
    ren %windir%\System32\wbem\Repository Repository.bak
  4. Restart the service—Windows auto-creates a fresh repository:
    net start winmgmt
  5. Force a full repository rebuild with the built-in schema files:
    winmgmt /resetrepository
    (Note: On Windows 10/11, this command sometimes returns "Access denied" if UAC isn't bypassed—if so, skip it; the auto-create in step 4 is usually enough.)
  6. Reboot your machine. Then test Media Player.

The reason step 3 works: The WMI repository lives in C:\Windows\System32\wbem\Repository. When it gets corrupted—often from a power loss during a WMI write, or a failed Windows Update—every query returns nothing or an error. By renaming it and letting Windows rebuild it, you get a clean slate. The schema is re-derived from the .MOF files in the same folder, so all standard functionality (including network stats) comes back.

Step 4: Check for deeper corruption (advanced, last resort)

If you're still seeing the error after Step 3, the problem isn't isolated to WMI. Run these checks from an admin terminal:

  • System File Checker: sfc /scannow — Takes 10-15 minutes. This repairs corrupted system files that might be pulling down WMI providers.
  • DISM health restore: DISM /Online /Cleanup-Image /RestoreHealth — Fixes the component store that SFC relies on. Run this if sfc finds errors it can't fix.

Skip these unless you're desperate. They rarely directly fix this specific error—most cases are resolved by Step 1 or 2. But if your system has broader issues, this catches them.

Prevention: Stop the rot

To avoid seeing this error again:

  • Don't use registry cleaners or WMI optimizers. They frequently unregister providers or truncate the repository.
  • Keep Windows Update current. Microsoft has patched several WMI deadlock bugs over the years (KB5034441 for Win11, KB5034440 for Win10).
  • If you use Media Player with network streams regularly, set the WMI service to Automatic (non-delayed) start in services.msc. Delayed start can cause race conditions where WMP queries stats before the service is fully up.

When the error isn't WMI

In rare cases, 0XC00D1B7D appears because the network source doesn't support statistics at all—like an old RealAudio stream or a direct MP3 link. Media Player then reports "no stats available" because the server never sent any. Test with a known-good stream like http://icecast.somafm.com/groovesalad-128 to rule this out. If that works, the error is specific to your original URL, not your system. No fix needed.

Was this solution helpful?