What does HRESULT 0x8004025C (VFW_E_UNSUPPORTED_AUDIO) mean?

 
Previous Next
VFW_E_PROCESSOR_NOT_SUITABLE VFW_E_UNSUPPORTED_VIDEO

VFW_E_UNSUPPORTED_AUDIO

Exact result and bit fields

VFW_E_UNSUPPORTED_AUDIO has the unsigned HRESULT value 2147746396 (0x8004025C) and the signed 32-bit representation -2147220900. AllStat describes it as “Cannot play back the audio stream: the audio format is not supported”. In the operation that produces this result, the graph cannot produce playable audio from the stream format even though an audio track was identified.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 604 (0x025C). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.

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.

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: audio subtype, format tag, sample rate, channels and bit depth.
  • Evidence 2 for this HRESULT: decoder candidates and connection failures.
  • Evidence 3 for this HRESULT: whether another audio track in the same file can render.

Conditions that can produce it

  • Cause 1 for this HRESULT: the codec or profile is unsupported.
  • Cause 2 for this HRESULT: the decoder accepts the subtype but rejects channel layout or sample parameters.
  • Cause 3 for this HRESULT: policy blocks the only third-party audio transform.

Step-by-step diagnosis

  1. Capture it at the first native return, not only at the top-level playback failure.
  2. identify the exact graph stage described here: the graph cannot produce playable audio from the stream format even though an audio track was identified.
  3. compare the live object state, topology and input with the documented interface preconditions.
  4. Before changing filters, drivers, registry data or media for this HRESULT, collect the code-specific evidence below.
  5. Test one evidence-backed the correction on the smallest reproducible graph.
  6. Verify that the corrected run no longer returns it and does not merely replace it with a nearby HRESULT.

Retry and recovery

Retry rule for this HRESULT: Retry after changing the selected track, decoder inventory or media asset. 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.

Correction strategy

  • Action 1 for this HRESULT: choose a supported audio track or decoder.
  • Action 2 for this HRESULT: transcode the audio while preserving the video stream when appropriate.
  • Action 3 for this HRESULT: surface the exact format parameters in diagnostics.

Example incident

A file contains supported video and an unusual multichannel audio profile; selecting its stereo track allows playback and isolates it to the original track. 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.

How it differs from nearby results

VFW_E_NO_AUDIO_HARDWARE concerns output-device availability; it concerns decoding or connecting the audio format. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.

Official Microsoft references

Looking for a different code? Search another status or error code.