| Previous | Next |
| ERROR_GRAPHICS_STALE_VIDPN_TOPOLOGY | ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY |
ERROR_GRAPHICS_MONITOR_NOT_CONNECTED
Locate the failing graphics boundary: graphics monitor not connected
ERROR_GRAPHICS_MONITOR_NOT_CONNECTED (0xC0262338) belongs to the vidpn layer. It marks the target ID is valid but no monitor is currently connected to it, rather than a generic rendering failure. The object that owns the decision is VidPN target connection state.
Evidence that makes the result actionable
| Capture item | Why it matters |
|---|---|
| Supporting trace | source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data |
| Object identity | VidPN target connection state |
| Rejected condition | the target ID is valid but no monitor is currently connected to it |
| What to capture | target ID, child status, connector type, EDID availability, hot-plug timestamp and current topology |
| Current graph state | VidPN, topology, source and target mode sets, and the present path connecting them |
A controlled comparison
- Disconnect and reconnect the specific monitor while querying the same target ID.
The comparison with ERROR_GRAPHICS_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE is especially useful: ERROR_GRAPHICS_NO_MONITORS_CORRESPOND_TO_DISPLAY_DEVICE concerns GDI-device mapping rather than a VidPN target.
Correction and proof
Handle the target as disconnected and rebuild choices after a fresh child/topology enumeration.
- debug-layer, ETW or driver diagnostics no longer report the rejected VidPN target connection state contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the VidPN target connection state.
- Microsoft: VidPN objects and interfaces
- Microsoft: Enumerating cofunctional VidPN modes
- Microsoft: Determining VidPN support
Looking for a different code? Search another status or error code.