What does HRESULT 0x8004025D (VFW_E_UNSUPPORTED_VIDEO) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Cannot play back the video stream: the video format is not supported. Causes, checks and.

Previous	Next
VFW_E_UNSUPPORTED_AUDIO	VFW_E_MPEG_NOT_CONSTRAINED

VFW_E_UNSUPPORTED_VIDEO

Exact result and bit fields

VFW_E_UNSUPPORTED_VIDEO has the unsigned HRESULT value 2147746397 (0x8004025D) and the signed 32-bit representation -2147220899. AllStat describes it as “Cannot play back the video stream: the video format is not supported”. In the operation that produces this result, the playback graph cannot render the encoded video format or profile presented by the source.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 605 (0x025D). 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: no installed transform supports the subtype.
Cause 2 for this HRESULT: resolution, bit depth or profile exceeds decoder capability.
Cause 3 for this HRESULT: the selected renderer cannot accept any decoder output offered for the stream.

Contract boundary

This result describes a capability or format boundary in a component graph. Container recognition, elementary-stream parsing, decoder selection, property metadata and renderer acceptance are different stages and need separate evidence.

The practical owner to locate for this HRESULT is the source filter, decoder or codec property provider and downstream connection. 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 playback graph cannot render the encoded video format or profile presented by the source.
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 media paths, codec configuration, property values and stream metadata.

Evidence 1 for this HRESULT: video subtype, profile, level, dimensions and frame rate.
Evidence 2 for this HRESULT: decoder and renderer connection attempts.
Evidence 3 for this HRESULT: successful behavior with alternate streams or renderers.

Correction strategy

Action 1 for this HRESULT: install a compatible trusted decoder or convert the asset.
Action 2 for this HRESULT: choose a renderer appropriate for the produced surface type.
Action 3 for this HRESULT: perform format-capability checks before entering playback.

Example incident

A high-profile legacy MPEG stream is parsed but every decoder rejects its format block; transcoding to a supported profile prevents 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 after the stream, decoder or renderer path changes. 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_NO_DECOMPRESSOR emphasizes that no suitable decoder was found; it is the broader final outcome that the video stream cannot be played. 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.