| Previous | Next |
| ERROR_GRAPHICS_VIDPN_SOURCE_IN_USE | ERROR_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL |
ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN
What Windows rejected: graphics cant access active vidpn
Windows reports ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN (0xC0262343) at the vidpn checkpoint. Here, the caller requested an access mode that is forbidden while the VidPN is active. That narrows the first investigation to active VidPN mutability boundary instead of the entire GPU stack.
Build a useful diagnostic record
| Capture item | Why it matters |
|---|---|
| Object identity | active VidPN mutability boundary |
| Rejected condition | the caller requested an access mode that is forbidden while the VidPN is active |
| What to capture | VidPN handle, active flag, requested interface operation and transaction or commit state |
| Current graph state | VidPN, topology, source and target mode sets, and the present path connecting them |
| Supporting trace | source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data |
Separate state from capability
- Clone or reacquire a modifiable VidPN and repeat outside active ownership.
The comparison with ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED is especially useful: ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED narrows the restriction to topology mutation.
Verify the repaired path
Use the documented query interface for active state and modify a separate candidate topology.
- debug-layer, ETW or driver diagnostics no longer report the rejected active VidPN mutability boundary contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the active VidPN mutability.
- 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.