| 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.
This result: Output protection is a policy-enforcement path. A fallback must respect the content policy; disabling HDCP or ignoring a signed-request failure is not a valid repair. 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 it |
|---|---|
| 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 |
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 this result.
Reproduce one variable at a time
- Freeze the result generation. Record driver model, output type, protection semantics, OPM certificate and capability query. Before diagnosing this result, do not resize, hot-plug, recreate or release the object under examination.
- Run the narrow this result comparison. run the capability query on an output known to support the required protected path. During the result comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
- Observe the layer after it. for it, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the boundary was crossed.
- Repeat it through a lifecycle transition. for it, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that it 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. 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 it 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 result 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 it; unrelated adapter, monitor and application state remains unchanged.
- 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 it without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.
Implementation notes
Log output certificate, OPM semantics, sequence number, command GUID, protection level and connector status. When the 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 it 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 it.
Technical references
- Microsoft: Supporting Output Protection Manager — background for the protected-output user-accessible bus capability boundary involved in it.
- Microsoft: Using the OPM DDI
- Microsoft: Configuring a protected output
- Microsoft: Using Output Protection Manager
Looking for a different code? Search another status or error code.