| Previous | Next |
| MF_E_UNEXPECTED | MF_E_INVALIDTYPE |
MF_E_INVALIDNAME
Read this as a state transition
MF_E_INVALIDNAME (0xC00D36BC) is a failure result from Windows Media Foundation. The generated section above already contains the platform message; the useful extra information is that this result isolates a named attribute, stream, service, property, or object identifier is not accepted in the current API context.
The producer is the method that interprets the supplied name rather than the media payload, so diagnosis should begin with that object and its state rather than with a broad reinstall or an unrelated codec change. A representative occurrence is an attribute query passes a display label where the interface expects a canonical property name or GUID-derived key.
Checkpoint map
| Checkpoint | Question to answer |
|---|---|
| Input | What exact name, type, index, URL, position, media item, account, device, or setup package reached the method that interprets the supplied name rather than the media payload? |
| State | Was the object initialized, connected, started, stopped, committed, authorized, or ready when it evaluated a named attribute, stream, service, property, or object identifier is not accepted in the current API context? |
| Evidence | the exact UTF-16 name including length and terminator, owning interface, namespace or attribute store, and whether lookup is case-sensitive. |
| Completion | Which event, callback, output sample, provider result, or installer action should have followed this result? |
Record before the object changes
Collect this result data before automatic retries, Player navigation, device reconnection, source shutdown, or setup rollback destroys it. The minimum useful record contains the exact returning API, object identity, input identity, current lifecycle state, and the first lower-level failure.
A this result trace must not store credentials, license payloads, private keys, authorization headers, or unrelated library contents. Record identifiers, hashes, lengths, status values, and redacted endpoint information sufficient to correlate the event.
Test one hypothesis at a time
- Reproduce once with tracing enabled and preserve
0xC00D36BCbefore any fallback. - Verify the decisive observation: the exact UTF-16 name including length and terminator, owning interface, namespace or attribute store, and whether lookup is case-sensitive.
- Run the controlled comparison: call the same method with a documented name from the same object and keep all other arguments unchanged.
- Return to the result baseline, apply the supported correction, and create a new object generation if the old one entered a terminal state.
- Repeat the result test until the original call advances past this checkpoint and the expected output is validated.
Do not merge these HRESULTs
| HRESULT | Boundary indicated by its standard description |
|---|---|
MF_E_UNEXPECTED | An unexpected error has occurred in the operation requested; compare this boundary specifically with it. |
MF_E_INVALIDTYPE | Invalid type; compare this boundary specifically with it. |
MF_E_INVALIDINDEX | Invalid index; compare this boundary specifically with it. |
The codes compared with it can lead to the same user-facing “cannot play,” “operation failed,” or “setup failed” dialog. They remain technically different. Here, MF_E_NOT_FOUND means a valid lookup key was accepted but no matching value exists.
Confirm the correction
For this occurrence, use a documented identifier and preserve the original spelling; do not substitute an unrelated registry or file name. Avoid generic cleanup until the original artifact is copied and the producing state is known. A destructive reset during it diagnosis can remove evidence while leaving the actual policy, device, network, format, or lifecycle error unchanged.
Verification of it must use the same input and action that failed. Confirm the expected state transition and check that the workflow does not merely substitute another error after it disappears.
Authoritative references
- Media Foundation architecture — reference used for the checkpoint.
- Media Foundation error codes — reference used for the checkpoint.
- Media sources — reference used for the checkpoint.
- Media Foundation events — reference used for the checkpoint.
Looking for a different code? Search another status or error code.