| Previous | Next |
| ERROR_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED | ERROR_GRAPHICS_I2C_NOT_SUPPORTED |
ERROR_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST
The protected-output command failed session validation
This result is the command-side counterpart of an invalid status request. IOPMVideoOutput::Configure authenticates the command parameters with OMAC and expects the next value in the command sequence. The command counter is independent from the status-request counter established during session initialization.
A key difference from status polling is failure handling: Microsoft documents that when Configure fails, the application must not advance the command sequence number. The next command should reuse the same command number after the cause has been corrected. Advancing it turns one rejected command into a persistent protocol desynchronization.
Useful checks
- Confirm that the command GUID, parameter size, and additional parameter buffer are the ones required for this specific OPM command.
- Calculate the OMAC only after sequence number and all command bytes are final.
- Maintain a separate retry path for commands and status requests; their counter rules are similar but not identical.
References
- Microsoft: OPM_CONFIGURE_PARAMETERS and command sequence rules
- Microsoft: sending OPM commands
- Microsoft: ERROR_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST
Looking for a different code? Search another status or error code.