What does HRESULT 0xC026235C (ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).

Previous	Next
ERROR_GRAPHICS_INVALID_CLIENT_TYPE	ERROR_GRAPHICS_SPECIFIED_CHILD_ALREADY_CONNECTED

ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET

Locate the failing graphics boundary: graphics clientvidpn not set

The useful interpretation of ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET (0xC026235C) starts at the vidpn boundary: no client-originated VidPN has been set for the adapter in the current session. In practical terms, inspect user-mode client VidPN state before changing application-wide graphics settings.

ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET: VidPN handles and subobjects are generation-bound. For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, A monitor hot-plug, docking action, session switch or mode commit can invalidate an otherwise well-formed cached object. For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, 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_CLIENTVIDPN_NOT_SET`
Decisive capture	adapter LUID, client type, prior mode-change calls, session state and current active VidPN
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	user-mode client VidPN state
Rejected boundary	no client-originated VidPN has been set for the adapter in the current session

For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, 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_CLIENTVIDPN_NOT_SET.

A controlled comparison

Freeze the ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET generation. Record adapter LUID, client type, prior mode-change calls, session state and current active VidPN. Before diagnosing ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET comparison. perform a documented user-mode display change and repeat the client-VidPN query. During the ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET. For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET boundary was crossed.
Repeat ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET through a lifecycle transition. For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, 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_NO_ACTIVE_VIDPN is especially useful: ERROR_GRAPHICS_NO_ACTIVE_VIDPN means the adapter itself lacks an active VidPN. For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Correction and proof

Treat the state as absent data and fall back to active/system topology where appropriate. Repair of ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET 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_CLIENTVIDPN_NOT_SET 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_CLIENTVIDPN_NOT_SET; unrelated adapter, monitor and application state remains unchanged.
For ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET, debug-layer, ETW or driver diagnostics no longer report the rejected user-mode client VidPN state contract during the same scenario.
The application handles recurrence of ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET`

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

Technical references

Microsoft: Introduction to Video Present Networks — background for the user-mode client VidPN state boundary involved in ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET.
Microsoft: VidPN objects and interfaces — background for the user-mode client VidPN state boundary involved in ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET.
Microsoft: Enumerating cofunctional VidPN modes — background for the user-mode client VidPN state boundary involved in ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET.
Microsoft: Determining VidPN support — background for the user-mode client VidPN state boundary involved in ERROR_GRAPHICS_CLIENTVIDPN_NOT_SET.

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