NS_E_WMP_DRM_DRIVER_AUTH_FAILURE (0xC00D11CA) – Hard Drive DRM Fix
Windows Media Player can't verify DRM because the hard drive's bus driver failed authentication. Fix it by updating or reinstalling the storage controller driver.
Quick answer
Update or reinstall your storage controller driver (usually the Intel AHCI or RAID driver) from the motherboard manufacturer's site, not Windows Update.
What's actually happening here
You're playing a DRM-protected media file in Windows Media Player (versions 11 or 12, on Windows 7 through 10), and you get error 0xC00D11CA. The error string is NS_E_WMP_DRM_DRIVER_AUTH_FAILURE. What's going on under the hood is that WMP's DRM subsystem performs a bus-level check on the hard drive driver — it wants proof that the driver is digitally signed and hasn't been tampered with. If the driver (typically the AHCI or RAID driver from Intel, AMD, or a third-party like Marvell) doesn't return a valid authentication handshake, WMP aborts playback with this error.
This happens most often after a Windows update that replaces your storage driver with a generic Microsoft one, or after installing a new SSD and letting Windows auto-install its own driver. The generic driver works fine for normal disk I/O but lacks the proper DRM bus authentication hooks. I've seen it on Dell XPS 13s and Lenovo ThinkPads after a feature update to Windows 10 22H2.
Main fix: Update or reinstall the storage controller driver
- Open Device Manager. Press
Win + Xand select Device Manager (Windows 10/11) or go through Control Panel on older systems. - Expand "Storage controllers". Look for entries like "Intel(R) Chipset SATA/PCIe RST Premium Controller" or "Standard NVM Express Controller". This is your disk's bus driver.
- Right-click the controller under Storage controllers and select Update driver > Browse my computer for drivers > Let me pick from a list of available drivers on my computer.
- If you see an Intel or AMD branded driver in the list, select it and click Next. If there's only one generic Microsoft driver, skip to step 5.
- If no branded driver appears, download the correct driver from your motherboard or laptop manufacturer's support page. For Intel systems, search for "Intel RST (Rapid Storage Technology) driver" for your chipset. For AMD systems, look for "AMD AHCI Driver". You want the full driver package, not the F6 floppy version.
- Manually install the downloaded driver. Extract the installer files. In Device Manager, right-click the controller > Update driver > Browse my computer > Let me pick > Have Disk, then browse to the extracted
.inffile. Select the driver and install. - Reboot after the driver install completes.
The reason this works: the OEM driver (especially Intel RST) includes a bus interface module that performs DRM authentication via the PortableDeviceBus driver stack. The generic Microsoft storahci.sys driver doesn't include this module. After the reboot, WMP will see the driver's auth token and let the file play.
Alternative fix: Reinstall Windows Media Player DRM components
If the driver fix doesn't work, you might have a corrupted DRM store. Here's the cleanest way to reset it:
- Close WMP entirely.
- Open an elevated Command Prompt (Run as administrator).
- Run these commands in order:
net stop Audiosrv
net stop WMPNetworkSvc
reg delete "HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\DRM" /f
del /q /s %USERPROFILE%\Local Settings\Temp\*drm* 2>nul
del /q /s %USERPROFILE%\AppData\Local\Microsoft\Media Player\*drm* 2>nul - Reboot. WMP will recreate the DRM store on next launch.
This step is a fallback because it wipes your DRM licenses — you'll need to re-authorize any purchased content. But it's fast and sometimes the driver alone wasn't enough because the DRM store had a stale auth token.
Prevention tip
After you fix the error, disable automatic driver updates for storage controllers. Go to System Properties > Hardware > Device Installation Settings and select No (or "Never install driver software from Windows Update" on older builds). This prevents a future update from swapping your working OEM driver back to the generic one. I've been burned by this twice on my own machine — once after a cumulative update in October 2023. Don't let it happen to you.
Was this solution helpful?