NS_E_DRM_UNABLE_TO_CREATE_KEYS_OBJECT (0XC00D2758) Fix
This DRM error hits when Windows Media Player or Xbox apps can't create a protected keys object. Almost always a corrupted DRM data store or missing system files.
You're stuck with a DRM error that kills media playback.
I've seen this one more times than I can count. The good news? You don't need to reinstall Windows or nuke your media library. Nine times out of ten, the culprit is a corrupted local DRM data store that Windows Media Player or the Xbox app can't read anymore.
The Quick Fix: Reset Your DRM Store
- Close all media apps — WMP, Movies & TV, Xbox app, anything that plays protected content. Kill them in Task Manager if they're stuck.
- Open an elevated Command Prompt (right-click Start > Command Prompt (Admin) or PowerShell (Admin)).
- Run these three commands in order:
net stop Audiosrv net stop MpsSvc del /f /s /q "%ALLUSERSPROFILE%\Microsoft\PlayReady\*" - Restart the services with:
net start Audiosrv net start MpsSvc - Delete the DRM folder manually — just in case a file was locked. Navigate to
C:\ProgramData\Microsoft\PlayReadyand delete everything inside. If Windows says a file is in use, reboot and try again. - Reboot your machine. Then open Windows Media Player or your Xbox app again. It'll recreate the DRM store fresh from scratch.
That's it. This clears out any corrupted license data or partially-written keys objects that cause the 0XC00D2758 error.
Why This Works
The DRM subsystem in Windows (PlayReady) stores protected media licenses and encryption keys in C:\ProgramData\Microsoft\PlayReady. When that store gets corrupted — from a crash during playback, a failed Windows update, or third-party DRM software like Adobe Flash messing with it — the key creation process fails. Resetting the store forces Windows to rebuild it from scratch the next time you play protected content. No need to reacquire licenses if you're signed into the same Microsoft account; they get pulled down fresh.
The service restarts are key because the Audio Service and Media Protection Service both hold file locks on that directory. If you skip the service stop, you'll get an "access denied" when trying to delete the folder.
When the Quick Fix Isn't Enough
Rarely, the issue comes from deeper corruption. Here's what else I've seen:
Corrupted System Files
Run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth from an admin command prompt. This fixes system file corruption that can break DRM components.
Outdated or Missing Media Feature Pack
On Windows 10/11 N editions (the ones without Windows Media Player preinstalled), you need the Media Feature Pack from Microsoft. That pack includes the DRM runtime. Get it from Settings > Apps > Optional Features > Add a feature > search for “Media Feature Pack”. Install and reboot.
Third-Party DRM Conflicts
Older software like Windows Media Center or third-party codec packs (K-Lite, CCCP) sometimes install their own DRM clients that clash with PlayReady. Uninstall any codec packs, then reinstall the official Media Feature Pack.
User Profile Corruption
If the error follows a specific user account, create a new local admin account and test playback there. If it works, migrate your data and ditch the old profile. Not pretty, but it works.
Preventing This from Happening Again
- Don't kill media apps abruptly during license acquisition. Let them finish their DRM handshake before closing.
- Keep Windows updated. Cumulative updates often include PlayReady fixes. Skip them and you're rolling the dice.
- Avoid third-party DRM utilities. Programs that claim to “fix DRM” usually break it worse. Stick with the built-in tools.
- Run a disk health check quarterly. Bad sectors in the ProgramData directory can corrupt DRM files. Use
chkdsk /f C:to find and fix them. - Backup your PlayReady folder after a fresh license acquisition (just in case). You can zip
C:\ProgramData\Microsoft\PlayReadyand save it. If corruption hits again, restore that backup instead of re-downloading licenses.
That's the whole playbook. I've used this on Windows 10, 11, and even some Server 2019 builds running Media Player. It hasn't failed me yet.
Was this solution helpful?