0XC00D11BE

NS_E_WMP_NO_PROTOCOLS_SELECTED (0XC00D11BE) fix

Windows Errors Beginner 👁 3 views 📅 Jun 4, 2026

Windows Media Player can't play the file because no streaming protocols are enabled. The fix is re-enabling them in the settings.

Quick answer

Open Windows Media Player, go to Tools > Options > Network, check all protocol boxes (RTSP/TCP, RTSP/UDP, HTTP, Multicast), click Apply, then OK. That's it.

Why this happens

Windows Media Player (WMP) uses a set of network protocols — RTSP (Real-Time Streaming Protocol), HTTP, UDP, and multicast — to stream media over the internet or your local network. When none of these are selected in the Network settings, WMP can't negotiate a connection with the media server. The error 0XC00D11BE is WMP's way of saying “I have no way to ask for the file.”

This usually happens after a Windows update that resets or corrupts your WMP preferences, or after running a privacy-focused tool like O&O ShutUp10 or WPD that disables protocols to block telemetry. Some users also see it after manually tweaking Group Policy settings for network services. The fix is dead simple — you just need to flip a few checkboxes back on.

Fix steps

  1. Open Windows Media Player. If it's not pinned to your taskbar, hit the Start menu and type Windows Media Player to find it.
  2. Open the Network settings. Click Tools in the menu bar (if you don't see it, press Alt to reveal the menu), then select Options, and go to the Network tab.
  3. Enable all protocols. You'll see checkboxes for:
    • RTSP/TCP
    • RTSP/UDP
    • HTTP
    • Multicast
    Check all of them. The exact names depend on your WMP version, but there are usually four boxes. Don't skip HTTP — some people think it's only for web pages, but WMP uses it for progressive download streaming.
  4. Apply and test. Click Apply, then OK. Try playing the file again. If it works, you're done. If not, close WMP entirely and reopen it — the setting sometimes needs a full restart to take effect.

Alternative fixes if step 3 doesn't work

Sometimes the main fix doesn't stick, especially if a group policy or third-party tool is overriding your preferences. Here are the next things to try:

  • Reset WMP settings via registry. Close WMP, open Registry Editor (Win + R, type regedit), navigate to HKEY_CURRENT_USER\Software\Microsoft\MediaPlayer\Preferences. Delete the Protocols value (not the whole key). Restart WMP — it will recreate the defaults with all protocols enabled.
  • Check Group Policy. If you're on Windows Pro or Enterprise, run gpedit.msc, go to Computer Configuration > Administrative Templates > Windows Components > Windows Media Player > Networking. Make sure policies like “Set Protocols” are set to Not Configured rather than Disabled.
  • Re-register WMP. Open Command Prompt as admin, run regsvr32 wmp.dll and regsvr32 wmploc.dll. This re-registers the core Media Player components without reinstalling.
  • Disable third-party privacy tools. If you used WPD or ShutUp10, undo any changes related to Windows Media Player or network protocols. These tools often flip multiple registry keys at once.

Prevention tip

The most common cause is a privacy tool or script that aggressively disables network features. If you run one of those, add WMP to its exception list, or manually re-enable protocols right after. Also, before running a Windows feature update, note your WMP settings — updates can wipe them. A quick screenshot of the Network tab saves you ten minutes of digging later.

Was this solution helpful?