F.lux No Longer Working After Updating To Windows 10 Pro Insider Preview Build 18305
-
This post is deleted! -
This post is deleted! -
Same here. Windows 10 Enterprise Insider Preview 18305. It was working in build 18298.
-
Yes this seems to be broken overall in 18305, not sure what is going on yet.
-
FWIW, Windows own Night Light functionality doesn't work in this build either.
-
Please report via the Feedback Hub
-
I just noticed this thread, after responding in another thread. Since this thread is more appropriate (the other one was started by a Windows 7 user), I'll copy my message here as well:
Sorry, I can't help. I just wanted to add that I'm also having the same problem, on Windwoes 10. In my case, automatic, as well as manual color change (Shift-Alt-PgUp/PgDown) and also manual brightness control (Alt-PgUp/PgDown) no longer work. When I try to use the shortcuts, the notifications (e.g. for % brightness) show up the same as before, but nothing actually happens. This all worked for as long as I can remember, until a few months ago. I stopped using f.lux for a few weeks before that and when I tried to run it again, it was no longer working.
The only thing that still works is Vignette Mode. It may also be worth pointing out that the Night Light function built into Windows 10 also fails to work the same way (i.e. I can turn it on/off, change the setting, etc. but nothing happens).
I recently cleaned out the display drivers from safe mode -- although, come to thing of it, I've also performed an upgrade repair install of Windows (Insider Edition) since then. Only thing I haven't tried yet (since I only just thought of it) is to try from a different user account.
NVIDIA 25.21.14.1735: NVIDIA GeForce GTX 1070 (20181211)
Intel Corporation 20.19.15.4549: Intel(R) HD Graphics 530 (20161110)1 monitors
Generic PnP Monitor
Dimensions: 382 x 215
Year: 2016
Chroma:
R=0.636719 0.347656
G=0.333984 0.627930
B=0.154297 0.049805
W=0.313477 0.329102
sRGB gamut: 77%, AdobeRGB gamut: 54% -
@herf "Feedback Hub" -- as in, the one provided by Microsoft?
If so, done.
-
Still an issue as of Build 18312...
-
temporary fix here:
https://justgetflux.com/flux-setup4-91.exeWe are waiting on MSFT for the real fix.
-
Hi,
just installed the 4.92 version, rebooted and it still does not work: Is there anything to do ? I did not find any option to activate the fix.
Regards
-
Also tried the version above (4.91) and same result, here are the details for my computer
NVIDIA 25.21.14.1771: NVIDIA GeForce GTX 1080 (20190111)
Generic PnP Monitor, 621 x 341mm, built 2017
Chromaticities:
R=0.632813 0.339844
G=0.310547 0.632813
B=0.158203 0.060547
W=0.313477 0.329102sRGB gamut: 91%, AdobeRGB gamut: 64%
Windows Build: 18317
-
Yes we apparently posted this at the same time as 18317 - so 4.93 fixes that one too.
We are being conservative and only targeting specific windows build numbers.
-
Hi,
thanks, just installed it but it still does not work as expected, it looks like the colors fades to grey but I still have the same luminosity, it does not look red-ish as before.
I have to adjust the backlight of my screen to avoid eyes damages.
I'm waiting the fix from Microsoft with impatience
Regards
-
Yes, this transform will make the reds a bit less saturated. It's not what we wish it would do.
-
I'm on 18317 and it's broken again (it worked for me on the previous build).
Other people on MS Feedback Hub also report the fix not working with f.lux 4.93
Is it possible the fix is not unlocked for some versioins of the 18317 build?
Thanks -
Just to be sure, I pushed 4.94 just now.
-
on 18317.1000 and 92 fixed the issue, 93 seemed to have broke f.lux again, but 94 appears to have fixed it once again.
-
4.94 works again, thank you!
-
I have to say that @herf, you're a busy programmer, to have time to create multiple fixes for different windows builds, add interesting additions to the "outdoors" section of fluxometer and live your life. I don't think I can manage my time this well.
