0XC00D2738

Fix NS_E_DRM_LICENSE_CLOSE_ERROR (0xC00D2738)

Hardware – Hard Drives Intermediate 👁 1 views 📅 May 28, 2026

DRM license storage error when media files won't play. Usually a corrupted license store or permissions issue. Here's the real fix.

Quick Answer

Delete the C:\Users\[YourUsername]\AppData\Local\Microsoft\DRM folder, then re-open Windows Media Player. That clears corrupted license data 9 times out of 10.

Why This Happens

NS_E_DRM_LICENSE_CLOSE_ERROR (0xC00D2738) means Windows can't properly close or save your DRM license file. I've seen this mostly on Windows 10 machines that have been through a few updates, especially after a system restore or when running an older media player like WMP version 12. The DRM store—a hidden folder in your user profile—gets corrupt. Maybe from a crash mid-playback, a permissions issue after a user profile migration, or a third-party codec pack that steps on Microsoft's toes. The error pops up when you try to play protected content—like purchased music, videos from streaming services that use DRM, or old .wma files from your ripped CD collection.

Here's the kicker: Windows Media Player tries to write a license file that's basically a token saying “yes, you paid for this.” If the store is locked up, it throws that 0xC00D2738 code. The fix is brutal but simple—nuke the old store and let Windows rebuild it.

Step-by-Step Fix

  1. Close everything. Exit Windows Media Player, any video app, and any browser that might be streaming protected content. I've seen Firefox hold a lock on the DRM store and cause this error.
  2. Open File Explorer. Type %localappdata%\Microsoft\DRM in the address bar and hit Enter. You'll land in a folder with a few files like indiv01.key, license.lic, and some DrmClnt files.
  3. Back up the folder. Just a safety net—copy the whole DRM folder to your Desktop. If things go sideways (they won't), you can restore it.
  4. Delete everything inside. Select all files, delete them. You might get a permission error on indiv01.key. If so, open Task Manager, kill wmplayer.exe if it's running, then try again. Still stuck? Reboot into Safe Mode and delete from there.
  5. Reopen Windows Media Player. It'll recreate the DRM folder fresh. Try playing the file that caused the error. If it works, you're golden. If not, you might need to re-download the license from the content provider (like a purchase from the Microsoft Store or an old Napster track).

Alternative Fixes

Reset Windows Media Player

If the folder deletion didn't cut it, reset WMP's settings. Open Settings > Apps > Windows Media Player (or Media Features in older Windows versions), choose Advanced options, and hit Reset. This kills any corrupted preferences tied to the license store.

Run the DRM Repair Tool

Microsoft used to offer a DRMRepairTool.exe for XP and Vista. On Windows 10/11, it's not officially supported, but you can try the Windows Media Player Repair Tool from the Troubleshooting section: Control Panel > Troubleshooting > Programs > Windows Media Player > Next. It rarely works for this specific error, but it's worth a shot if you're out of options.

Clean Boot

Third-party services can lock the DRM store. Do a clean boot via msconfig—disable all non-Microsoft services, reboot, and try the fix again. I had a client last month whose anti-malware software was holding a handle on the DRM folder. Disabling it during playback fixed it.

Prevention Tip

Don't let Windows Media Player be your default player for everything. Use a modern app like VLC or MPC-HC for unprotected content. Only use WMP for DRM-encumbered files you actually own. Also, avoid those “codec packs” that promise to play everything—they're notorious for corrupting the DRM store. Stick to the built-in codecs or a single codec pack like K-Lite (basic version only) if you must.

Had a small law office last year where everyone's WMP started throwing 0xC00D2738 after an IT admin pushed a group policy that locked down AppData permissions. Reverting that policy plus the folder delete fixed the whole network. Check your permissions if you're in a corporate environment.

Was this solution helpful?