Fix NS_E_ALL_PROTOCOLS_DISABLED (0XC00D2EEB) in Windows

This error's a pain, but it's an easy fix

You're trying to stream a video or audio file, and Windows Media Player throws up this cryptic NS_E_ALL_PROTOCOLS_DISABLED (0XC00D2EEB) message. The short version: WMP can't use any network protocol to get the stream. The culprit here is almost always a single checkbox in WMP's settings that got turned off — either by accident, a Windows update, or some overzealous security software.

The fix: re-enable HTTP (or RTSP)

Open Windows Media Player. In the menu bar at the top, click Tools and then Options. If you don't see the menu bar, press Alt on your keyboard to show it.

Go to the Network tab. You'll see a section called Streaming proxy settings with a list of protocols: RTSP/TCP, RTSP/UDP, HTTP, and sometimes MMS. If every single one is unchecked, that's your problem.

Check the box next to HTTP (and RTSP too, if it's there). Click OK. Try streaming again.

That's it. Nine times out of ten, this immediately kills the error. If it doesn't work, close WMP completely, restart it, and try again. Sometimes the setting doesn't take until the app reloads.

Why this works

WMP uses different protocols to fetch media over a network. HTTP is the standard web protocol — same one your browser uses. RTSP is older, designed for real-time streaming (like IP cameras or media servers). When all protocols are disabled in WMP, it has no way to pull the stream. The error code literally means “all protocols disabled” — it's not being dramatic.

Most streaming URLs these days use HTTP. So enabling HTTP alone fixes almost every instance of this error. If you get the same error with a local file (not a network stream), that's a different problem — likely corrupt codecs or a broken file.

Less common variations

Sometimes the problem isn't WMP itself but the underlying Windows networking stack. Here are a few edge cases I've seen:

• Corrupt WMP settings: If re-enabling protocols doesn't stick, WMP's configuration might be corrupted. Reset it by deleting the registry key HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer while WMP is closed. Windows will recreate it fresh.
• Group Policy blocked it: On corporate or managed PCs, an admin might have disabled streaming protocols via Group Policy. Check with your IT team — or look in gpedit.msc under Computer Configuration > Administrative Templates > Windows Components > Windows Media Player > Network.
• Third-party firewall or antivirus: Some security suites (especially Norton and McAfee) silently block WMP's network access. Temporarily disable the firewall to test. If that fixes it, whitelist wmplayer.exe.
• IP address change or VPN: If you're on a VPN or your IP changed, WMP might think the network is unavailable. Disconnect the VPN, refresh the network connection (ipconfig /release then ipconfig /renew), and try again.

Preventing it from happening again

Once you've got it working, don't let it sneak back. Here's how:

1. Don't run WMP as admin unless you have to. Running it elevated can sometimes reset user-specific settings.
2. Check Windows updates before installing them. Occasionally a cumulative update will reset WMP's network settings. If you notice the error right after an update, you know the fix.
3. If you use third-party media players like VLC or MPC-HC, they bypass this error entirely because they don't rely on Windows Media Player's protocol stack. Consider switching for day-to-day streaming — it'll save you headaches.
4. Export your WMP settings once you have them dialed in. Use regedit to export HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer. If the error comes back, double-click the export to restore everything.

I've seen this error on Windows 7 all the way through Windows 11. The fix hasn't changed. Keep that Network tab setting in mind — it'll save you a lot of googling next time.