HRESULT 0xC0262502 (ERROR_GRAPHICS_UAB_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The driver does not support UAB.

Previous	Next
ERROR_GRAPHICS_COPP_NOT_SUPPORTED	ERROR_GRAPHICS_OPM_INVALID_ENCRYPTED_PARAMETERS

ERROR_GRAPHICS_UAB_NOT_SUPPORTED

Interpret the result in its owning layer: graphics uab not supported

The useful interpretation of ERROR_GRAPHICS_UAB_NOT_SUPPORTED (0xC0262502) starts at the opm boundary: the display driver does not support the UAB mechanism required by the requested protected-output operation. In practical terms, inspect protected-output user-accessible bus capability before changing application-wide graphics settings.

ERROR_GRAPHICS_UAB_NOT_SUPPORTED: Output protection is a policy-enforcement path. For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, A fallback must respect the content policy; disabling HDCP or ignoring a signed-request failure is not a valid repair. For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, 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.

Capture before recreating objects

Capture item	Why it matters for `ERROR_GRAPHICS_UAB_NOT_SUPPORTED`
Supporting trace	output certificate, OPM semantics, sequence number, command GUID, protection level and connector status
Object identity	protected-output user-accessible bus capability
Rejected boundary	the display driver does not support the UAB mechanism required by the requested protected-output operation
Decisive capture	driver model, output type, protection semantics, OPM certificate and capability query
Current graph state	OPM protected-output session, signed request and display-miniport response

For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, 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_UAB_NOT_SUPPORTED.

Reproduce one variable at a time

Freeze the ERROR_GRAPHICS_UAB_NOT_SUPPORTED generation. Record driver model, output type, protection semantics, OPM certificate and capability query. Before diagnosing ERROR_GRAPHICS_UAB_NOT_SUPPORTED, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow ERROR_GRAPHICS_UAB_NOT_SUPPORTED comparison. run the capability query on an output known to support the required protected path. During the ERROR_GRAPHICS_UAB_NOT_SUPPORTED comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after ERROR_GRAPHICS_UAB_NOT_SUPPORTED. For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the ERROR_GRAPHICS_UAB_NOT_SUPPORTED boundary was crossed.
Repeat ERROR_GRAPHICS_UAB_NOT_SUPPORTED through a lifecycle transition. For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, 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_OPM_NOT_SUPPORTED is especially useful: ERROR_GRAPHICS_OPM_NOT_SUPPORTED means OPM as a whole is unavailable. For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Recovery contract

Treat the capability as unavailable and select another compliant output or playback policy. Repair of ERROR_GRAPHICS_UAB_NOT_SUPPORTED 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_UAB_NOT_SUPPORTED 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_UAB_NOT_SUPPORTED; unrelated adapter, monitor and application state remains unchanged.
For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, debug-layer, ETW or driver diagnostics no longer report the rejected protected-output user-accessible bus capability contract during the same scenario.
The application handles recurrence of ERROR_GRAPHICS_UAB_NOT_SUPPORTED without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `ERROR_GRAPHICS_UAB_NOT_SUPPORTED`

For ERROR_GRAPHICS_UAB_NOT_SUPPORTED, log output certificate, OPM semantics, sequence number, command GUID, protection level and connector status. When the ERROR_GRAPHICS_UAB_NOT_SUPPORTED 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_UAB_NOT_SUPPORTED 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_UAB_NOT_SUPPORTED.

Technical references

Microsoft: Supporting Output Protection Manager — background for the protected-output user-accessible bus capability boundary involved in ERROR_GRAPHICS_UAB_NOT_SUPPORTED.
Microsoft: Using the OPM DDI — background for the protected-output user-accessible bus capability boundary involved in ERROR_GRAPHICS_UAB_NOT_SUPPORTED.
Microsoft: Configuring a protected output — background for the protected-output user-accessible bus capability boundary involved in ERROR_GRAPHICS_UAB_NOT_SUPPORTED.
Microsoft: Using Output Protection Manager — background for the protected-output user-accessible bus capability boundary involved in ERROR_GRAPHICS_UAB_NOT_SUPPORTED.

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