| Previous | Next |
| STATUS_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST | STATUS_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST |
STATUS_GRAPHICS_I2C_NOT_SUPPORTED
STATUS_GRAPHICS_I2C_NOT_SUPPORTED says that Windows cannot use an I2C bus for the selected monitor-control path. It should not be read as “the monitor has no adjustable settings.” DDC/CI and MCCS commonly use I2C, but a physical connection, adapter, or display implementation can make that bus unavailable to this API.
The Low-Level Monitor Configuration API operates on physical-monitor handles and VCP features. Before sending a VCP request, establish that the selected physical output and transport expose the expected DDC/CI route.
What to distinguish
- This is earlier than a VCP-not-supported result: there is no usable I2C control path to ask the monitor about a feature.
- Do not infer support from a different connector or a different operating system tool; identify the active physical output.
- For external utilities, a monitor can also expose a different control transport, but that is not evidence that this Windows I2C path is available.
References
- Microsoft: low-level monitor configuration
- VESA free DDC/CI and MCCS standards
- MS-ERREF: NTSTATUS values
Looking for a different code? Search another status or error code.