| Previous | Next |
| TPC_E_RECOGNIZER_NOT_REGISTERED | TPC_E_INVALID_RIGHTS |
VFW_E_CORRUPT_GRAPH_FILE
Meaning and numerical form
VFW_E_CORRUPT_GRAPH_FILE is HRESULT 2147746357 (0x80040235; signed -2147220939). AllStat records its meaning as “Cannot render the file because it is corrupt”. In practical terms, it is returned when DirectShow cannot load a persisted graph because the graph file is corrupt or internally inconsistent.
The severity bit in 0x80040235 is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 565 (0x0235). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
Where the failure belongs
This result belongs to DirectShow filter-graph processing. DirectShow is a legacy, component-based media pipeline. Graph state, pin transport, negotiated media types, allocators, clocks, samples, renderers and source filters contribute separate contracts to the operation. The decisive condition is this: DirectShow cannot load a persisted graph because the graph file is corrupt or internally inconsistent. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.
Likely causes
- Possible cause 1 for this HRESULT: serialized storage is truncated.
- Possible cause 2 for this HRESULT: CLSID or connection records are damaged.
- Possible cause 3 for this HRESULT: a writer failed midway and left partially updated graph data.
Evidence to collect
A useful diagnostic record for this result includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for this HRESULT: file hash, length and storage structure.
- Capture 2 for this HRESULT: first invalid filter or connection record.
- Capture 3 for this HRESULT: writer version and completion status.
Telemetry for this HRESULT should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing media content, file paths, device identifiers or credentials.
Diagnostic sequence
- Capture it at the first native return and identify the exact object and method.
- Confirm that the observed path matches this condition: DirectShow cannot load a persisted graph because the graph file is corrupt or internally inconsistent.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Correction and retry boundary
- Corrective action 1 for this HRESULT: restore a known-good graph file or rebuild the topology.
- Corrective action 2 for this HRESULT: write graph files atomically through a temporary file.
- Corrective action 3 for this HRESULT: validate persistence output before replacing the previous version.
Retry guidance for this HRESULT. Retry only with different bytes or after rebuilding; reopening the identical corrupt file has no recovery value. A retry must avoid this hazard: replay obsolete samples, duplicate graph changes or reuse interfaces from an earlier topology generation. It must also preserve the evidence needed to locate the original producer of it.
Practical scenario
A crash occurs while overwriting a saved graph and leaves partial structured storage; atomic replacement prevents it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Difference from nearby HRESULTs
VFW_E_INVALID_FILE_FORMAT applies to media-file parsing generally; it specifically concerns a persisted DirectShow graph. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for this HRESULT should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.
Operational repair for this HRESULT should use supported filter installation, device, graph-building and renderer configuration paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: DirectShow graph building
- Microsoft: IGraphBuilder::RenderFile
Looking for a different code? Search another status or error code.