Windows 11 26H2 intermittently detects incorrect HDR peak brightness after startup
Operating System: Windows 11 26H2 (upgraded from Windows 11 23H2)
GPU: NVIDIA GeForce RTX 5080 (KFA2)
CPU: AMD Ryzen 7 9800X3D
Monitor: MSI MAG 321UP QD-OLED X24, 4K 240Hz
Monitor Firmware: FW.012
Connection: DisplayPort 1.4a with DSC enabled
NVIDIA Driver: 621.24 WHQL
Problem
Windows 11 intermittently reports an incorrect HDR peak brightness after system startup.
My monitor supports approximately 1000 nits peak HDR brightness. Under normal conditions, Windows Advanced Display reports approximately 1038 nits. However, after some system startups, Windows reports only 240 nits.
This is not merely a cosmetic reporting issue. Auto HDR and games actually behave according to the incorrectly detected 240-nit limit. When Windows reports approximately 1038 nits, HDR rendering behaves normally.
Reproduction and workaround
After Windows starts and HDR is enabled, Advanced Display sometimes reports only 240 nits.
The correct value can be restored by:
- Turning the monitor off and on using its physical power button.
- Switching the monitor’s HDR mode through its OSD and then returning to HDR 1000.
After reinitialization, Windows correctly reports approximately 1038 nits in HDR 1000 mode and approximately 530 nits in True Black 500 mode.
Simply opening Advanced Display settings does not resolve the issue.
Important diagnostic findings
- The monitor’s OSD correctly displays its selected HDR mode even when Windows reports 240 nits.
- No custom Windows HDR Calibration profiles are installed or used.
- The factory MSI ICC profile does not contain an MHC2 HDR metadata tag.
- An EDID capture taken while Windows reported 240 nits contained a CTA-861 HDR Static Metadata block with a maximum luminance value of approximately 1037.5 nits.
- Restarting the graphics driver with Win + Ctrl + Shift + B does not resolve the issue.
- A clean NVIDIA driver installation using DDU did not resolve it.
- Testing another GPU DisplayPort output with the same cable did not resolve it.
Suspected Windows issue
I suspect that Windows 11 may intermittently fail to correctly initialize, retrieve, or apply the monitor’s HDR capabilities during startup.
The monitor appears to provide correct HDR metadata, but Windows sometimes uses an incorrect peak brightness value until the monitor is reinitialized.
This may be related to Windows Advanced Color, HDR capability detection, EDID/DisplayID handling, or DisplayPort hot-plug detection (HPD).
The issue is particularly concerning because it persists without any custom HDR calibration profiles.
Request
Could the Windows display/HDR engineering team investigate a possible regression or initialization issue in Windows 11 26H2?
In particular:
- Why does Windows sometimes report 240 nits when the monitor’s EDID contains approximately 1037.5 nits?
- Why does reinitializing the monitor through its OSD or power button restore the correct HDR peak brightness?
- Could this be related to Advanced Color initialization or EDID/DisplayID processing after startup?
- Is there a known issue affecting HDR capability detection in Windows 11 24H2, 25H2, or 26H2?
Thank you.