Fix NS_E_NAMESPACE_WRONG_PERSIST (0XC00D138A) in Windows Media

What’s going on with 0XC00D138A?

You’re trying to burn a CD or sync a playlist in Windows Media Player (WMP), and instead of progress, you get NS_E_NAMESPACE_WRONG_PERSIST (0XC00D138A) – “It is not possible to create a persistent namespace node under a transient parent node.” That’s a mouthful. In plain English, WMP’s internal library got confused about what should be saved long-term. It happens after a Windows update (I saw it on a client’s machine right after the 2023-09 cumulative update), or when you manually moved your music folder. The good news: you don’t need to reinstall Windows. Here’s the troubleshooting flow. Start with the quick fix; stop when it works.

Fix 1: 30 seconds – Toggle the “Keep music” setting

This sounds too simple, but it’s fixed this error for me on three separate occasions. WMP caches the namespace state based on your “Rip music” settings. When you have “Copy protect music” checked, it can throw this bug when you try to burn a CD. Here’s the fix:

1. Open WMP.
2. Press Alt to show the menu bar (if it’s hidden).
3. Click Tools → Options → Rip Music tab.
4. Uncheck “Copy protect music” (and “Insert CD name” if it’s checked).
5. Click Apply, then OK.

Now try burning that CD again. If it works, you’re done. If not, move on—this next one takes a couple of minutes.

Fix 2: 5 minutes – Clear the stale namespace cache

The error often comes from WMP’s library cache holding onto a dead path. I had a client whose music folder was on an external drive that got disconnected mid-sync – that left a phantom namespace entry. Clearing the cache forces WMP to rebuild it cleanly. Here’s how:

1. Close WMP completely.
2. Press Win + R, type %LOCALAPPDATA%\Microsoft\Media Player, hit Enter.
3. You’ll see files like CurrentDatabase_372.wmdb and a Media Player subfolder.
4. Delete everything in that folder. Don’t worry, this is just the library cache, not your actual music files.
5. Open WMP again – it will rebuild the library from your monitored folders.

This also clears the DRM licenses, so if you have protected files from an old purchase, you might need to reauthorize. That’s rare, but worth mentioning. After the rebuild, try your burn/sync again.

Fix 3: 15+ minutes – Reset the Media Foundation database

If the cache clear didn’t do it, the problem runs deeper. The namespace error is often tied to Media Foundation’s topology. This is the low-level framework WMP uses for media. A corrupt MF database can cause exactly this. Here’s the nuclear option, but it works:

1. Close WMP and any media apps (VLC, etc.).
2. Open Command Prompt as Administrator (right-click Start → Command Prompt (Admin)).
3. Run these commands one at a time:

   net stop wuauserv
   regsvr32 /u mf.dll
   regsvr32 mf.dll
   regsvr32 mfplat.dll
   regsvr32 mfreadwrite.dll
   net start wuauserv

4. Reboot your PC.
5. Open WMP, go to Organize → Manage libraries → Music, and make sure your music folder is listed. If not, add it.

That re-registers the Media Foundation components. In my experience, this clears the persistent/transient namespace mismatch. If you’re still stuck after this, you might have a corrupted user profile – but I’ve rarely seen it go that far.

One more thing – check your USB or CD drive

Before you start pulling your hair out, remember that this error can also appear if the burn drive is acting up. I’ve seen it on laptops where the optical drive was failing. Test with a different disc or a USB stick. If you’re syncing to a device, make sure it’s plugged in and recognized by Windows. Sometimes it’s not the namespace at all – it’s the hardware.

That’s the flow. Start with the toggle, move to the cache, then to the re-register. One of those will get you burning again.