| Previous | Next |
| MF_E_NOT_FOUND | MF_E_NO_CLOCK |
MF_E_NOT_AVAILABLE
What the code tells you
MF_E_NOT_AVAILABLE means the object recognizes the requested value or operation but cannot supply it in its current configuration or state.
The result comes from the component that owns the optional value or asynchronous state. A representative case is a duration query is made before a network source has completed enough opening work to publish duration.
Read the call sequence as a timeline. First, the application reaches the component that owns the optional value or asynchronous state. Next, the component evaluates the object recognizes the requested value or operation but cannot supply it in its present configuration or moment. A wrapper, user interface, or fallback path can report a less specific message afterward.
Build a useful incident record
- Exact request: method name, all identifiers, units, flags, stream number, requested action, and this result.
- Object state: the current lifecycle state, selected stream, pending operation, requested attribute, and the event sequence leading to the call.
- Correlation: callback cookie, object instance, URL or file identity, device identity, and timestamps from the same attempt.
- Underlying cause: the first Win32, COM, network, driver, policy, or component error reported before
0xC00D36D6.
Reproduce without erasing context
Use one controlled experiment: wait for the documented readiness event or enable the required stream, then repeat the identical query. A useful comparison for this result changes exactly that variable; changing content, account, proxy, device, components, and version together makes attribution impossible.
| Outcome | Interpretation |
|---|---|
| The same operation now succeeds | The changed precondition was relevant to the failure. |
| A more specific earlier HRESULT appears | Preserve it; this result was probably a wrapper or terminal state. |
| The operation advances and fails later | The condition is fixed even though the complete workflow still has another defect. |
| No behavior changes | Restore the original baseline and test another documented prerequisite instead of stacking workarounds. |
Comparison with adjacent conditions
| Related code | Why it is not interchangeable |
|---|---|
MF_E_NOT_FOUND | The specified object or value does not exist. |
MF_E_THINNING_UNSUPPORTED | This component does not support stream-thinning. |
MF_E_UNRECOVERABLE_ERROR_OCCURRED | An unrecoverable error has occurred. |
The important distinction is this: MF_E_NOT_FOUND indicates absence from a namespace, while it commonly reflects temporary or configuration-dependent availability. Use the symbolic constant and 0xC00D36D6 value to distinguish states that share a similar visible message.
Resolution and proof
Apply the narrow remedy: move the request to the supported state or provide the prerequisite data; repeated blind polling can hide the event-order bug. Then discard stale media objects, pending callbacks, cached provider sessions, or installer state as appropriate and rerun the exact request that originally returned it.
References
Looking for a different code? Search another status or error code.