| Previous | Next |
| ERROR_GRAPHICS_CANCEL_VIDPN_TOPOLOGY_AUGMENTATION | ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET |
ERROR_GRAPHICS_INVALID_CLIENT_TYPE
Locate the failing graphics boundary: graphics invalid client type
ERROR_GRAPHICS_INVALID_CLIENT_TYPE (0xC026235B) belongs to the vidpn layer. It marks the caller supplied a client type that DMM does not recognize, rather than a generic rendering failure. The object that owns the decision is display-mode-management client classification.
Evidence that makes the result actionable
| Capture item | Why it matters |
|---|---|
| Rejected condition | the caller supplied a client type that DMM does not recognize |
| What to capture | client-type enum, API entry point, process/session context and requested VidPN operation |
| 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 | display-mode-management client classification |
A controlled comparison
- Use the documented client classification for the same request.
The comparison with ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET is especially useful: ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET means a recognized client has no client VidPN yet.
Correction and proof
Centralize client-type selection and reject unknown values before entering DMM.
- debug-layer, ETW or driver diagnostics no longer report the rejected display-mode-management client classification contract during the same scenario.
Technical references
- Microsoft: Introduction to Video Present Networks — background for the display-mode-management client classification.
- 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.