| Previous | Next |
| MF_E_NET_BWLEVEL_NOT_SUPPORTED | MF_E_NET_MANUALSS_NOT_SUPPORTED |
MF_E_NET_STREAMGROUPS_NOT_SUPPORTED
MF_E_NET_STREAMGROUPS_NOT_SUPPORTED means the application requested stream-group behavior that the current network source does not support.
What to check for MF_E_NET_STREAMGROUPS_NOT_SUPPORTED
- Use the default stream selection path unless the source explicitly exposes stream groups.
- Check that the media URL is being opened by the intended source resolver and protocol handler.
- Treat this as a capability mismatch, not as evidence of packet loss or server unavailability.
Microsoft: Networking in Media Foundation
Microsoft: Supported protocols for Media Foundation network sources
Diagnostic interpretation of MF_E_NET_STREAMGROUPS_NOT_SUPPORTED
MF_E_NET_STREAMGROUPS_NOT_SUPPORTED has the HRESULT value 0xC00D426E. AllStat records the condition as “Internal. Stream groups are not supported.%0”. For MF_E_NET_STREAMGROUPS_NOT_SUPPORTED, in practice, interpret that wording at the boundary owned by Media Foundation or Windows media pipeline state, rather than treating the value as a generic Windows message.
Evidence to capture for MF_E_NET_STREAMGROUPS_NOT_SUPPORTED
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0xC00D426E value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions MF_E_NET_STREAMGROUPS_NOT_SUPPORTED or the mf / net / streamgroups / supported operation.
- For MF_E_NET_STREAMGROUPS_NOT_SUPPORTED, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery for MF_E_NET_STREAMGROUPS_NOT_SUPPORTED
Retry MF_E_NET_STREAMGROUPS_NOT_SUPPORTED only when the owning API documents a transient state or after the condition described as “Internal. Stream groups are not supported.%0” has changed. For MF_E_NET_STREAMGROUPS_NOT_SUPPORTED, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.