Fix NS_E_NAMESPACE_NODE_NOT_FOUND (0XC00D138D) Error

What's triggering this error?

You're trying to open a playlist or library in Windows Media Player and you get slapped with NS_E_NAMESPACE_NODE_NOT_FOUND (0XC00D138D). It usually happens after a crash, a failed sync with a portable device, or when you've manually moved or deleted media files that the player was tracking. I've seen it on Windows 10 version 22H2 and Windows 11 after a Windows Update that hosed the library database. It's infuriating because the player won't let you do anything until it's fixed.

Let's walk through the fixes, from easiest to most involved. Try each one in order — stop when the error goes away.

Fix 1: Quick reset of the current playlist (30 seconds)

This is the fastest fix and often works if the error is tied to a single playlist.

1. Close Windows Media Player completely.
2. Open File Explorer and type %USERPROFILE%\Music\Playlists into the address bar, then press Enter.
3. Look for any .wpl or .zpl files you don't need. Delete them — especially ones you didn't create yourself (like auto-generated sync playlists). Then restart Windows Media Player.

If the error is gone, you're done. If not, move to the next step.

Fix 2: Clear the media library cache (5 minutes)

Windows Media Player stores metadata and playlist info in a database file. If that file gets corrupted, you'll see the 0XC00D138D error. Deleting it forces the player to rebuild the library from scratch.

1. Close Windows Media Player completely. Check Task Manager to make sure no WMP processes are running (look for wmplayer.exe).
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, and hit Enter.
3. You'll see several folders with long gibberish names and a file called CurrentDatabase_*.wmdb. Delete the entire contents of this folder. Don't worry — Windows will recreate everything when you restart the player.
4. Restart Windows Media Player. It'll take a minute or two to rebuild the library, scanning your Music, Videos, and Pictures folders. The error should be gone after that.

I've used this fix on dozens of machines. It's the one that works for about 80% of users. If it didn't work for you, the issue is deeper.

Fix 3: Repair or reinstall Windows Media Player (15+ minutes)

If the database reset didn't help, the WMP installation itself might be damaged. On Windows 10 and 11, you can't uninstall WMP normally — it's a Windows Feature. But you can turn it off and back on again.

1. Open Control Panel (search for it in the Start menu).
2. Go to Programs > Turn Windows features on or off.
3. In the list, find Media Features and expand it. Uncheck Windows Media Player. Click OK and restart your PC.
4. After the restart, go back to the same place and re-check Windows Media Player. Click OK and restart again.

This reinstalls WMP cleanly. You'll lose any custom settings or playlists you had, but the error will be gone.

If that still fails — use the DISM tool

Sometimes the system files behind WMP are corrupt. Run these commands from an elevated Command Prompt:

dism /online /cleanup-image /restorehealth
sfc /scannow

Let both complete. Restart, then try the Windows Features toggle again. I've had this clean up stubborn corruption on a Surface Pro 7 where nothing else worked.

Last resort: Switch to a different media player

Look, I love Windows Media Player for its simplicity, but it hasn't seen real updates in years. If you're still seeing 0XC00D138D after all this, it might be time to move on. VLC Media Player is free, handles everything, and won't throw obscure namespace errors. Install it, point it to your media folders, and don't look back.

But if you're determined to stay with WMP, a clean Windows reset (keeping your files) will fix it — though that's a nuclear option I'd only recommend if you're already planning to reinstall the OS.

That's it. The 30-second fix, the 5-minute fix, and the 15-minute fix. Start with the quick one — I bet it saves you time.