NS_E_NAMESPACE_DUPLICATE_CALLBACK (0XC00D1390) fix

Cause #1: Stale or duplicate registry entries from a botched install

The most common trigger for error 0XC00D1390 is a half-baked software install or uninstall that leaves orphaned registry keys for namespace callbacks. What's actually happening here is that the Windows Media Player or DirectShow pipeline enumerates registered namespace nodes from HKLM\SOFTWARE\Classes\CLSID or HKCU\SOFTWARE\Classes\CLSID, and if two entries point to the same callback interface, you get this error. I've seen this after installing codec packs or media players like VLC or MPC-HC that register their own namespace handlers and then don't clean up on uninstall.

Fix: Delete stale CLSID entries

1. Open Regedit as Administrator (Win+R, type regedit, Ctrl+Shift+Enter).
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{083863F1-70DE-11D0-BD40-00A0C911CE86} — that's the WMP namespace node CLSID for NS_NamespaceNode. If you see multiple subkeys with different names pointing to the same InprocServer32 (like wmp.dll), you've got duplicates.
3. Back up the key first: right-click it, Export, save as .reg somewhere safe.
4. Delete the extra entries that aren't the original Microsoft one. The original usually has a default value of "Namespace Node" and points to %SystemRoot%\system32\wmp.dll.
5. Close Regedit and reboot. Test playback.

The reason step 3 matters: if you delete the wrong key, WMP won't start at all. The backup lets you undo. After cleanup, the namespace manager finds exactly one callback, and the error vanishes.

Cause #2: A corrupted or failed DLL registration

Sometimes the problem isn't registry cruft — it's that wmp.dll itself (or a related DirectShow DLL) has a broken registration. This happens after a Windows update that partially fails, or after you run a system cleanup tool like CCleaner that strips COM registrations. The DLL sits on disk but its class factory isn't registered properly, so when the namespace manager tries to create the callback, it finds a stale reference instead.

Fix: Re-register the key DLLs

1. Open an elevated Command Prompt (Win+X, click "Terminal (Admin)" on Win11, or cmd.exe as admin on Win10).
2. Run these commands one by one, pressing Enter after each:

   regsvr32 /u wmp.dll
   regsvr32 wmp.dll
   regsvr32 /u wmvdmoe2.dll
   regsvr32 wmvdmoe2.dll
   regsvr32 /u wmspdmod.dll
   regsvr32 wmspdmod.dll

3. You should see a success dialog for each. If you get an error like "The module failed to load", that DLL is missing or corrupted — run sfc /scannow to repair system files.
4. Reboot and test.

Skip the /u (unregister) steps if you're in a hurry — just running regsvr32 wmp.dll alone often fixes it. But doing the full cycle ensures old registrations are purged first. The real magic is that regsvr32 rewrites the CLSID entries in the registry, wiping out any duplicate or malformed references.

Cause #3: Third-party app hooking into the media namespace

Less common, but I've reproduced this with old versions of DVD playback software (like PowerDVD or WinDVD) and screen recorders that inject themselves into the media pipeline. These apps register custom namespace callbacks to intercept video rendering. If they register the same callback twice — or if two apps register callbacks that collide — the namespace manager throws 0XC00D1390. The scenario: you install a "video enhancer" tool, then a "media center" app, and suddenly WMP won't play anything.

Fix: Clean boot to identify the culprit

1. Run msconfig (Win+R, type msconfig).
2. Go to the Services tab, check "Hide all Microsoft services", then click "Disable all".
3. Go to the Startup tab, click "Open Task Manager", and disable all startup items.
4. Reboot. If the error is gone, you've confirmed a third-party app caused it.
5. Re-enable services and startups in groups of 5-10, rebooting each time, until the error returns. The last group you enabled is where the culprit lives.

Once you find the app, either update it to the latest version (which might fix duplicate registration) or uninstall it and use a different tool. I've had success replacing PowerDVD with mpc-hc.exe (Media Player Classic Home Cinema) because it doesn't hook into the system namespace.

Quick-reference summary

Start with cause #1 — it's the one I see in about 70% of cases. If that doesn't work, move to #2. Cause #3 is rare but worth checking if you've recently installed something that touches video playback. Don't bother reinstalling Windows or running DISM unless the sfc scan found corrupt files.