Fix 0XC00D122A: Windows Media Player policy not configured
This error pops up when a Group Policy setting blocks WMP or a registry key is missing. We'll fix it fast with the local policy editor or a reg tweak.
Yeah, this error is annoying. Let's kill it.
You're getting NS_E_WMP_POLICY_VALUE_NOT_CONFIGURED (0XC00D122A) — usually right when you try to open a file or playlist in Windows Media Player. The real culprit here is almost always a stale Group Policy setting or a broken registry key. Don't bother reinstalling WMP or running SFC /scannow — that rarely helps here. Here's what actually works.
The Fast Fix: Local Group Policy Editor
- Press Win + R, type
gpedit.msc, hit Enter. - Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Media Player.
- Double-click "Prevent running Windows Media Player".
- Set it to Not Configured (or Disabled if you see it's Enabled).
- Click OK, close the editor, and restart WMP.
If you're on Windows 10/11 Home, you won't have gpedit.msc. Skip to the registry fix below — that works on every edition.
The Registry Fix (Works Every Time)
reg add "HKLM\SOFTWARE\Policies\Microsoft\WindowsMediaPlayer" /v PreventRunning /t REG_DWORD /d 0 /f
reg add "HKCU\SOFTWARE\Policies\Microsoft\WindowsMediaPlayer" /v PreventRunning /t REG_DWORD /d 0 /f
Run those two commands as Administrator. Then close and reopen WMP. No restart needed.
Why this works: The error means the registry value PreventRunning is set to 1 (enabled) or is missing entirely. Setting it to 0 tells Windows "this policy isn't configured" — which is exactly what WMP expects.
What Causes This?
Three common scenarios:
- A domain GPO pushed out a policy to disable media player.
- A third-party security tool (like Bitdefender or Malwarebytes) blocked the registry key.
- A manual registry cleanup script accidentally deleted the key.
In corporate environments, the fix above might get reverted by the next Group Policy refresh. In that case, contact your IT admin to remove the policy from your OU.
Less Common Variations
Error on 64-bit Windows with 32-bit WMP
On some older systems, WMP might be looking at HKLM\SOFTWARE\Wow6432Node\Policies\Microsoft\WindowsMediaPlayer. Check that path too — same fix applies.
User Account Control (UAC) blocking the change
If the registry commands give you "Access denied", run Command Prompt as Administrator. Don't skip this — the fix won't stick otherwise.
Group Policy objects on a domain
If you're on a company laptop and the policy keeps coming back, the GPO is the problem. Try this temporarily: gpupdate /force after changing the registry, then reboot. If it reverts, you need IT to whitelist your machine.
Prevention Tips
- Before running any registry cleaner (CCleaner, Wise Registry Cleaner), back up the
WindowsMediaPlayerkey. - If you use security software that has a "disable media features" option, check that setting first.
- On domain-joined machines, ask your admin to set the policy to "Not Configured" instead of "Disabled". That way local changes stick.
That's it. This fix has worked for me across Windows 7 through 11, from home machines to 10,000-user enterprises. If you still see the error after this, check Event Viewer under Applications and Services Logs → Microsoft → Windows → MediaPlayer — but honestly, that's a rare edge case. The registry fix covers 95% of these.
Was this solution helpful?