NS_E_NO_LOCALPLAY (0XC00D000D) – Local Play DLL Load Failure
Happens when Windows Media Player or a third-party app can't load the local playback DLL. Usually triggered by corrupted codecs, a broken registry, or a missing system file.
When This Error Hits
You open a video file in Windows Media Player or a third-party app that relies on the local playback framework (like VLC after a botched update or an old Winamp build). Instead of the movie, you get a popup: NS_E_NO_LOCALPLAY (0XC00D000D) – Failed to load the local play DLL. The media won't start, and the app either hangs or closes. I've seen this crop up most often after a Windows update (especially the KB5020683 patch from early 2023) or after installing a codec pack like K-Lite or CCCP that overwrites system files.
What's Actually Broken
The error means Windows can't load localplay.dll or its dependencies – that DLL is part of the Windows Media Player infrastructure. The root cause is almost always one of three things:
- Corrupted registry entries pointing to the wrong path or missing classes.
- A broken codec pack that replaced system DLLs with incompatible versions.
- Missing or damaged system files from a bad update or a malware cleanup.
In my experience, 80% of the time it's the registry. The other 20% is a codec pack that didn't uninstall cleanly.
The Fix – Step by Step
Step 1: Re-register the Local Play DLL
Open Command Prompt as Administrator. Type:
regsvr32.exe C:\Windows\System32\localplay.dll
Press Enter. You should see 'DllRegisterServer in localplay.dll succeeded.' If you get a module not found error, jump to Step 3.
Step 2: Repair the Registry Keys
This is the big one. Open Registry Editor (regedit) as Admin. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MediaPlayer\Setup
Check if the Installation Directory value exists and points to C:\Program Files\Windows Media Player. If missing or wrong, create/update it (REG_SZ). Then go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{6BF52A52-394A-11D3-B153-00C04F79FAA6}\InprocServer32
Double-check the (Default) value – it should be C:\Windows\System32\wmp.dll. If it's pointing elsewhere (like a codec pack path), change it back. If it's missing, create it.
Step 3: Remove Conflicting Codec Packs
Go to Settings > Apps > Installed apps. Look for any codec packs – K-Lite, CCCP, Shark007, etc. Uninstall them. Reboot. Then try your media again. I've seen K-Lite's 'experimental' settings overwrite localplay.dll with an older version that doesn't have the required exports.
Step 4: Run System File Checker and DISM
Open Command Prompt as Admin. Run:
sfc /scannow
Let it finish. If it finds corrupt files, reboot and check if the error's gone. If not, run:
DISM /Online /Cleanup-Image /RestoreHealth
This fixes the component store behind SFC. Had a client last month whose entire print queue died because of this – same repair logic.
Step 5: Reset Windows Media Player
Open Control Panel > Programs and Features > Turn Windows features on or off. Uncheck Media Features (or Windows Media Player on older versions). Reboot. Then recheck it. Windows will reinstall the player from scratch, which puts back the correct registry entries and DLLs.
If It Still Fails
Couple things to check:
- Check for malware. There's a nasty strain of adware that deletes
localplay.dllto break media playback and redirect you to fake codec sites. Run Malwarebytes and a Defender full scan. - Third-party firewall blocking. Some security suites (McAfee, Norton) quarantine
localplay.dllas a false positive. Check quarantine logs. - Windows updates. A pending update can lock DLLs. Run
wuauclt /detectnowand install everything, then reboot.
If nothing works, a repair install of Windows (keeping your files) is the nuclear option – but I've only needed that twice in ten years. Usually Step 2 and Step 3 do the job.
Was this solution helpful?