| 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.
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.
Capture before recreating objects
| Capture item | Why it matters |
|---|---|
| Supporting trace | output certificate, OPM semantics, sequence number, command GUID, protection level and connector status |
| Object identity | protected-output user-accessible bus capability |
| Rejected condition | the display driver does not support the UAB mechanism required by the requested protected-output operation |
| What to 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 |
Reproduce one variable at a time
- Capture the failing state. Record driver model, output type, protection semantics, OPM certificate and capability query.
- Run the capability query on an output known to support the required protected path.
The comparison with ERROR_GRAPHICS_OPM_NOT_SUPPORTED is especially useful: ERROR_GRAPHICS_OPM_NOT_SUPPORTED means OPM as a whole is unavailable.
Recovery contract
Treat the capability as unavailable and select another compliant output or playback policy.
- debug-layer, ETW or driver diagnostics no longer report the rejected protected-output user-accessible bus capability contract during the same scenario.
Implementation notes
A production fallback 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.
Technical references
- Microsoft: Supporting Output Protection Manager — background for the protected-output user-accessible bus capability.
- 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.