| Previous | Next |
| ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED | ERROR_GRAPHICS_NOT_A_LINKED_ADAPTER |
ERROR_GRAPHICS_CHILD_DESCRIPTOR_NOT_SUPPORTED
Interpret the result in its owning layer: graphics child descriptor not supported
Windows reports ERROR_GRAPHICS_CHILD_DESCRIPTOR_NOT_SUPPORTED (0xC0262401) at the child checkpoint. Here, the selected child device cannot provide EDID or another requested descriptor through this interface. That narrows the first investigation to child descriptor exposure capability instead of the entire GPU stack.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| Supporting trace | child UID, HPD awareness, monitor descriptor support, PnP events and connector telemetry |
| Object identity | child descriptor exposure capability |
| Rejected condition | the selected child device cannot provide EDID or another requested descriptor through this interface |
| What to capture | child UID, child type, descriptor type, hot-plug awareness and driver capabilities |
| Current graph state | display-adapter child, monitor PDO and connector-presence state |
Reproduce one variable at a time
- Query a descriptor-capable monitor child and compare with the unsupported child type.
The comparison with ERROR_GRAPHICS_INVALID_MONITORDESCRIPTOR is especially useful: ERROR_GRAPHICS_INVALID_MONITORDESCRIPTOR means a descriptor was supplied but malformed.
Recovery contract
Branch on descriptor support and use fixed or driver-supplied modes when the child has no descriptor.
- debug-layer, ETW or driver diagnostics no longer report the rejected child descriptor exposure capability contract during the same scenario.
Technical references
- Microsoft: Child device enumeration — background for the child descriptor exposure capability.
- Microsoft: Monitor child devices
- Microsoft: Introduction to VidPNs
- Microsoft: Graphics error codes
Looking for a different code? Search another status or error code.