What does HRESULT 0xC026235A (ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION) mean?

ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION

What Windows rejected: graphics cancel vidpn topology augmentation

Windows reports ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION (0xC026235A) at the vidpn checkpoint. Here, the miniport asked DMM to stop augmenting the candidate topology for the specified source. That narrows the first investigation to driver-requested topology augmentation cancellation instead of the entire GPU stack.

ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION: VidPN handles and subobjects are generation-bound. For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, A monitor hot-plug, docking action, session switch or mode commit can invalidate an otherwise well-formed cached object. For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, the built-in one-line message identifies the immediate result; diagnosis also needs the producing API, object ownership and the display generation current at the time.

Build a useful diagnostic record

For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, preserve the unsigned HRESULT, symbolic name, first failing API and timestamp in one record. If cleanup later fails too, keep that secondary result separately from ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.

Separate state from capability

1. Freeze the ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION generation. Record source ID, candidate topology, augmentation reason, driver callback and preceding constraints. Before diagnosing ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION comparison. repeat with a minimal topology that does not require the rejected augmentation. During the ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION. For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION boundary was crossed.
4. Repeat ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION through a lifecycle transition. For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that this result does not reuse stale handles.

The comparison with ERROR_GRAPHICS_NO_RECOMMENDED_VIDPN_TOPOLOGY is especially useful: ERROR_GRAPHICS_NO_RECOMMENDED_VIDPN_TOPOLOGY means no recommendation could be produced. For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Honor the cancellation and let DMM choose another candidate instead of forcing the partial topology. Repair of ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION is complete only when the original call succeeds or returns its documented nonfatal status and the same lifetime test remains correct after a second display transition.

• The ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION trace identifies one producing API and one current graphics object, rather than only the final UI symptom.
• The passing run changes exactly the condition described for ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION; unrelated adapter, monitor and application state remains unchanged.
• For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, debug-layer, ETW or driver diagnostics no longer report the rejected driver-requested topology augmentation cancellation contract during the same scenario.
• The application handles recurrence of ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION

For ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION, log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data. When the ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION path returns a count, size, status flag or replacement object, retain it even on a nonfatal result because it can direct the next call.

A production fallback for ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION 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 for ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.

Technical references

• Microsoft: Introduction to Video Present Networks — background for the driver-requested topology augmentation cancellation boundary involved in ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.
• Microsoft: VidPN objects and interfaces — background for the driver-requested topology augmentation cancellation boundary involved in ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.
• Microsoft: Enumerating cofunctional VidPN modes — background for the driver-requested topology augmentation cancellation boundary involved in ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.
• Microsoft: Determining VidPN support — background for the driver-requested topology augmentation cancellation boundary involved in ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION.

Looking for a different code? Search another status or error code.