Problems after updating to Windows 10 May 2020 (version 2004)
After updating to the Windows 10 May 2020 (version 2004) I am experiencing some issues with f.lux.
This is the supposed color curve:
Steps 1 and 2 appear to work fine, but step 3 is never reached, the colors stay at step 2.
Also when I opened the Windows 10 Settings App (not in full screen) the colors would jump from step 2 to step 1, as if f.lux was disabled, and I only could bring it back by double-clicking on the color curve so it would simulate a 24 hour interval.
I am using f.lux version 4.111.
Also when I open programs in fullscreen f.lux is disabled (as it was configured to do), but when I remove a program from fullscreen, making is smaller, f.lux doesn't come back, I have to open it and trigger a 24 hour simulation so it would work again.
Intel Corporation 126.96.36.19959: Intel(R) HD Graphics 3000 (20160519)
NVIDIA 188.8.131.5214: NVIDIA GeForce GTX 1060 6GB (20200515)
Generic PnP Monitor, 410 x 257mm, built 2007
sRGB gamut: 99%, AdobeRGB gamut: 64%
Generic PnP Monitor, 160 x 90mm, built 2010
sRGB gamut: 100%, AdobeRGB gamut: 64%
Monitor 1 on NVIDIA GeForce GTX 1060 6GB: VCGT=0 gamma=1
Monitor 2 on NVIDIA GeForce GTX 1060 6GB: VCGT=0 gamma=1
Windows Build: 19041.264
Apparently Window 10 May 2020 Update (2004) introduced WDDM 2.7 (Windows Display Driver Model) and "should improve multi-monitor support" (you know, 2 steps forward, 1 step backwards... the more features you add, the more bugs comes along). So here are my suppositions on what might be going on:
1 - WDDM 2.7 breaks previous functionality intentionally and documented this.
2 - WDDM 2.7 breaks previous functionality intentionally and didn't document this.
3 - WDDM 2.7 breaks previous functionality unintentionally (a bug on Windows so not f.lux fault).
4 - Some internal component of Windows that manages multi-monitors wasn't upgraded properly to deal with WDDM 2.7. That would include the Windows Title rendering of windows (a bug on Windows so not f.lux fault).
I am not a Windows developer so I might be totally wrong on this, just following a feeling on what could be the root of this.
According to an article "WDDM 2.7 in Windows 10 version 2004 requires Nvidia drivers 450.12, Intel driver 184.108.40.20659 and above." But Nvidia is only servicing 446.14 for my GTX 1060 so this might be a corner case while the new drives don't go mainstream? Don't know, just another wild guess.
pratnala last edited by
@mfeinstein I checked the GeForce website with various graphics cards, and they all show 446.xx as the latest. I am on 1050 and I have 446.14 too. I guess we have to wait till 450.xx comes out.
We have issued two updates, and the most recent has a toggle (f.lux options) to use the "internal" setting.
Can you see if just updating helps, and if not, if toggling the setting helps?
@herf what do you mean by "use the "internal" setting"?
@herf I can't see any options saying anything about "internal" settings. I am using f.lux version 4.116.
Also I tried to simulate the 24hrs interval by clicking twice on the 24hrs graph and the problem I first reported persists, regions 2 and 3 of my first image have the same colors.
After a restart f.lux says it's on limited color mode and once I enable more colors and restart it works as it did before, thanks!
(I still can't see any toggles for internal settings though)
lamchcl last edited by
It will only appear if the feature is available at all - otherwise the checkbox would have no effect.
@lamchcl can't find this Tuning menu anywhere.
But so far things appear to be working just fine.
I can see it under "Options and Smart Lighting".
@herf I just got an update to version 4.117, but the What's New page apparently removed the v4.116, if it was a beta then it shouldn't be on the What's New page, and if it wasn't a beta than v4.116 shouldn't be removed, my 2 cents.
@mfeinstein thanks - yes all the notes since the previous version are there - but this readme is intended for normal releases.
We pulled all the May 2020 Windows people into the beta temporarily to get the bug fixes out, but that will be turned off as soon as it's stable. (i.e. as soon as possible)
Detailed notes are here: