| Previous | Next |
| MF_E_PEAUTH_SESSION_NOT_STARTED | MF_E_PEAUTH_PUBLICKEY_REVOKED |
MF_E_INSUFFICIENT_BUFFER
What the code tells you
MF_E_INSUFFICIENT_BUFFER means the caller-provided output buffer cannot hold the Media Foundation response.
The result comes from the API that serializes an attribute, string, blob, list, or query result into caller storage. A representative case is a method reports the required byte count for a codec or attribute list, but the caller treats it as a WCHAR count.
Evidence to preserve
supplied size, required size if returned, element count, character versus byte units, structure version, and whether the result changed between calls.
Build a useful incident record
Reproduce without erasing context
- Record and verify: supplied size, required size if returned, element count, character versus byte units, structure version, and whether the result changed between calls.
- Run the controlled comparison: perform the documented size-query call, allocate that exact requirement plus required terminator, and call again.
Comparison with adjacent conditions
| HRESULT | Meaning in the standard description |
|---|---|
MF_E_REBOOT_REQUIRED | We need to reboot the machine. |
MF_E_NO_INDEX | The index that is necessary for the requested action is not found. |
MF_E_ALREADY_INITIALIZED | This object has already been initialized and cannot be re-initialized at this time. |
Here, MF_E_RT_OUTOFMEMORY is failure to obtain runtime resources, while this code says the caller buffer is too small.
Resolution and proof
For this occurrence, use the two-call sizing pattern and validate integer arithmetic before allocation.
Authoritative references
Looking for a different code? Search another status or error code.