What does HRESULT 0xC0262335 (ERROR_GRAPHICS_NO_VIDPNMGR) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Display adapter in question does not have an associated VidPN manager.

Previous	Next
ERROR_GRAPHICS_MONITOR_COULD_NOT_BE_ASSOCIATED_WITH_ADAPTER	ERROR_GRAPHICS_NO_ACTIVE_VIDPN

ERROR_GRAPHICS_NO_VIDPNMGR

What Windows rejected: graphics no vidpnmgr

The useful interpretation of ERROR_GRAPHICS_NO_VIDPNMGR (0xC0262335) starts at the vidpn boundary: the selected adapter does not expose a VidPN manager for the requested operation. In practical terms, inspect adapter display-mode manager availability before changing application-wide graphics settings.

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

Build a useful diagnostic record

Capture item	Why it matters for `ERROR_GRAPHICS_NO_VIDPNMGR`
Rejected boundary	the selected adapter does not expose a VidPN manager for the requested operation
Decisive capture	adapter LUID, driver model, render-only flag, output enumeration and DMM interface acquisition result
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	adapter display-mode manager availability

For ERROR_GRAPHICS_NO_VIDPNMGR, 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_NO_VIDPNMGR.

Separate state from capability

Freeze the ERROR_GRAPHICS_NO_VIDPNMGR generation. Record adapter LUID, driver model, render-only flag, output enumeration and DMM interface acquisition result. Before diagnosing ERROR_GRAPHICS_NO_VIDPNMGR, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow ERROR_GRAPHICS_NO_VIDPNMGR comparison. repeat against a display-capable adapter and a render-only adapter. During the ERROR_GRAPHICS_NO_VIDPNMGR comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after ERROR_GRAPHICS_NO_VIDPNMGR. For ERROR_GRAPHICS_NO_VIDPNMGR, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_NO_VIDPNMGR boundary was crossed.
Repeat ERROR_GRAPHICS_NO_VIDPNMGR through a lifecycle transition. For ERROR_GRAPHICS_NO_VIDPNMGR, 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 a manager exists but has no active topology. For ERROR_GRAPHICS_NO_VIDPNMGR, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Select an adapter with display outputs or avoid mode-management calls on render-only devices. Repair of ERROR_GRAPHICS_NO_VIDPNMGR 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_NO_VIDPNMGR 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_NO_VIDPNMGR; unrelated adapter, monitor and application state remains unchanged.
For ERROR_GRAPHICS_NO_VIDPNMGR, debug-layer, ETW or driver diagnostics no longer report the rejected adapter display-mode manager availability contract during the same scenario.
The application handles recurrence of ERROR_GRAPHICS_NO_VIDPNMGR without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `ERROR_GRAPHICS_NO_VIDPNMGR`

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

Technical references

Microsoft: Introduction to Video Present Networks — background for the adapter display-mode manager availability boundary involved in ERROR_GRAPHICS_NO_VIDPNMGR.
Microsoft: VidPN objects and interfaces — background for the adapter display-mode manager availability boundary involved in ERROR_GRAPHICS_NO_VIDPNMGR.
Microsoft: Enumerating cofunctional VidPN modes — background for the adapter display-mode manager availability boundary involved in ERROR_GRAPHICS_NO_VIDPNMGR.
Microsoft: Determining VidPN support — background for the adapter display-mode manager availability boundary involved in ERROR_GRAPHICS_NO_VIDPNMGR.

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