| Previous | Next |
| MF_E_NET_REQUIRE_NETWORK | MF_E_NET_BWLEVEL_NOT_SUPPORTED |
MF_E_NET_REQUIRE_ASYNC
Read this as a state transition
MF_E_NET_REQUIRE_ASYNC means the network component requires the operation to use the asynchronous Media Foundation contract.
The result comes from the network source or byte-stream entry point that refuses a synchronous invocation. A representative case is a network source cannot complete source resolution synchronously without blocking its protocol state machine.
Evidence to preserve
the called method, callback object, work-queue context, URL, pending operation state, and whether the API documents Begin/End semantics.
Record before the object changes
Test one hypothesis at a time
- Record and verify: the called method, callback object, work-queue context, URL, pending operation state, and whether the API documents Begin/End semantics.
- Run the controlled comparison: invoke the documented asynchronous form with a callback and wait for the matching completion result.
Do not merge these HRESULTs
| HRESULT | Meaning in the standard description |
|---|---|
MF_E_NETWORK_RESOURCE_FAILURE | An attempt to acquire a network resource failed. |
MF_E_NET_REQUIRE_INPUT | Internal; Entry cannot complete operation without input. |
MF_E_OFFLINE_MODE | The requested URL is not available in offline mode. |
Here, MF_E_OPERATION_IN_PROGRESS reports overlapping work even when the correct async API is used.
Confirm the correction
For this occurrence, move the operation to the async contract rather than blocking a Media Foundation work queue.
Authoritative references
Looking for a different code? Search another status or error code.