What does HRESULT 0xC0262340 (ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Specified target is not part of the specified VidPN's topology.

Previous	Next
ERROR_GRAPHICS_INVALID_PIXELVALUEACCESSMODE	ERROR_GRAPHICS_NO_DISPLAY_MODE_MANAGEMENT_SUPPORT

ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY

Interpret the result in its owning layer: graphics target not in topology

ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY (0xC0262340) belongs to the vidpn layer. It marks the requested target ID is absent from every present path in the supplied topology, rather than a generic rendering failure. The object that owns the decision is VidPN target membership.

Prove target membership from paths

A connected monitor or enumerated target does not automatically belong to every VidPN. Walk the candidate topology and match VidPnTargetId in each D3DKMDT_VIDPN_PRESENT_PATH. Capture the monitor child UID separately so a physical hot-plug event is not confused with logical topology membership. The controlled fix is to construct or select a path that references the target within the same candidate VidPN.

ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY: VidPN handles and subobjects are generation-bound. For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, A monitor hot-plug, docking action, session switch or mode commit can invalidate an otherwise well-formed cached object. For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, 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.

Capture before recreating objects

Capture item	Why it matters for `ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY`
Decisive capture	target ID, path enumeration, topology generation and monitor-child mapping
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	VidPN target membership
Rejected boundary	the requested target ID is absent from every present path in the supplied topology

For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, 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_TARGET_NOT_IN_TOPOLOGY.

Reproduce one variable at a time

Freeze the ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY generation. Record target ID, path enumeration, topology generation and monitor-child mapping. Before diagnosing ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY comparison. add a path to the target in a disposable topology and repeat the operation. During the ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY. For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY boundary was crossed.
Repeat ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY through a lifecycle transition. For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, 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_SOURCE_NOT_IN_TOPOLOGY is especially useful: ERROR_GRAPHICS_SOURCE_NOT_IN_TOPOLOGY applies to the source endpoint. For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Recovery contract

Derive target membership from current paths and reacquire after hot-plug. Repair of ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY 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_TARGET_NOT_IN_TOPOLOGY 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_TARGET_NOT_IN_TOPOLOGY; unrelated adapter, monitor and application state remains unchanged.
For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, debug-layer, ETW or driver diagnostics no longer report the rejected VidPN target membership contract during the same scenario.
The application handles recurrence of ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY`

For ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY, log source and target IDs, topology generation, path descriptors, pinned modes, mode-set handles and monitor timing data. When the ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY 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_TARGET_NOT_IN_TOPOLOGY 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_TARGET_NOT_IN_TOPOLOGY.

Technical references

Microsoft: Introduction to Video Present Networks — background for the VidPN target membership boundary involved in ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY.
Microsoft: VidPN objects and interfaces — background for the VidPN target membership boundary involved in ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY.
Microsoft: Enumerating cofunctional VidPN modes — background for the VidPN target membership boundary involved in ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY.
Microsoft: Determining VidPN support — background for the VidPN target membership boundary involved in ERROR_GRAPHICS_TARGET_NOT_IN_TOPOLOGY.

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