| Previous | Next |
| NS_E_WMP_MMS_NOT_SUPPORTED | NS_E_WMP_GOFULLSCREEN_FAILED |
NS_E_WMP_NO_PROTOCOLS_SELECTED
Diagnosing NS_E_WMP_NO_PROTOCOLS_SELECTED in the Windows Media Player playback path
NS_E_WMP_NO_PROTOCOLS_SELECTED (0xC00D11BE) is returned when all streaming transports usable by the Player have been disabled in configuration.
Trace path or URL resolution, proxy and network selection, parser and codec discovery, graph construction, rendering and optional DRM as separate layers. The actionable checkpoint is all streaming transports usable by the Player have been disabled in configuration. Although this result may appear as “cannot play” or “cannot save,” it belongs to a specific object state that should be diagnosed directly.
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: enabled protocol flags, policy values, Player Network settings and URL scheme. The controlled comparison for this HRESULT is: enable one supported protocol, restart the Player object and retry one known streaming URL.
Closest distinction: NS_E_WMP_INVALID_PROTOCOL means a scheme is unsupported even if other protocols remain enabled.
Capture the first failing layer
| Capture | Why it matters for this HRESULT |
|---|---|
| Object or resource | enabled protocol flags, policy values, Player Network settings and URL scheme |
| 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
- Capture the resource identity and enabled protocol flags, policy values, Player Network settings and URL scheme.
- verify that the caller uses the current Playlist, Media, Network, graph, device or DRM object generation.
- Run the narrow experiment: enable one supported protocol, restart the Player object and retry one known streaming URL.
- Do not mix the result experiment with a codec pack, Player reset or broad registry cleanup.
- After this result, treat a new specific HRESULT as evidence that this boundary was cleared.
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 — all streaming transports usable by the Player have been disabled in configuration — 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
- opening firewall ports while the client has no transport selected.
- 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
- Supported protocols and file types
- Using Windows Media in DirectShow
- Working with codecs
- DirectShow filters
- Microsoft HRESULT registry
The result fix is demonstrated by the same Player path succeeding with the same resource, not by another application opening it.
Looking for a different code? Search another status or error code.