0XC00D11D8

Fix NS_E_WMP_DRM_CANNOT_RESTORE (0XC00D11D8) Restore Limit Error

You've hit Windows Media Player's daily DRM restore cap. Wait 24 hours, then restore once—or skip DRM files entirely.

So you're trying to play a song or video in Windows Media Player and you get slapped with NS_E_WMP_DRM_CANNOT_RESTORE (0XC00D11D8) — "You have exceeded your restore limit for the day." It's annoying because it doesn't tell you what the actual limit is, or when it resets, or why you burned through it in the first place.

Here's what's happening. DRM-protected files (WMA, WMV, some older audiobook and movie downloads) need a license to play. That license lives on your PC. When WMP thinks the license is missing or broken, it goes to the Microsoft license server and asks for a fresh copy. Microsoft caps how many times you can do that per day — historically it's been around 5 per file, per 24 hours, but Microsoft has never published the exact number and it changes. Once you're over, you're locked out until the next day.

The error usually shows up in three situations. Let's go through them in order of how often I see them on the help desk.

Cause 1: You Actually Hit the Daily Limit (Most Common)

This is the boring answer, and it's the right one most of the time. You clicked "Restore" too many times. Maybe the first restore didn't seem to work, so you tried again. And again. And now you're locked out.

I've seen this happen most with old audiobook WMA files from Audible or OverDrive. A user syncs the file to a new laptop, the license fails to come down cleanly, and they hammer the restore button trying to make it work. Five clicks later, they're done for the day.

The fix

  1. Stop clicking Restore. Every click burns another attempt.
  2. Wait a full 24 hours from your last restore attempt. Not from when the first one failed — from the last one.
  3. Make sure your PC's clock is correct. Right-click the time in the taskbar, choose "Adjust date/time," and turn on "Set time automatically." A skewed clock can make the license server think your 24 hours haven't passed even when they have.
  4. After waiting, open Windows Media Player, go to Tools > Options > Privacy, and make sure "Acquire licenses automatically for protected content" is checked. If it's already checked, uncheck it, click Apply, then re-check it. This nudges WMP to re-scan.
  5. Try to play the file once. If the license downloads automatically, you're done. If not, hit Restore exactly once and wait a few minutes before touching anything else.

After clicking Restore, you should see the "Restoring media usage rights" progress bar. Give it a full two minutes before deciding it didn't work. The Microsoft license servers are slow — genuinely slow, like dial-up slow — and impatient users are the number-one cause of hitting this limit.

Cause 2: Your DRM Store Is Corrupted

If you wait 24 hours, click Restore once, and still get 0XC00D11D8, your local DRM store is probably toast. This happens when:

  • You restored a Windows backup or used a disk imaging tool like Macrium Reflect to clone a drive, and the DRM folder got copied with stale machine IDs.
  • You upgraded from Windows 7 or 8.1 to Windows 10 with WMP files still in place.
  • You changed your Windows user account name or the PC name. DRM licenses are tied to both.
  • An antivirus quarantined a file inside the DRM folder.

The DRM store lives here:

C:\ProgramData\Microsoft\Windows\DRM

It's a hidden folder. In File Explorer, click View > Show > Hidden items to see it. Inside you'll find subfolders like DRMv2, Cache, and a bunch of .drm files.

The fix (nuclear, but it works)

Before you do this, understand the trade-off: deleting this folder removes all your existing DRM licenses. You'll need to re-download or re-restore every protected file you own. If you have 200 audiobooks, that's a bad day. If you have three, no big deal.

  1. Close Windows Media Player completely. Not minimized — closed. Check Task Manager if you're not sure.
  2. Open File Explorer and paste C:\ProgramData\Microsoft\Windows\DRM into the address bar. Press Enter.
  3. Rename the DRM folder to DRM.old instead of deleting it. That way you can undo this if things go sideways.
  4. Create a new empty folder called DRM in the same location.
  5. Restart your PC. WMP will rebuild the DRM store on next launch.
  6. Now try to play your protected file. It should trigger a fresh license download.

After restart, when you first open Windows Media Player, you'll likely see it re-prompt you to accept the license agreement. That's expected — it's a sign the rebuild worked. If you don't see that prompt, something else is blocking WMP from writing to the DRM folder, and you probably have a permissions problem or antivirus meddling.

Cause 3: Windows Media Player Itself Is Broken or Outdated

Windows 10 and 11 ship WMP as a legacy feature. Microsoft isn't updating it much. But there's still a version difference between fully-patched installs and ones that haven't been updated since 2018. The DRM components are aging and sometimes fail to negotiate with the modern license server.

Also — and I've seen this trip people up — if you've never launched WMP on a fresh Windows 11 install, it may not have finished its first-run setup. Skip the initial "recommended settings" screen and DRM won't initialize properly. Then you hit this error the first time you try to play a protected file.

The fix

  1. Open the Start menu, type optional features, and click "Add an optional feature."
  2. Search for "Media Features." If it's not installed, install it. If it is, uninstall it, restart, and reinstall it. This reinstalls the WMP engine cleanly.
  3. Run Windows Update. Cumulative updates through 2023 and later include patches to the DRM DLLs. Don't skip them.
  4. Launch WMP and let it finish the setup wizard completely. Don't click through it half-heartedly — pick your privacy options and hit Finish.
  5. Now try the license restore.

One more thing: if you're on Windows 11, WMP is deprecated. For non-DRM files, use the Media Player app (the new one from the Store) or VLC. But VLC won't play DRM-protected WMA/WMV files at all, and no other player will either. That's not a bug — it's how DRM works. If your file is DRM-locked, you're stuck with WMP, or you strip the DRM using tools like FairUse4WM (which is legal in some jurisdictions for personal backups, but check your local laws before trying).

If Nothing Else Works

Try the file on a different PC. If it works there, your original machine has a local issue — usually the DRM folder from Cause 2. If it fails on the second PC too, the problem is with the file or the content provider's license server. In that case, contact the store you bought it from. Audible, for instance, has a backend that can re-issue licenses when WMP-side restores fail.

And yeah, the last resort is a clean Windows install. I hate recommending that. It's a sledgehammer. But if your DRM store is corrupted at a level that survives a folder reset, a clean install does fix it. Just back up your non-DRM files first.

Quick Reference

Cause Signs Fix Time
Hit daily restore limit Error appears after multiple Restore clicks Wait 24 hours, restore exactly once 24 hrs
Corrupted DRM store Restore still fails after waiting a day Rebuild C:\ProgramData\Microsoft\Windows\DRM 15 min
Broken / outdated WMP Never finished initial WMP setup, or WMP hasn't been updated Reinstall Media Features, run Windows Update 20 min

Most people hit this because they clicked Restore too many times. Do the boring thing first: wait a day, fix your clock, click once. If that doesn't work, rebuild the DRM folder. Only then start poking at Windows itself.

Related Errors in Windows Errors
0X000005A8 Fix ERROR_INVALID_SCROLLBAR_RANGE (0x000005A8) on Windows 0X00000843 Fix 0X00000843: Queue is empty on Windows print server Spooler subsystem app has stopped working Print spooler keeps stopping? Here's the real fix 0XC0210011 BitLocker error 0XC0210011: how to fix failed authentication

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.