Bypass MST first
Connect the monitor directly to the PC. If DDC/CI works direct, the MST hub or daisy-chain is likely the bottleneck.
DisplayPort MST fix
DDC/CI not working through DisplayPort MST
If brightness works with a direct cable but fails through an MST hub or daisy-chain, the chain may not be forwarding DDC/CI control commands.
Reduce the chain
Try one display at a time, disable daisy-chain mode, remove adapters, or lower refresh rate while testing.
Use fallback dimming
When MST cannot pass DDC/CI reliably, gamma dimming keeps a practical brightness slider available.
Confirm whether MST is the problem
Start by removing MST from the path. Connect the problem monitor directly to the PC with a single DisplayPort, HDMI, or USB-C display connection, then test brightness control again.
- If DDC/CI works directly but fails through the MST hub or daisy-chain, the chain is blocking the control channel.
- If DDC/CI still fails directly, check the monitor menu and make sure DDC/CI is enabled.
- If the first monitor in a daisy-chain has a DP Out or MST setting, disable it and test the monitor as a normal single display.
Why MST can break brightness control
DisplayPort MST lets one output feed multiple displays, but the hardware brightness path is more fragile than the video path. A hub or first monitor can pass the image while failing to forward DDC/CI messages reliably.
Hub forwarding
An MST hub may route video to every display, but only forward monitor-control traffic to some displays, or none at all.
Sleep and wake state
Some MST chains work after a fresh connection but become flaky after sleep, wake, monitor power changes, or HDR mode changes.
Fixes worth trying
- Move the display you adjust most often to a direct PC connection.
- Try one monitor at a time through the MST hub to find where DDC/CI stops working.
- Disable MST, DP Out, or daisy-chain mode in the first monitor's on-screen menu when possible.
- Update dock, hub, GPU, and monitor firmware if updates are available.
- Remove DP-to-HDMI adapters or extra hubs while testing.
- Lower refresh rate or disable HDR temporarily to see whether a simpler signal path restores control.
When the MST chain cannot pass DDC/CI
If the MST path never forwards DDC/CI reliably, hardware brightness will stay inconsistent through that chain. Use gamma dimming fallback for those displays so brightness control still works from Windows.
If you need true hardware backlight control, a direct connection for that monitor is usually the most reliable fix.
Frequently asked questions
Does DisplayPort MST support DDC/CI?
Sometimes, but it depends on the hub, monitor firmware, and chain layout. Many MST setups pass video while failing to forward the DDC/CI control channel reliably.
Will daisy-chaining always block brightness control?
No. Some monitors forward DDC/CI through a daisy-chain, but many setups are unreliable, especially after sleep, wake, HDR changes, or adapter changes.
What is the most reliable fix?
A direct cable from the PC to the monitor is the most reliable path for DDC/CI. If you must keep MST, use gamma dimming fallback for stable brightness control.
Keep brightness control when MST blocks DDC/CI.
Use hardware brightness where supported, with gamma fallback when needed.