| Previous | Next |
| STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_NO_LONGER_EXISTS | STATUS_GRAPHICS_OPM_INVALID_INFORMATION_REQUEST |
STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS
The protected output is not a COPP-compatible output
STATUS_GRAPHICS_OPM_PROTECTED_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS is a Windows NTSTATUS value from the graphics/display facility. In this group, the status is tied to protected video output, OPM/COPP compatibility, PVP certificate validation, output-protection hardware, or the monitor configuration path.
OPM supports both OPM-native behavior and COPP-compatible behavior for older application models. This status means the caller used a COPP-style information or configuration path against a protected output whose semantics are OPM-native rather than COPP-compatible.
This is normally a caller/API mismatch. The display hardware may be able to protect the output, but the handle is being queried through the wrong semantic model. Review how the protected output was created and keep COPP-compatible information requests separate from OPM-native status requests.
What to check
- Log whether the protected output was created for COPP-compatible or OPM semantics.
- Use the matching get-information and configure calls for that semantics mode.
- Do not infer missing HDCP support until the same request is made through the correct protected-output model.
References
- Microsoft: Supporting Output Protection Manager
- Microsoft: Using Output Protection Manager
- Microsoft: Using Certified Output Protection Protocol
- Microsoft: Retrieving information about a protected output
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.