I know this error is infuriating — you just want to watch a video, and Windows throws a wall of hex at you instead.
Here's the short version: 0XC00D2906 means the media file or stream is demanding a hardware protection level (usually HDCP or a specific uncompressed digital video protection tier) that your display chain can't deliver. Windows Media Player, Movies & TV, and some third-party players all respect this flag, so they refuse to play rather than downgrade. You have three real options: fix the display chain, lower the protection requirement, or switch players. Let's start with the fastest one.
Step 1: Try the built-in troubleshooters first (2 minutes)
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run Video Playback.
- Run Windows Media Player if it shows up (Win 10 only).
This clears stale DRM licenses about 20% of the time. Don't expect miracles, but it's free.
Step 2: The real fix — reset the DRM store and clear the HDCP handshake
This is the one that actually works. The error happens because Windows cached a bad HDCP handshake or a corrupt license from a previous session. Blow both away and force a fresh negotiation.
# Run Command Prompt as Administrator
net stop wmpnetworksvc
cd %windir%\System32\LogFiles
rmdir /s /q wmplayer
cd %ProgramData%\Microsoft\Windows\DRM
rmdir /s /q * /q
Then delete the individual DRM license files:
del /f /q "%ProgramData%\Microsoft\Windows\DRM\*.drm"
del /f /q "%ProgramData%\Microsoft\Windows\DRM\*.lic"
Restart the machine. Don't skip the reboot — the HDCP handshake only re-runs at driver load.
If you're on Windows 11 22H2 or later, the DRM folder path is the same, but you may also need to reset the Media Foundation store:
net stop mfnetworksvc
sc config mfnetworksvc start= auto
net start mfnetworksvc
Step 3: Fix the display chain — this is where 80% of cases live
HDCP needs an unbroken path from GPU to monitor. Break any link and the protection level drops. Common culprits:
- Cheap HDMI splitters or KVM switches — many strip HDCP silently. Swap to direct connection and retest.
- DisplayPort-to-HDMI adapters under $15 — hit or miss. The ones that look like a cable with a fat end often fake HDCP.
- Capture cards in the chain — Elgato HD60 S and similar will trigger this error on protected content by design.
- Old monitors — a 2012 Dell U2412M over DVI will happily fail HDCP 2.2 handshakes. HDCP 1.4 only.
Unplug everything. Connect GPU straight to the primary monitor with a known-good cable. Try the video again. If it plays, you found your problem — reintroduce devices one at a time until it breaks.
Step 4: Lower the video output color depth
Some content requests uncompressed digital video protection at 10-bit or 12-bit color depth that your GPU can't wrap in HDCP. Drop it to 8-bit:
- Right-click desktop > Display settings > Advanced display.
- Note the refresh rate. Then open your GPU control panel (NVIDIA Control Panel or AMD Software).
- NVIDIA: Change resolution > set Output color depth to 8 bpc.
- AMD: Display > set Color Depth to 8 bpc.
- Reboot and try playback.
Step 5: Switch to VLC or MPV (the nuclear option)
VLC ignores DRM protection flags by default unless you've enabled them. For unprotected local files that WMP refuses to play, just use VLC. It's the fastest workaround and it's what I tell people when they're on a deadline.
For protected content from a streaming service, this won't help — but if the file is yours, VLC will play it while WMP sulks.
Why this works
The error fires when the file's protection descriptor asks for a minimum level your current output can't meet. Windows Media Player treats this as a hard refusal. It won't fall back to a lower protection tier automatically — that's actually a security feature from the PlaysForSure era that never got a graceful fallback.
By resetting the DRM store, you clear any cached license that hard-coded an old protection level. By fixing the display chain, you make the current hardware capable of meeting the requested level. By dropping color depth, you reduce the bandwidth requirement that HDCP has to carry. Each step attacks a different part of the same handshake.
Less common variations
Error appears only on a second monitor
Multi-monitor setups negotiate HDCP per-output. If one display is a TV and the other is a monitor, Windows may pick the weakest link. Move the video player to the primary display, or disable the secondary monitor in Display Settings temporarily.
Error appears only after a Windows Update
Windows 11 build 22621.2361 and a few earlier 22H2 patches reset your HDCP driver state. Reinstall the GPU driver using DDU (Display Driver Uninstaller) in Safe Mode, then reinstall the latest driver from NVIDIA/AMD/Intel directly — not through Windows Update.
Error appears in a VM or over Remote Desktop
RDP sessions can't negotiate HDCP at all. There's no fix — you have to play the content on the local console. Same for VMware and Hyper-V guests unless you pass through the GPU and a physical display.
Error on a laptop with a hybrid GPU
Intel iGPU + NVIDIA dGPU laptops route the video through the Intel GPU for display but decode via NVIDIA. The handshake gets confused. Force the player to use the discrete GPU: Settings > System > Display > Graphics > [player app] > High performance.
Prevention
- Skip cheap HDMI splitters and sub-$20 adapters. They cost you hours later.
- Keep your GPU driver current, but install from the vendor's site — Windows Update drivers lag 2-6 months on HDCP fixes.
- Don't chain capture cards into your daily-use monitor path. Use a second monitor for capture.
- Before a Windows feature update, note your display color depth. Updates sometimes reset it to the display's EDID default, which can break handshakes that were working fine.
- Keep VLC installed. It's the one player that won't argue with you about DRM flags for your own files.
If you've done all of this and it still fails, the file itself probably has a corrupted protection descriptor. Test with a different file of the same type. If only that one file fails, it's not your machine — it's the file.