Fix NS_E_WMPCORE_BUSY (0XC00D10B7) in Windows Media Player

You're listening to a podcast in Windows Media Player (WMP) on Windows 10 or 11. You skip to the next track, and the player freezes. A few seconds later you get: Windows Media Player cannot play the file at this time. The server is busy (0XC00D10B7). Or you just closed a video that crashed, and when you try to play another file, same error. This isn't a corrupt file — it's the player's internal state being stuck.

What causes the 0XC00D10B7 error?

The error code NS_E_WMPCORE_BUSY means the Windows Media Player core engine is locked. The player tried to do something — load a file, switch streams, or update its library — and that operation never finished. So when you ask it to play something new, it says "I'm busy, can't do that now." This happens when:

• You force-close WMP while a file was loading or buffering.
• You rapidly click between files or folders in the library.
• A plugin (like a codec pack) interferes with the playback pipeline.
• The Windows Media Player Network Sharing Service is hung or misconfigured.

Fix it in three steps

Don't reinstall Windows Media Player. Don't run an SFC scan. The fix is simpler than that. Follow these steps in order.

Step 1: Kill the stuck WMP process

The player's still running in the background even if you closed the window. You need to end it completely.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click "More details" at the bottom if you only see a short list.
3. Go to the "Processes" tab. Look for Windows Media Player under "Background processes".
4. Right-click it and select End task. After you do this, the player's icon should disappear from the taskbar and the process list should no longer show it.

If you don't see Windows Media Player listed, look for wmplayer.exe on the "Details" tab instead. Same thing — right-click and end it.

Step 2: Restart the Windows Media Player Network Sharing Service

This service handles library access and streaming. It gets stuck after a crash. Restarting it clears the lock.

1. Press Win + R, type services.msc, and hit Enter.
2. Scroll down to Windows Media Player Network Sharing Service.
3. Right-click it and choose Restart. You'll see the status change from "Running" to "Stopped" and back to "Running". That takes about 5 seconds.
4. Close the Services window.

Step 3: Test playback

Open Windows Media Player again. Play the same file that gave you the error. It should work now. If it doesn't, close WMP and repeat steps 1 and 2 once more — sometimes the background process respawns before the service restarts.

If the error comes back right away

A few people see the error every time they try to play anything. That usually means one of these is the real culprit:

• Corrupted library database. Close WMP. Go to %LOCALAPPDATA%\Microsoft\Media Player in File Explorer. Delete everything in that folder. WARNING: This removes your playlists and playback history, but not your actual media files. Next time you open WMP, it rebuilds the library from scratch. The error will be gone.
• A third-party codec pack. If you installed something like K-Lite Codec Pack or CCCP, uninstall it temporarily. Test WMP playback after a reboot. If the error stops, that codec pack was conflicting. You can try reinstalling a newer version or switching to a different player like VLC for those file types.
• Windows Media Player is trying to access a network location that's slow or offline. If your library includes files on a NAS or network share, disconnect that drive temporarily. The error can happen when WMP tries to scan a network folder that's timing out. Remove the folder from your library in WMP's Organize > Manage Libraries > Music. Add it back only after confirming the network share is stable.

That's it. The 0XC00D10B7 error is a nuisance, not a sign of a broken system. Kill the process, restart the service, and you're back to listening. Skip the complicated registry edits — they don't fix this one.