| Previous | Next |
| VFW_E_DDRAW_CAPS_NOT_SUITABLE | VFW_E_NO_CAPTURE_HARDWARE |
VFW_E_NO_VP_HARDWARE
Meaning
Windows documents VFW_E_NO_VP_HARDWARE as “No VideoPort hardware is available, or the hardware is not responding”. Here, a graph requests a hardware VideoPort path but no responsive VideoPort device is available.
Relevant contract
Start with the renderer, graphics driver, display connection and negotiated surfaces.
Conditions that can produce it
- Cause 1: the adapter or capture device has no VideoPort support.
- Cause 2: the required hardware path is disabled by the driver.
- Cause 3: the device was removed or reset during graph construction.
Evidence worth preserving
Record lengths and hashes instead of raw content when the incident includes display identifiers, protected-content state, driver details and media paths.
- Evidence 1: adapter and capture-device capabilities.
- Evidence 2: device presence and driver events.
- Evidence 3: requested VideoPort interface and renderer mode.
Correction strategy
- Action 1: fall back to memory-based delivery where supported.
- Action 2: select compatible hardware and drivers for a required legacy path.
- Action 3: handle device loss by tearing down and rebuilding the branch.
Retry and recovery
Retry rule: Retry after device arrival, driver recovery or fallback-path selection.
How it differs from nearby results
VFW_E_VP_NEGOTIATION_FAILED indicates failed negotiation with present hardware; it indicates that the required hardware path is absent or unresponsive.
Example incident
A capture application assumes every analog tuner supports hardware video-port transfer; capability detection routes unsupported devices to a standard sample path and avoids it.
Official Microsoft references
Looking for a different code? Search another status or error code.