What does HRESULT 0x80040275 (VFW_E_NO_CAPTURE_HARDWARE) mean?

 
Previous Next
VFW_E_NO_VP_HARDWARE VFW_E_DVD_OPERATION_INHIBITED

VFW_E_NO_CAPTURE_HARDWARE

Exact result and bit fields

VFW_E_NO_CAPTURE_HARDWARE has the unsigned HRESULT value 2147746421 (0x80040275) and the signed 32-bit representation -2147220875. AllStat describes it as “No Capture hardware is available, or the hardware is not responding”. In the operation that produces this result, DirectShow cannot start the requested capture path because no usable capture hardware is present or responding.

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

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, device identifiers, registry values and stream metadata.

  • Evidence 1 for this HRESULT: device-enumerator results and symbolic link.
  • Evidence 2 for this HRESULT: Plug and Play state and driver error.
  • Evidence 3 for this HRESULT: open handles, exclusive-use owner and connection events.

Contract boundary

This result is a DirectShow contract failure whose owner must be identified from the exact interface, filter instance, graph generation and operation stage.

The practical owner to locate for this HRESULT is the filter graph, device or persisted configuration that first returned the result. 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.

Conditions that can produce it

  • Cause 1 for this HRESULT: the camera or tuner is disconnected.
  • Cause 2 for this HRESULT: the device driver failed to start.
  • Cause 3 for this HRESULT: another process has exclusive ownership of the hardware.

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: DirectShow cannot start the requested capture path because no usable capture hardware is present or responding.
  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.

Correction strategy

  • Action 1 for this HRESULT: prompt for or select an available capture device.
  • Action 2 for this HRESULT: release competing ownership and rebuild the capture graph.
  • Action 3 for this HRESULT: respond to removal and arrival notifications instead of retaining stale filters.

Example incident

A USB camera is unplugged while its moniker remains cached; re-enumerating devices before capture 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.

Retry and recovery

Retry rule for this HRESULT: Retry after the device becomes available; use bounded reconnection and preserve the original device identity. 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_AUDIO_HARDWARE concerns playback output, while it concerns an input device required by the capture graph. 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.