What does HRESULT 0x80040296 (VFW_E_VMR_NOT_IN_MIXER_MODE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The VMR has not yet created a mixing component. That is,.

Previous	Next
VFW_E_CERTIFICATION_FAILURE	VFW_E_VMR_NO_AP_SUPPLIED

VFW_E_VMR_NOT_IN_MIXER_MODE

Exact result and bit fields

VFW_E_VMR_NOT_IN_MIXER_MODE has the unsigned HRESULT value 2147746454 (0x80040296) and the signed 32-bit representation -2147220842. AllStat describes it as “The VMR has not yet created a mixing component. That is, IVMRFilterConfig::SetNumberofStreams has not yet been called”. In the operation that produces this result, a mixer-specific VMR method is called before SetNumberOfStreams has created and enabled the mixing component.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 662 (0x0296). 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 tied to a legacy rendering or graphics-capability boundary. The result should be diagnosed from the selected renderer, adapter, driver, surface contract and graph topology rather than from the file extension alone.

The practical owner to locate for this HRESULT is the renderer, graphics driver, display connection and negotiated surfaces. 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: a mixer-specific VMR method is called before SetNumberOfStreams has created and enabled the mixing component.
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: the application assumes the VMR starts in mixer mode.
Cause 2 for this HRESULT: configuration occurs after input pins are connected.
Cause 3 for this HRESULT: a renderer rebuild loses the prior stream-count setting.

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 display identifiers, protected-content state, driver details and media paths.

Evidence 1 for this HRESULT: VMR-7 or VMR-9 identity.
Evidence 2 for this HRESULT: SetNumberOfStreams call and result.
Evidence 3 for this HRESULT: input connection order and current stream count.

Correction strategy

Action 1 for this HRESULT: configure the VMR before connecting its inputs.
Action 2 for this HRESULT: set an explicit stream count for mixing scenarios.
Action 3 for this HRESULT: reapply configuration after creating a new renderer instance.

Retry and recovery

Retry rule for this HRESULT: Retry after the VMR has entered mixer mode and the relevant mixer interface is reacquired. 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_VMR_NO_AP_SUPPLIED concerns renderless-mode allocator-presenter setup, while it concerns the missing mixing component. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.

Example incident

An overlay application calls IVMRMixerControl9 on a freshly added VMR-9 without setting the stream count; configuring two streams first removes 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.