What does HRESULT 0xC0262400 (ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED) mean?

ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED

Interpret the result in its owning layer: graphics specified child already connected

ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED, value 0xC0262400, is produced by child when the child output already has an external device associated with it. The investigation should stay attached to display-child connector occupancy and to the exact generation in which it was obtained.

This result: A child UID identifies an output of the adapter, not necessarily a permanently attached monitor. Presence and descriptor capability must be re-evaluated after hot-plug. 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

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 this result.

Reproduce one variable at a time

1. Freeze the result generation. Record child UID, connector, previous arrival event, monitor PDO and attempted association. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
2. Run the narrow this result comparison. disconnect the existing child cleanly before associating the test device. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
3. Observe the layer after it. for it, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the boundary was crossed.
4. Repeat it through a lifecycle transition. for it, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that it does not reuse stale handles.

The comparison with ERROR_GRAPHICS_MONITOR_NOT_CONNECTED is especially useful: ERROR_GRAPHICS_MONITOR_NOT_CONNECTED reports the opposite physical state for a VidPN target. Recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Recovery contract

Deduplicate hot-plug events and maintain one current external device per child connector. Repair of it 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 result 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 it; unrelated adapter, monitor and application state remains unchanged.
• debug-layer, ETW or driver diagnostics no longer report the rejected display-child connector occupancy contract during the same scenario.
• The application handles recurrence of it without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes

Log child UID, HPD awareness, monitor descriptor support, PnP events and connector telemetry. When the 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 it 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 it.

Technical references

• Microsoft: Child device enumeration — background for the display-child connector occupancy boundary involved in it.
• Microsoft: Monitor child devices
• Microsoft: Introduction to VidPNs
• Microsoft: Graphics error codes

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