What does HRESULT 0x8004029A (VFW_E_DVD_VMR9_INCOMPATIBLEDEC) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

VMR9 does not work with VPE-based hardware decoders. Causes, checks and safe retry.

Previous	Next
VFW_E_VMR_NO_PROCAMP_HW	VFW_E_NO_COPP_HW

VFW_E_DVD_VMR9_INCOMPATIBLEDEC

Exact result and bit fields

VFW_E_DVD_VMR9_INCOMPATIBLEDEC has the unsigned HRESULT value 2147746458 (0x8004029A) and the signed 32-bit representation -2147220838. AllStat describes it as “VMR9 does not work with VPE-based hardware decoders”. In the operation that produces this result, DVD graph construction pairs VMR-9 with a hardware decoder based on Video Port Extensions, a combination VMR-9 does not support.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 666 (0x029A). 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: the selected MPEG-2 decoder outputs through VPE.
Cause 2 for this HRESULT: graph policy forces VMR-9 despite a legacy hardware path.
Cause 3 for this HRESULT: an existing decoder in the graph constrains renderer choice.

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 graph construction pairs VMR-9 with a hardware decoder based on Video Port Extensions, a combination VMR-9 does not support.
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: decoder output transport and interfaces.
Evidence 2 for this HRESULT: renderer CLSID and graph-builder flags.
Evidence 3 for this HRESULT: candidate software or non-VPE decoders.

Correction strategy

Action 1 for this HRESULT: select a decoder that outputs compatible surfaces or samples.
Action 2 for this HRESULT: use a renderer appropriate for the VPE hardware path.
Action 3 for this HRESULT: avoid forcing VMR-9 before inspecting decoder transport.

Example incident

A DVD player forces VMR-9 while the machine selects an old VPE hardware decoder; choosing a software decoder 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 after changing decoder or renderer; reconnection cannot make VPE output compatible with VMR-9. 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_VP_NEGOTIATION_FAILED concerns a failed video-port negotiation, while it identifies an inherently unsupported VPE-decoder and VMR-9 pairing. 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.