| Previous | Next |
| MF_E_NET_UDP_BLOCKED | MF_E_NET_PROTOCOL_DISABLED |
MF_E_NET_UNSUPPORTED_CONFIGURATION
MF_E_NET_UNSUPPORTED_CONFIGURATION means the selected network-source configuration is not supported by the source, protocol, or platform.
What to check for MF_E_NET_UNSUPPORTED_CONFIGURATION
- Compare application-set network properties with the protocol capabilities of the selected source.
- Disable unsupported optional controls rather than changing unrelated transport settings.
- Use logging to confirm which protocol and transport were actually selected.
Microsoft: Networking in Media Foundation
Microsoft: Supported protocols for Media Foundation network sources
Microsoft: Media Foundation client logging
Diagnostic interpretation of MF_E_NET_UNSUPPORTED_CONFIGURATION
MF_E_NET_UNSUPPORTED_CONFIGURATION has the HRESULT value 0xC00D4293. AllStat records the condition as “The specified configuration value is not supported.%0”. For MF_E_NET_UNSUPPORTED_CONFIGURATION, 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_UNSUPPORTED_CONFIGURATION
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0xC00D4293 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_UNSUPPORTED_CONFIGURATION or the mf / net / configuration operation.
- Reproduce MF_E_NET_UNSUPPORTED_CONFIGURATION with the smallest valid input and note whether the result changes with identity, architecture, service state, or target object.
Retry and recovery for MF_E_NET_UNSUPPORTED_CONFIGURATION
Retry MF_E_NET_UNSUPPORTED_CONFIGURATION only when the owning API documents a transient state or after the condition described as “The specified configuration value is not supported.%0” has changed. For MF_E_NET_UNSUPPORTED_CONFIGURATION, 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.