| Previous | Next |
| VFW_E_OUT_OF_VIDEO_MEMORY | VFW_E_DDRAW_CAPS_NOT_SUITABLE |
VFW_E_VP_NEGOTIATION_FAILED
Meaning
Windows documents VFW_E_VP_NEGOTIATION_FAILED as “The VideoPort connection negotiation process has failed”. Here, the Overlay Mixer and video-port path cannot agree on the hardware transport, surface or format needed for a VideoPort connection.
Relevant contract
Start with the renderer, graphics driver, display connection and negotiated surfaces.
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: IVPConfig or related capability exchange.
- Evidence 2: source format, destination surface and connection index.
- Evidence 3: graphics driver version and negotiation step that failed.
Conditions that can produce it
- Cause 1: capture or decoder hardware advertises incompatible video-port capabilities.
- Cause 2: the display driver rejects the requested connection parameters.
- Cause 3: format or surface changes occur during negotiation.
Retry and recovery
Retry rule: Retry after a real capability or topology change; repeated negotiation with the same hardware tuple is deterministic.
Correction strategy
- Action 1: select a compatible transport or renderer.
- Action 2: rebuild the graph after stabilizing the video format.
- Action 3: avoid forcing VideoPort use when a memory-based path is available.
Example incident
An analog capture device exposes a video port that the current display driver cannot bind to the Overlay Mixer; choosing a memory-delivery capture path avoids it.
How it differs from nearby results
VFW_E_NO_VP_HARDWARE means no usable VideoPort hardware exists, whereas it means hardware was found but the connection contract failed.
Official Microsoft references
Looking for a different code? Search another status or error code.