| Previous | Next |
| VFW_E_BUFFER_UNDERFLOW | VFW_E_NO_TRANSPORT |
VFW_E_UNSUPPORTED_STREAM
Exact result and bit fields
VFW_E_UNSUPPORTED_STREAM has the unsigned HRESULT value 2147746405 (0x80040265) and the signed 32-bit representation -2147220891. AllStat describes it as “Cannot play back the file. The format is not supported”. In the operation that produces this result, DirectShow recognizes the file but cannot render one or more streams because their format or combination is unsupported.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 613 (0x0265). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
Contract boundary
This result is a DirectShow contract failure whose owner must be identified from the exact interface, filter instance, graph generation and operation stage.
The practical owner to locate for it is the filter graph, device or persisted configuration that first returned the result. When handling this result, capture the native result before a wrapper replaces it with a generic exception, and keep the graph generation or object identity with the record.
Step-by-step diagnosis
- Capture it at the first native return, not only at the top-level playback failure.
- identify the exact graph stage described here: DirectShow recognizes the file but cannot render one or more streams because their format or combination is unsupported.
- compare the live object state, topology and input with the documented interface preconditions.
- Before changing filters, drivers, registry data or media for it, collect the code-specific evidence below.
- Test one evidence-backed the correction on the smallest reproducible graph.
- Verify that the corrected run no longer returns it and does not merely replace it with a nearby HRESULT.
Conditions that can produce it
- Cause 1 for it: the container includes an unsupported elementary stream.
- Cause 2 for it: the parser emits a subtype with no downstream path.
- Cause 3 for it: the file combines tracks in a way the selected source filter cannot expose correctly.
Evidence worth preserving
Log the interface and method, filter CLSID and friendly name, process and thread, graph state, connected pin names, media-type summary, renderer or device identity where relevant, and the first preceding HRESULT. Record lengths and hashes instead of raw content when the incident includes media paths, device identifiers, registry values and stream metadata.
- Evidence 1 for it: container type and complete track inventory.
- Evidence 2 for it: per-pin media types and render results.
- Evidence 3 for it: whether partial rendering succeeds for other streams.
Correction strategy
- Action 1 for it: select supported tracks or permit explicit partial playback.
- Action 2 for it: install approved transforms for required streams.
- Action 3 for it: convert the file when the source or parser cannot expose a usable topology.
Retry and recovery
Retry rule for it: Retry after track selection, filter inventory or file conversion changes. A safe it retry must use a changed capability, state, object generation or input. While recovering from it, preserve cancellation and avoid replaying side effects when the original operation may have partially completed.
How it differs from nearby results
VFW_E_UNKNOWN_FILE_TYPE means the container was not recognized; it means the container was recognized but a contained stream cannot be handled. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
Example incident
A container holds playable video plus an unsupported data stream and strict rendering treats the whole operation as failed; rendering only required pins avoids it. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.
Implementation notes
Code that handles it should preserve the original HRESULT, the failed stage and an opaque correlation identifier. After it, do not infer success from partial graph construction, and do not continue using interfaces retained from a graph or device generation that has already changed.
Operational remediation for it should favor supported component installation, device configuration and documented DirectShow calls. Manual registry or driver changes are appropriate only when the collected evidence for it points to that layer and a rollback is available.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: IGraphBuilder::RenderFile
- Microsoft: DirectShow media types
Looking for a different code? Search another status or error code.