Fix WMP Error 0XC00D11BB (Unsupported Protocol)

Windows Media Player throws this when it hits a URL it can't handle. Usually a streaming protocol mix-up or a broken file association. Here's how to fix it fast.

I know this error is infuriating. You double-click a link or a file, and Windows Media Player just stares back at you with that cryptic 0XC00D11BB. It translates to "the specified protocol is not supported." But what does that actually mean?

It means WMP doesn't recognize the way the file is being delivered. Think of protocols as different languages for streaming. WMP speaks a few, but if it hears a dialect it doesn't know, it bails. The good news? This is rarely a broken player. It's usually a settings hiccup or a file association gone wrong.

Here's the fix path. Start with step one—if it doesn't work, move down. Most people never need to go past step two.

Step 1: The 30-Second Fix—Reset File Associations

Half the time, this error pops up because WMP is trying to open a file type it shouldn't be handling. Windows 10 and 11 sometimes reassign associations after an update, and suddenly WMP is the default for everything, including protocols it can't handle.

Open Settings (Win + I).
Go to Apps > Default apps.
Scroll down and click Choose default apps by file type.
Look for .mp3, .wmv, .asf, and .wma. If WMP is listed for any of them, click and switch to Movies & TV or VLC (if you have it). Or better, click Reset at the top to let Windows decide.

That resets the defaults and usually stops WMP from grabbing files it shouldn't. Try playing the file again. If it still throws 0XC00D11BB, move on.

Step 2: The 5-Minute Fix—Check the Streaming Protocol

This is where the error gets its name. WMP supports specific protocols: mms://, rtsp://, and http:// (with Windows Media Services). If the link you're trying to open uses rtmp:// or https:// with a non-Windows server, WMP just can't speak that language.

Here's a real-world scenario: you click a streaming link from a legacy security camera or an old radio station's website. The URL might look like rtsp://192.168.1.50/stream. WMP should handle that, but if the server is sending a different codec, it fails. Or the link is actually rtmp://—that's Adobe's protocol, and WMP will never support it.

How to check: right-click the link and copy the URL. Paste it into Notepad. Look at the prefix.

If it's mms:// or rtsp://, WMP should work—but you might need to enable the protocol in WMP's options.
If it's anything else, like rtmp:// or https:// (that's not a direct media file), WMP isn't your player. Use VLC instead.

To enable RTSP/MMS in WMP:

Open WMP.
Go to Tools > Options (if you don't see the menu, press Alt+T).
Click the Network tab.
Under Streaming protocols, make sure RTSP/UDP, RTSP/TCP, and HTTP are checked.
Apply and restart WMP.

If the link still fails, it's the protocol mismatch. VLC will handle those links without complaint—it's free and supports nearly every protocol under the sun. Don't fight it; just switch.

Step 3: The 15+ Minute Fix—Registry Cleanup for the Advanced User

If you've ruled out associations and protocol issues, the error could be a corrupted registry entry. This happens after uninstalling other media players or codec packs that hijacked WMP's protocol handlers.

Warning: Back up your registry before you touch anything. Export a copy first, or create a restore point.

The registry keys that matter:

HKEY_CLASSES_ROOT\MMS
HKEY_CLASSES_ROOT\RTSP
HKEY_CLASSES_ROOT\PNM

These should point to WMP.MMSProtocolHandler, WMP.RTSPProtocolHandler, and WMP.PNMProtocolHandler respectively. If they point to something else—like a codec pack's handler—that's your problem.

Here's the fix:

Press Win + R, type regedit, hit Enter.
Navigate to HKEY_CLASSES_ROOT\MMS.
Double-click the (Default) value and set it to WMP.MMSProtocolHandler.
Do the same for HKEY_CLASSES_ROOT\RTSP (set to WMP.RTSPProtocolHandler) and HKEY_CLASSES_ROOT\PNM (set to WMP.PNMProtocolHandler).
Close regedit and restart your PC.

This resets WMP's protocol bindings to factory defaults. I've seen this fix stubborn cases after a messy uninstall of K-Lite Codec Pack.

If that still doesn't do it, you might be dealing with a damaged WMP installation. Run sfc /scannow in an elevated command prompt—that checks system files and repairs what's broken.

When to Give Up on WMP

Let's be honest. WMP is a zombie—it exists, but it's not actively developed. If your streaming source uses modern protocols or encrypted streams, WMP won't cut it. Install VLC (VideoLAN) or MPC-HC. They handle everything, and you won't see this error again.

But if you're stuck with WMP for legacy reasons, the steps above will get you through 90% of the cases. Start with the associations, check the protocol, and if it's still broken, go deep into the registry.

Good luck. And if you hit a snag, drop a comment below—I read every one.