| Previous | Next |
| ERROR_GRAPHICS_CANT_ACCESS_ACTIVE_VIDPN | ERROR_GRAPHICS_INVALID_PATH_CONTENT_GEOMETRY_TRANSFORMATION |
ERROR_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL
Interpret the result in its owning layer: graphics invalid path importance ordinal
ERROR_GRAPHICS_INVALID_PATH_IMPORTANCE_ORDINAL (0xC0262344) belongs to the vidpn layer. It marks the path importance ordinal is outside the valid unique ordering for the topology, rather than a generic rendering failure. The object that owns the decision is present-path priority ordering.
Audit the full ordinal map
Importance is a topology-wide ordering property, not an arbitrary priority attached independently to each path. Dump every source-target pair and its ordinal, then check range and uniqueness after sorting. Preserve which path represents the primary view and which paths were added later. Repair by rebuilding a compact ordering for the whole topology instead of incrementing one path until an unused number happens to appear.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| Rejected condition | the path importance ordinal is outside the valid unique ordering for the topology |
| What to capture | path source/target IDs, all assigned ordinals, path count and recommendation context |
| 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 |
| Object identity | present-path priority ordering |
Reproduce one variable at a time
- Capture the failing state. Record path source/target IDs, all assigned ordinals, path count and recommendation context.
- Assign a unique ordinal within the available range and compare.
The comparison with ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS is especially useful: ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS means the valid ordinal space is exhausted.
Recovery contract
Allocate ordinals from the topology instead of reusing a fixed value.
- debug-layer, ETW or driver diagnostics no longer report the rejected present-path priority ordering contract during the same scenario.
Implementation notes
Log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the present-path priority ordering.
- 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.