| Previous | Next |
| VFW_E_DVD_NO_BUTTON | VFW_E_DVD_RENDERFAIL |
VFW_E_DVD_GRAPHNOTREADY
Exact result and bit fields
VFW_E_DVD_GRAPHNOTREADY has the unsigned HRESULT value 2147746425 (0x80040279) and the signed 32-bit representation -2147220871. AllStat describes it as “DVD-Video playback graph has not been built yet”. In the operation that produces this result, DVD navigation or information is requested before the DVD-Video playback graph has been built successfully.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 633 (0x0279). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
Contract boundary
This result belongs to the legacy DirectShow DVD Navigator contract. DVD state is authored and stateful: domains, user-operation controls, titles, menus, streams, command objects and graph construction each impose different preconditions.
The practical owner to locate for this HRESULT is the DVD Navigator, graph builder, decoder inventory and renderer topology. 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: DVD navigation or information is requested before the DVD-Video playback graph has been built successfully.
- 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.
Conditions that can produce it
- Cause 1 for this HRESULT: IDvdGraphBuilder has not completed RenderDvdVideoVolume.
- Cause 2 for this HRESULT: graph construction is still asynchronous in application control flow.
- Cause 3 for this HRESULT: a previous graph was torn down but stale DVD interfaces remain.
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 disc identifiers, navigation state, parental settings and media paths.
- Evidence 1 for this HRESULT: graph-build call and HRESULT.
- Evidence 2 for this HRESULT: filter list and connection state.
- Evidence 3 for this HRESULT: interface generation and ready-state transition.
Correction strategy
- Action 1 for this HRESULT: do not expose DVD controls until graph construction succeeds.
- Action 2 for this HRESULT: release interfaces when rebuilding or closing the graph.
- Action 3 for this HRESULT: preserve the underlying build failure instead of continuing into navigation.
Retry and recovery
Retry rule for this HRESULT: Retry after a successful DVD graph build and reacquisition of IDvdControl2 or IDvdInfo2. 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_DVD_RENDERFAIL says graph construction failed, while it says the requested operation arrived before a usable graph exists. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
Example incident
A player creates the navigator and immediately queries title count before RenderDvdVideoVolume returns; waiting for graph readiness prevents 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.
Official Microsoft references
Looking for a different code? Search another status or error code.