What does HRESULT 0x80040314 (VFW_E_CODECAPI_NO_CURRENT_VALUE) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

No current value. Practical DirectShow troubleshooting.

Previous	Next
VFW_E_CODECAPI_NO_DEFAULT	VFW_E_DVD_CHAPTER_DOES_NOT_EXIST

VFW_E_CODECAPI_NO_CURRENT_VALUE

Exact result and bit fields

VFW_E_CODECAPI_NO_CURRENT_VALUE has the unsigned HRESULT value 2147746580 (0x80040314) and the signed 32-bit representation -2147220716. AllStat describes it as “No current value”. In the operation that produces this result, a codec property has no readable current value in the codec’s present lifecycle or configuration state.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 788 (0x0314). 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: property GUID and support flags.
Evidence 2 for this HRESULT: codec initialization and streaming state.
Evidence 3 for this HRESULT: media type, profile and most recent successful SetValue call.

Conditions that can produce it

Cause 1 for this HRESULT: the encoder is not initialized with an input type.
Cause 2 for this HRESULT: the property is write-only or becomes meaningful only after streaming starts.
Cause 3 for this HRESULT: a profile change invalidated the previously active value.

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 codec property has no readable current value in the codec’s present lifecycle or configuration state.
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.

Retry and recovery

Retry rule for this HRESULT: Retry after initialization or state transition that makes the property active; polling an unchanged inactive codec is not useful. 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: defer the query until the documented lifecycle stage.
Action 2 for this HRESULT: retain an application-side desired value when the property is not readable.
Action 3 for this HRESULT: refresh values after type or profile negotiation.

Example incident

A rate-control property is queried before the encoder receives an output type and has no active value; moving the query after type negotiation prevents 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.

How it differs from nearby results

VFW_E_CODECAPI_NO_DEFAULT concerns absence of a recommended initial value; it concerns absence of a value in the current codec state. 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.