What does HRESULT 0xC00D11BD (NS_E_WMP_MMS_NOT_SUPPORTED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Windows Media Player cannot play the file because the specified protocol is not supported. If you typed a URL in the Open URL dialog box, try using a different transport protocol (for example, "mms:").%0

Previous	Next
NS_E_WMP_INVALID_LIBRARY_ADD	NS_E_WMP_NO_PROTOCOLS_SELECTED

NS_E_WMP_MMS_NOT_SUPPORTED

Diagnosing NS_E_WMP_MMS_NOT_SUPPORTED in the Windows Media Player playback path

NS_E_WMP_MMS_NOT_SUPPORTED (0xC00D11BD) is returned when the requested legacy MMS transport is unavailable in the installed Player path or for the target resource.

Trace path or URL resolution, proxy and network selection, parser and codec discovery, graph construction, rendering and optional DRM as separate layers. This result identifies a narrower stage than the dialog text exposes, so preserve its operation before trying a workaround. In this case the rejected checkpoint is the requested legacy MMS transport is unavailable in the installed Player path or for the target resource.

Playback boundary

AllStat already supplies the standard user-facing description for this HRESULT; this custom block instead isolates the additional technical boundary. Earlier success in file lookup, network connection, parser creation or graph construction does not prove that the later the operation is valid.

Case-specific checkpoint: URL scheme, Player version, enabled protocols, server-supported alternatives and rollover trace. The controlled comparison for this HRESULT is: use the server-provided HTTP or RTSP URL for the same publishing point and compare session creation.

Closest distinction: NS_E_WMP_INVALID_PROTOCOL can apply to any unsupported scheme; this result identifies MMS specifically.

Capture the first failing layer

Capture	Why it matters for this HRESULT
Object or resource	URL scheme, Player version, enabled protocols, server-supported alternatives and rollover trace
State snapshot	Record the Player openState/playState or operation phase, object identity and exact timestamp when this result was returned.
First lower result	Keep the earliest Win32, Winsock, COM, parser, codec, DRM or device result that appears before this result.
Comparison record	Use one known-good case that follows the same API, protocol and component path while changing only the rejected precondition.

Controlled playback comparison

Freeze the current object state and collect URL scheme, Player version, enabled protocols, server-supported alternatives and rollover trace.
Reproduce it once without automatic retries or fallback applications.
Change only one precondition: use the server-provided HTTP or RTSP URL for the same publishing point and compare session creation.
compare the first nested status and next Player event with the failed run.
After testing it, restore the original configuration if the change was diagnostic only.

How to interpret the retest

Retest outcome	Interpretation
Same it on the same object	The governing state or value is unchanged, or the caller is reusing an object created before the relevant change.
Fresh object succeeds	Lifetime, cached configuration or stale playlist/graph state contributed to it.
A later HRESULT appears	The rejected condition — the requested legacy MMS transport is unavailable in the installed Player path or for the target resource — was cleared for this HRESULT; diagnose the new code at its own layer.
Only one item or endpoint fails for this HRESULT	The evidence favors resource-specific data, rights, routing or device state rather than a global Player failure.

Actions that obscure the cause

changing mms:// to http:// without verifying the server exposes HTTP streaming.
Do not discard the first occurrence by repeatedly invoking Play, open, save or retry; later events can replace its original state.
do not publish credentials, private URLs, license material or complete protected-content headers; retain only redacted identifiers, lengths, hashes and protocol fields.

Technical references

After it, a different downstream HRESULT is progress and should be recorded as a separate condition.

Looking for a different code? Search another status or error code.