0XC00D11D0

0XC00D11D0: WMP needs DRM authorization—real fixes

Network & Connectivity Intermediate 👁 0 views 📅 May 27, 2026

This error means Windows Media Player can't reach Microsoft's DRM license servers. Usually a firewall, corrupted rights store, or time/date issue. Fixes below.

You got 0xC00D11D0NS_E_WMP_DRM_NEEDS_AUTHORIZATION. This happens when Windows Media Player can't verify a digital license with Microsoft's servers. I've seen it on Windows 10 22H2, Windows 11, and even older Win7 machines trying to play purchased music or video files. The three culprits are almost always: a blocked firewall, a corrupted local DRM store, or a system clock that's off by more than a few minutes.

1. Firewall or proxy blocking the DRM server

WMP tries to reach https://drmlicense.one.microsoft.com and a few other Microsoft servers to validate licenses. If your firewall, antivirus, or company proxy is blocking that, you get 0xC00D11D0 right away. The reason step 1 is here: it's the most common cause, and it's the easiest to test.

What to do

  1. Open Windows Defender Firewall (or whatever third-party firewall you use).
  2. Make sure wmplayer.exe is allowed outbound on port 443 (HTTPS). The default path is C:\Program Files\Windows Media Player\wmplayer.exe.
  3. If you're behind a corporate proxy, WMP must use the system proxy settings. Open Internet Options > Connections > LAN settings. Check "Automatically detect settings" or enter your proxy manually. WMP doesn't have its own proxy config—it inherits from IE/Edge.
  4. Test by temporarily disabling the firewall. If the file plays, you've found the problem.

I've also seen this caused by aggressive web filtering in products like Kaspersky or Norton. Add an exception for *.microsoft.com or drmlicense.one.microsoft.com if needed.

2. Corrupted local DRM store

If the firewall is fine, the next suspect is a corrupted DRM folder. Windows stores license data in %PROGRAMDATA%\Microsoft\Windows\DRM. If those files get borked—maybe from a crash, disk error, or old antivirus quarantine—WMP can't authorize anything.

Reset the store

  1. Close WMP completely.
  2. Open File Explorer and go to C:\ProgramData\Microsoft\Windows\DRM. You might need to enable hidden items in View menu.
  3. Rename the DRM folder to DRM.old. Don't delete it yet—keep a backup.
  4. Restart WMP and try to play the file again. Windows will regenerate a fresh DRM folder.

What's actually happening here is that the local license cache is gone, so WMP has to fetch a new one from Microsoft. It will silently re-authorize on first play. If that works, you can safely delete DRM.old after a day. On some systems, you might need to run WMP as Administrator once to write the new folder.

3. System clock out of sync

DRM licenses are time-sensitive. They check the expiry date and also use timestamps to validate the handshake. If your clock is off by more than about 15 minutes, the server rejects the request and throws 0xC00D11D0. I've seen this after a CMOS battery failure or after dual-booting from another OS that changes the hardware clock.

Fix the clock

  1. Right-click the clock in the taskbar > Adjust date/time.
  2. Turn on "Set time automatically" and "Set time zone automatically".
  3. Click "Sync now" under Synchronize with an internet time server. Wait a few seconds.
  4. Verify the clock is correct—seconds matter less than minutes.

If you're in a corporate domain with a firewall that blocks NTP (port 123), sync via a local time server instead. Also check the w32tm service is running. You can force a resync with w32tm /resync in an admin command prompt.

Quick-reference summary

CauseCheck thisFix it with
Firewall/proxy blockCan you reach drmlicense.one.microsoft.com in a browser?Allow wmplayer.exe on port 443, configure proxy
Corrupted DRM storeDRM folder exists and has weird file sizes?Rename folder to DRM.old, let WMP recreate it
Clock skewTime off by more than 5 minutes?Sync with time.windows.com manually

These three fixes solve the problem in 95% of cases. If none work, you could also try reinstalling WMP via Windows Features, but that's rare. The error is almost always a network or clock problem—not a corrupt file or missing codec.

Was this solution helpful?