What's actually happening here
That error code (0XC00D2909) is Windows Media Player's way of saying your audio device won't play uncompressed digital audio because it can't handle the current HDCP protection level. This usually shows up when you're trying to play a DVD, Blu-ray, or a downloaded movie over HDMI or DisplayPort. Your TV or receiver is expecting a certain content protection handshake, and the audio driver on your PC isn't cooperating.
The good news: most of the time it's a driver or settings issue, not a hardware failure. The fixes below go from least invasive to most thorough. Stop when the audio works.
Fix 1: The 30-second fix — Set your audio output to stereo
This sounds counterintuitive, but dropping to 2-channel PCM often bypasses the protection check entirely. Uncompressed 5.1 or 7.1 audio requires a higher HDCP level than stereo. If your receiver doesn't negotiate that level properly, Windows throws this exact error.
- Right-click the speaker icon in the system tray and select Sound settings.
- Under Output, click your HDMI or DisplayPort device.
- Click Device properties → Additional device properties.
- Go to the Advanced tab and change the default format to
2 channel, 16 bit, 48000 Hz (DVD Quality). - Click Apply, then try playing your file again.
If that works, you're done. If not, move on. Real-world trigger: this happens a lot with older AV receivers that support 4K video but only HDMI 1.4 audio passthrough.
Fix 2: The 5-minute fix — Update or reinstall your audio driver
Here's the thing: the protection level is negotiated by the audio driver, not the hardware itself. A driver from 2019 might not support the HDCP 2.2 or 2.3 levels that modern content requires. Updating it is the most common permanent fix.
- Press Win + X and select Device Manager.
- Expand Sound, video and game controllers.
- Find your HDMI audio device — it usually has the GPU vendor's name (NVIDIA, AMD, Intel) and “Audio” in the title.
- Right-click it and choose Update driver → Search automatically for drivers.
- If Windows doesn't find anything, go to your GPU manufacturer's site:
- NVIDIA: download the latest driver from nvidia.com/drivers. The audio driver is bundled.
- AMD: same deal — the audio driver comes with the Adrenalin package.
- Intel: grab the latest graphics driver, which includes HDMI audio.
After updating, restart your PC and test. If the error persists, the driver didn't fix the handshake — so we go deeper.
Fix 3: The 15+ minute fix — Disable HDCP or switch to a different audio output
This is the nuclear option, but it works when the protection level negotiation is fundamentally broken on your hardware. I'm not going to pretend this is elegant — you're bypassing the protection check, which means some content might not play at all. But for the error you're seeing, it's often the only real fix.
Option A: Turn off HDCP in your graphics driver
- Open the NVIDIA Control Panel (or AMD Radeon Software).
- Look for Display → Change resolution (NVIDIA) or Display → HDCP (AMD).
- Find the HDCP setting and set it to Off or Disabled.
- Apply, restart the display, and test.
Note: Some drivers don't expose this setting anymore. If you can't find it, skip to option B.
Option B: Force the audio output to a non-HDMI device
If you have a separate analog audio output (3.5mm jack, USB DAC, or Bluetooth), set that as the default output device. The protection level is only enforced over digital links like HDMI/DisplayPort. It's a workaround, not a fix, but if you're streaming to a TV via HDMI, you might already have the audio going to a soundbar via Bluetooth — so this doesn't cost you anything.
- Right-click the speaker icon → Sound settings.
- Under Output, choose the non-HDMI device.
- Test your playback.
Option C: Use a different media player
Windows Media Player and the Movies & TV app are strict about HDCP. VLC Media Player, on the other hand, has its own decryption routines and often just ignores the protection level. It won't fix the underlying driver issue, but it'll get your audio playing right now. Install VLC (it's free), open your file, and see if the error goes away. If it does, you know the problem is specifically the Windows audio stack, not your hardware.
Why this error appears more on Windows 11 than Windows 10
Windows 11 tightened the audio protection model to align with newer DRM requirements from streaming services. That means older drivers that worked fine on Windows 10 now fail the handshake. If you recently upgraded and hit this, check your motherboard manufacturer's site for updated audio drivers — not just the GPU ones. Realtek and Intel HD Audio drivers sometimes need a manual update even if Windows Update says you're current.
When all else fails — check your cable
I know this sounds too simple, but I've seen this exact error caused by a cheap HDMI cable that only carries 4K video, not full audio bandwidth. The protection level negotiation includes a data channel that some budget cables drop. Swap in a cable that's certified for HDMI 2.0 or higher (look for the “High Speed” or “Ultra High Speed” label). If that's your issue, the fix costs less than $10 and five minutes. Worth a shot before you RMA your motherboard.
That's the whole flow. Try the stereo trick first, then the driver, then the HDCP bypass. You should hit audio at one of those steps.