| Previous | Next |
| VFW_E_DVD_CMD_CANCELLED | VFW_E_DVD_STATE_CORRUPT |
VFW_E_DVD_STATE_WRONG_VERSION
Exact result and bit fields
VFW_E_DVD_STATE_WRONG_VERSION has the unsigned HRESULT value 2147746436 (0x80040284) and the signed 32-bit representation -2147220860. AllStat describes it as “The data did not contain a recognized version”. In the operation that produces this result, the DVD Navigator rejects saved state data because its version is not recognized by the restoring implementation.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 644 (0x0284). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
Conditions that can produce it
- Cause 1 for this HRESULT: bookmark data was created by an incompatible component version.
- Cause 2 for this HRESULT: application storage wrapped or altered the state blob.
- Cause 3 for this HRESULT: old state was retained across a format-breaking upgrade.
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: the DVD Navigator rejects saved state data because its version is not recognized by the restoring implementation.
- 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.
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: state-object producer version.
- Evidence 2 for this HRESULT: serialized state length and version field.
- Evidence 3 for this HRESULT: DVD Navigator and application build versions.
Correction strategy
- Action 1 for this HRESULT: discard incompatible bookmarks and create new state.
- Action 2 for this HRESULT: version application wrappers separately from the opaque DVD state.
- Action 3 for this HRESULT: never edit or reinterpret opaque IDvdState data.
Example incident
An upgrade loads a bookmark saved by an older DVD Navigator build and restoration rejects its version; invalidating old bookmarks resolves it. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.
Retry and recovery
Retry rule for this HRESULT: Retry only with state produced in a compatible format; falling back to normal disc start is safer than repeatedly restoring invalid state. 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_STATE_CORRUPT means state data is damaged, while it means it is structurally from an unsupported revision. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
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.