HRESULT 0xC026235B (ERROR_GRAPHICS_INVALID_CLIENT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Specified client type was not recognized.

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.

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

Evidence that makes this result actionable

Capture item	Why it matters for `ERROR_GRAPHICS_INVALID_CLIENT_TYPE`
Rejected boundary	the caller supplied a client type that DMM does not recognize
Decisive 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

For ERROR_GRAPHICS_INVALID_CLIENT_TYPE, 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_INVALID_CLIENT_TYPE.

A controlled comparison

Freeze the ERROR_GRAPHICS_INVALID_CLIENT_TYPE generation. Record client-type enum, API entry point, process/session context and requested VidPN operation. Before diagnosing ERROR_GRAPHICS_INVALID_CLIENT_TYPE, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow ERROR_GRAPHICS_INVALID_CLIENT_TYPE comparison. use the documented client classification for the same request. During the ERROR_GRAPHICS_INVALID_CLIENT_TYPE comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after ERROR_GRAPHICS_INVALID_CLIENT_TYPE. For ERROR_GRAPHICS_INVALID_CLIENT_TYPE, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_INVALID_CLIENT_TYPE boundary was crossed.
Repeat ERROR_GRAPHICS_INVALID_CLIENT_TYPE through a lifecycle transition. For ERROR_GRAPHICS_INVALID_CLIENT_TYPE, 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_CLIENTVIDPN_NOT_SET is especially useful: ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET means a recognized client has no client VidPN yet. For ERROR_GRAPHICS_INVALID_CLIENT_TYPE, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Correction and proof

Centralize client-type selection and reject unknown values before entering DMM. Repair of ERROR_GRAPHICS_INVALID_CLIENT_TYPE 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_INVALID_CLIENT_TYPE 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_INVALID_CLIENT_TYPE; unrelated adapter, monitor and application state remains unchanged.
For ERROR_GRAPHICS_INVALID_CLIENT_TYPE, debug-layer, ETW or driver diagnostics no longer report the rejected display-mode-management client classification contract during the same scenario.
The application handles recurrence of ERROR_GRAPHICS_INVALID_CLIENT_TYPE without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `ERROR_GRAPHICS_INVALID_CLIENT_TYPE`

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

Technical references

Microsoft: Introduction to Video Present Networks — background for the display-mode-management client classification boundary involved in ERROR_GRAPHICS_INVALID_CLIENT_TYPE.
Microsoft: VidPN objects and interfaces — background for the display-mode-management client classification boundary involved in ERROR_GRAPHICS_INVALID_CLIENT_TYPE.
Microsoft: Enumerating cofunctional VidPN modes — background for the display-mode-management client classification boundary involved in ERROR_GRAPHICS_INVALID_CLIENT_TYPE.
Microsoft: Determining VidPN support — background for the display-mode-management client classification boundary involved in ERROR_GRAPHICS_INVALID_CLIENT_TYPE.

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