Thanks, this resolved my issue. Oddly, that update seems to have been installed almost 2 weeks ago, but problem occurred only today.
Windows 11 keeps forcing Dolby Vision every time I start up, even though I turned it OFF
Hi all,
I have an LG OLED G4 connected to my PC (Windows 11, NVIDIA 4090 graphics card). In Windows settings I’ve turned off “Use Dolby Vision mode,” and on the TV I’ve also disabled the Dolby Vision option for that HDMI port. Despite that, every single time I power the TV and PC back on, Windows starts in Dolby Vision anyway.
The picture looks brown, dim, and washed-out until I manually go into Windows, turn the Dolby Vision toggle on and then off again. After that, it switches to the normal HDR mode I actually want (“HDR Game Optimizer” on the TV) and everything looks fine—until the next restart, when the whole problem repeats. If I turn the TV off and on again while the PC is still on, it says in HDR Game Optimizer; it's when I restart the PC and the TV that it reverts to Dolby Vision again. It'll even revert to Dolby Vision if I just restart the PC, leaving the TV on the entire time. I've also tried hard power-cycling the TV (unplugged for one minute) after getting all the settings the way I want) and the problem still occurs.
In short:
- Dolby Vision is OFF in Windows.
- Dolby Vision is OFF in the TV’s input settings.
- Yet Windows still chooses Dolby Vision at every cold boot or wake-up.
- Manually flicking the toggle fixes it temporarily, but the setting never sticks.
This started after a recent Windows and graphics-driver update. It’s making HDR on my PC basically unusable.
Please let me know how to stop Windows from forcing Dolby Vision at startup, or escalate this as a bug. I just want my system to stay in regular HDR when I’ve told it to.
Windows for home | Windows 11 | Devices and drivers
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.
116 answers
Sort by: Oldest
-
Anonymous
2025-06-10T20:33:50+00:00 -
Anonymous
2025-06-10T20:38:45+00:00 I have the same issue, after restarting my PC earlier I get the pinkish purple/green screen. I noticed when the video range is set to full it forces dolby vision which seems to be the issue. I switched to Limited and this got rid of the issue but with limited it crushes blacks. Ive always used Full and never had any issues. I always have dolby vision turned off as quite frankly, I think it's rubbish and it shows it just causes issues.
If this is due to a MS update then when will this be fixed?
-
Anonymous
2025-06-10T22:20:43+00:00 rtx 4090 with LG C4 same problem. Dolby Vision is off on tv and in windows 11 Home, however whenever I check my HDR in BO6 it says Dolby Vision HDR is on.
-
Anonymous
2025-06-11T01:47:18+00:00 Just started happening to me as well. Dolby Vision just started forcing on, and it is broken as well, making everything green, grey, and purple.
This happens whenever HDR is on and I open any window. HDR Games will still boot with normal working HDR. But opening anything else like a browser, settings, files, etc. will force on broken Dolby Vision. It will sometimes flicker between Dolby Vision and normal HDR as well. Toggling Dolby Vision on and off again will fix it, but a PC restart or sleep mode breaks it again.I am using an LG C2 TV, with an AMD GPU with the latest drivers. Though this started happening to me only a few days ago, so I assume the problem is a Windows update.
EDIT: I followed the suggestion to uninstall the update that causes the problem, KB5058499, and it solved the issue. And I turned off the option to get the latest updates as soon as they are available in hopes it won't automatically install itself again.
-
Anonymous
2025-06-11T07:07:54+00:00 Hi,
I also experience this issue and I see I have KB5058499 installed.
When opening Uninstall updates (under "Related settings"), I don't have an option to remove KB5058499, only other a few other updates are there that I can select.
Would appreciate help.Edit: In order to have the option to remove it, I had to first remove KB5060842...