| Previous | Next |
| VFW_E_MPEG_NOT_CONSTRAINED | VFW_E_NO_TIME_FORMAT |
VFW_E_NOT_IN_GRAPH
Exact result and bit fields
VFW_E_NOT_IN_GRAPH has the unsigned HRESULT value 2147746399 (0x8004025F) and the signed 32-bit representation -2147220897. AllStat describes it as “Cannot perform the requested function on an object that is not in the filter graph”. In the operation that produces this result, an operation is invoked on a filter or related object that is not currently part of the target filter graph.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 607 (0x025F). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
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 this HRESULT: filter identity and owning graph pointer.
- Evidence 2 for this HRESULT: add/remove timestamps and graph generation.
- Evidence 3 for this HRESULT: calling thread and outstanding interface references.
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 this HRESULT 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.
Conditions that can produce it
- Cause 1 for this HRESULT: the filter was removed during reconfiguration.
- Cause 2 for this HRESULT: the caller retained an interface from an earlier graph generation.
- Cause 3 for this HRESULT: the object was created but never added to the graph.
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: an operation is invoked on a filter or related object that is not currently part of the target filter graph.
- compare the live object state, topology and input with the documented interface preconditions.
- Before changing filters, drivers, registry data or media for this HRESULT, 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.
Correction strategy
- Action 1 for this HRESULT: validate membership before graph-scoped operations.
- Action 2 for this HRESULT: discard stale interfaces after topology replacement.
- Action 3 for this HRESULT: serialize removal with operations that require graph ownership.
Example incident
A UI caches a filter interface, rebuilds the graph, then calls a graph-scoped method on the removed instance; reacquiring the current filter 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 this HRESULT should favor supported component installation, device configuration and documented DirectShow calls. Manual registry or driver changes are appropriate only when the collected evidence for this HRESULT points to that layer and a rollback is available.
Retry and recovery
Retry rule for this HRESULT: Retry after adding the object to the intended graph or reacquiring it from the current topology. 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_NOT_FOUND means an object could not be located, whereas it means the object exists but is outside the graph required by the operation. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: DirectShow filters and pins
- Microsoft: overview of DirectShow graph building
Looking for a different code? Search another status or error code.