I do suggest you, and all people here use the Feedback Hub to make this issue loud and clear to microsoft, as it looks like the only place they hear us out .. sometimes.
Over-exposure in screenshots and recordings with HDR in Windows 11
Hello, I am inquiring about an issue I can't seem to solve (without turning HDR off all-together, which defeats the purpose of having it even be an option in Windows 11)
In recordings (primarily using OBS) and in screenshots (with snip and sketch) everything appears extremely over-exposed / bright with HDR enabled. This is a big problem for me as I actually, well, want to use the OS normally. I record lots of clips and take many screenshots and I've finally gotten fed up of it and am now looking for a solution. Any help appreciated, thanks
(snip and sketch has since stopped doing it, however it likes to do it randomly now. commonly happens in fullscreen programs and also my web browser for some reason)
Windows for home | Windows 11 | Display and graphics
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
259 answers
Sort by: Oldest
-
Anonymous
2023-12-15T17:13:05+00:00 -
Anonymous
2023-12-15T18:25:34+00:00 Microsoft is apparently getting ready for an update with HDR support/awareness. The DirectX 12 team put out a Tweet Nov 9 (also see here on yahoo! finance) saying that it is being released into the Windows Insiders in the Canary and Dev Channels. When that translates to a full public release is unknown at this time.
-
Anonymous
2023-12-18T15:59:14+00:00 This worked for me, I had the same issue and after seeing this I tried reducing "SDR Content Brightness" Slider to 35% and voila! it worked. The over exposure happens when you over expose the SDR content using that slider, Anything above 40 is a no go for Screenshots. Also this helped me to find the perfect balance between my SDR and HDR content 😍
-
Anonymous
2023-12-19T08:40:48+00:00 This was a great idea! It is being fixed in an updated version of the snipping tool.