What does HRESULT 0x80040216 (VFW_E_NOT_FOUND) mean?

 
Previous Next
VFW_E_NO_INTERFACE VFW_E_CANNOT_CONNECT

VFW_E_NOT_FOUND

Meaning and numerical form

VFW_E_NOT_FOUND is HRESULT 2147746326 (0x80040216; signed -2147220970). AllStat records its meaning as “An object or name was not found”. In practical terms, it is returned when a DirectShow lookup cannot find the requested filter, pin, object or name in its current scope.

The severity bit in 0x80040216 is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 534 (0x0216). Those fields classify the value but do not identify the component instance, call, object or input that produced it.

Where the failure belongs

This result belongs to DirectShow filter-graph processing. DirectShow is a legacy, component-based media pipeline. Graph state, pin transport, negotiated media types, allocators, clocks, samples, renderers and source filters contribute separate contracts to the operation. The decisive condition is this: a DirectShow lookup cannot find the requested filter, pin, object or name in its current scope. Record the first native producer instead of relying only on a framework exception translated several layers later.

Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.

Likely causes

  • Possible cause 1 for it: the filter or pin was removed during graph reconstruction.
  • Possible cause 2 for it: the caller uses a display name that does not match the registered component.
  • Possible cause 3 for it: enumeration was performed in another device category or graph instance.

Evidence to collect

A useful this result record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.

  • Capture 1 for it: requested name or identifier and lookup scope.
  • Capture 2 for it: current graph filter and pin enumeration.
  • Capture 3 for it: device-category registration and hardware presence.

Telemetry for it should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing media content, file paths, device identifiers or credentials.

Diagnostic sequence

  1. Capture it at the first native return and identify the exact object and method.
  2. Confirm that the observed path matches this the condition: a DirectShow lookup cannot find the requested filter, pin, object or name in its current scope.
  3. compare the live state with the method contract before changing configuration.
  4. collect the code-specific evidence listed above and preserve any more specific preceding error.
  5. change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
  6. Add a regression check that distinguishes it from the related outcomes described below.

Correction and retry boundary

  • Corrective action 1 for it: enumerate the current scope and use stable identifiers where available.
  • Corrective action 2 for it: invalidate cached names after graph or device changes.
  • Corrective action 3 for it: distinguish optional absence from installation failure.

Retry guidance for it. Retry after enumeration changes or device arrival; repeated lookup of the same absent name should be bounded. A it retry must avoid this hazard: replay obsolete samples, duplicate graph changes or reuse interfaces from an earlier topology generation. It must also preserve the evidence needed to locate the original producer of it.

Practical scenario

A capture device is unplugged after its friendly name is cached; re-enumerating devices prevents repeated it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.

Difference from nearby HRESULTs

VFW_E_ENUM_OUT_OF_RANGE means enumeration reached its end, while it means a particular requested object or name was not located. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.

Developer and operational guidance

Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for it should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.

Operational repair for it should use supported filter installation, device, graph-building and renderer configuration paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.

Official Microsoft references

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