| Previous | Next |
| ERROR_GRAPHICS_OPM_SESSION_TYPE_CHANGE_IN_PROGRESS | ERROR_GRAPHICS_OPM_INVALID_INFORMATION_REQUEST |
ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_COPP_SEMANTICS
The requested operation belongs to the other semantic mode
IOPMVideoOutput is created in one of two fixed modes: current OPM semantics or COPP compatibility semantics. The choice is made while obtaining the video output and remains unchanged for that object’s lifetime. This code means a caller sent a COPP-specific request to an object that uses OPM semantics.
The distinction matters for HDCP management. OPM semantics support device revocation and repeater handling through the OPM workflow, while the connected-device-information query is reserved for COPP emulation. Treating the two modes as interchangeable leads to the wrong command GUID or status request even when the display driver is functioning correctly.
Check the request contract
- Record the semantic mode selected at output creation together with the command or information GUID sent to the object.
- Use the OPM-specific protection flags and commands for an OPM-semantics output.
- Do not try to switch the existing object to COPP mode. Release it and obtain a new output only when backward-compatible COPP behavior is the intended contract.
References
- Microsoft: OPM and COPP semantic modes
- Microsoft: connected HDCP device information and COPP emulation
- Microsoft: OPM features compared with COPP
Looking for a different code? Search another status or error code.