Windows 11 keeps forcing Dolby Vision every time I start up, even though I turned it OFF

Anonymous
2025-06-05T17:36:51+00:00

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.

0 comments No comments

116 answers

Sort by: Oldest
  1. Anonymous
    2025-06-24T14:36:42+00:00

    This also did not work for me, the colours remained bugged till I toggled deep colour off and back on in my display's settings on my LG C2. Which works to fix it even on the latest update

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-06-25T02:12:05+00:00

    I had the same problem as everyone, and this fixed it for me

    https://powrusr.com/fix-the-dolby-vision-black-screen-issue-in-games-like-need-for-speed-heat/

    It was initially meant for another issue, but works with this thread's issue too.

    LG C2 + 5080.

    It removes the Dolby Vision profile from your drivers, as I understand. So it's okay to use if you don't care about it. I prefer that solution over the one recommended here, forcing to use a limited color range.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2025-06-25T08:46:52+00:00

    This ALSO, did not work for me, this was on the list of things I tried before toggling deep colour on the LG C2's menus fixed it, completely. No need to remove Dolby Vision from the EDID, no need to rollback updates, nothing.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-06-25T12:46:19+00:00

    Mine is doing the exact same thing; you're not the only one. I have an LG C2

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2025-06-25T15:35:51+00:00

    LG C2's and G2's seem to have a green/pink screen with dolby vision enabled in windows. If you want to keep Dolby Vision enabled with these displays, u/ZGremlin seems to have found a fix. Cannot test myself though. His fix:

    "System > Display > HDR > Enabled Dolby Vision for selected monitor

    Nvidia Control Panel > Change resolution > Use NVIDIA color settings > Output color format > Change to YCbCr420 > Apply

    The colors and display will be really off after the above step, press N on the keyboard to undo the changes. After I did this the colors look normal and dolby vision is still enabled."

    He confirmed it still worked properly after a restart.

    Was this answer helpful?

    0 comments No comments