| Previous | Next |
| VFW_E_CANNOT_LOAD_SOURCE_FILTER | VFW_E_INVALID_FILE_VERSION |
VFW_E_FILE_TOO_SHORT
Meaning
Windows documents VFW_E_FILE_TOO_SHORT as “A file appeared to be incomplete”. In practical terms, it is returned when DirectShow determines that a media file ends before enough data is available to parse or render it.
Evidence to collect
- Capture 1: actual file length and expected minimum structure.
- Capture 2: transfer completion status and content-length metadata.
- Capture 3: parser read offset at end-of-file.
Where the failure belongs
This result belongs to DirectShow filter-graph processing. The relevant condition is that DirectShow determines that a media file ends before enough data is available to parse or render it.
Likely causes
- Possible cause 1: download or copy was truncated.
- Possible cause 2: the file contains only a partial header or index.
- Possible cause 3: a live-growing file is opened before required structures are written.
Diagnostic sequence
- Confirm that the observed path matches this condition: DirectShow determines that a media file ends before enough data is available to parse or render it.
Correct handling and retry
- Corrective action 1: obtain the complete file.
- Corrective action 2: wait for producer finalization when consuming growing output.
- Corrective action 3: use atomic publish semantics so readers do not see partial media.
Retry guidance. Retry when file length increases or a complete replacement is available; repeated parsing of unchanged bytes cannot succeed.
Difference from nearby HRESULTs
VFW_E_INVALID_FILE_FORMAT can describe malformed complete data, while it specifically indicates insufficient file length.
Practical scenario
A player opens a file while another process is still copying it and reaches EOF in the header; publishing only after copy completion prevents it.
Official Microsoft references
Looking for a different code? Search another status or error code.