| Previous | Next |
| ERROR_GRAPHICS_TOPOLOGY_CHANGES_NOT_ALLOWED | ERROR_GRAPHICS_INCOMPATIBLE_PRIVATE_FORMAT |
ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS
Interpret the result in its owning layer: graphics no available importance ordinals
The useful interpretation of ERROR_GRAPHICS_NO_AVAILABLE_IMPORTANCE_ORDINALS (0xC0262354) starts at the vidpn boundary: every valid importance ordinal is already assigned in the topology. In practical terms, inspect present-path priority capacity before changing application-wide graphics settings.
Distinguish exhaustion from an invalid number
This result means all ordinals accepted by the topology are already consumed, so merely choosing another random integer cannot repair the request. Count active paths, list the assigned ordering and identify whether a stale path remained after a target was removed. A focused test removes one optional path, recomputes all ordinals and then adds the intended path using the newly available position.
Capture before recreating objects
| 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 | present-path priority capacity |
| Rejected condition | every valid importance ordinal is already assigned in the topology |
| What to capture | path count, ordinal map, duplicate detection and maximum supported paths |
| Current graph state | VidPN, topology, source and target mode sets, and the present path connecting them |
Reproduce one variable at a time
- Capture the failing state. Record path count, ordinal map, duplicate detection and maximum supported paths.
- Remove an unnecessary path or rebuild a compact ordinal assignment.
The comparison with ERROR_GRAPHICS_MAX_NUM_PATHS_REACHED is especially useful: ERROR_GRAPHICS_MAX_NUM_PATHS_REACHED is the adapter path-count limit.
Recovery contract
Allocate ordinals once after topology construction instead of incrementally leaking values.
- debug-layer, ETW or driver diagnostics no longer report the rejected present-path priority capacity 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.
A production fallback should be explicit: pause rendering, re-enumerate, rebuild one cache entry, recreate a device, or decline a protected path only when this layer calls for that action. Reinstalling every display component, deleting all caches or forcing a resolution change is not an evidence-based fix.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the present-path priority capacity.
- 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.