f.lux does require a restart (of f.lux only) when you change your profile.

We used to detect changes and update automatically, but there was a huge memory leak in Windows that made our detector expensive, so we stopped doing that.

Yes this is a core feature for us - it has been in the software since v3 (in 2013). Recent changes to Windows may have affected it, but most profiles with a VCGT tag work fine.

Can you post your f.lux options > driver info and email us the ICC profile?

Send to support at justgetflux.com

Hi,

No artifacts so far, thank you. However when I put my laptop to sleep at deep night (1900K) and wake it up another day, I need to restart f.lux. It shows 6500K, however 1900K temperature is still applied. Closing f.lux does not fix it, I need to run it again. Not a big deal though. 4.118

Updated to V4.118, still the same problem.
At nighttime Alt PgUp/PgDn dims or brightens. It's 11:05 PM now and the range is 2% to 60%. But it doesn't dim as much as earlier this year, and does not become red tinted when dimmed, just remains neutral.

Changed the pulldown to "recommended colors". It was on "custom colors" before, for some reason. Alt PgUp, PgDn now change between 0 and 14% but the brightness of the display does not actually change.

In Features and Notifications, backwards alarm clock is selected, use display data for color accuracy, use GPU for better quality. Use Windows internal color table is not selected.

Driver info is:
NVIDIA 26.21.14.4112: NVIDIA GeForce GT 635 (20191024)

Generic PnP Monitor, 597 x 336mm, built 2013
Chromaticities:
R=0.679688 0.309570
G=0.209961 0.700195
B=0.147461 0.053711
W=0.313477 0.329102
sRGB gamut: 102%, AdobeRGB gamut: 99%

Generic PnP Monitor, 521 x 293mm, built 2017
Chromaticities:
R=0.650391 0.333008
G=0.316406 0.612305
B=0.152344 0.067383
W=0.313477 0.329102
sRGB gamut: 96%, AdobeRGB gamut: 66%

Winlimit=0, 0
Monitor 1 on NVIDIA GeForce GT 635: VCGT=0 gamma=1
Monitor 2 on NVIDIA GeForce GT 635: VCGT=1 gamma=1

Windows Build: 19041.329

Um, the cancel button on the f.lux Options panel is greyed out and the Done button doesn't dismiss it! :)

Same visual response on the HDMI and VGA monitors, one is not different than the other.

Windows night light is off. No difference whether the strength is 0, 50, or 100, f.lux is still prevented from working.

Turn night light on, f.lux still has no effect whether the strength is 0, 50, or 100.

This issue is still active in flux version 4.118 (non-beta).

I am running flux on windows 10 home edition (x64 bit), version 2004, build 19041.329.
I can provide additional info if any is needed.

Note: I am experiencing the EXACT same problem as zsuraski.

@Betsy said in Flux Refuses to Appear as a Program Option:

I turned on my computer today and flux is gone, it wouldn't come up. I reinstalled, once it's done installing it disappears.
Any advice?

What do you mean? Do you mean that the window slides down and disappears? Do you mean that the icon in the Notification Area goes away?

If you’re referring to the window sliding down and disappearing, then that’s normal. If you’re referring to the icon disappearing, then check the hidden icons. To do that, click the button that looks like an upward pointing arrow.

I don't know of any reason it should be f.lux.

Things to check: your "DPI" (under "scale and layout") in Settings.
Logout and back in, sometimes it messes up after an update.

@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:
https://forum.justgetflux.com/topic/7507/windows-may-2020-update-2004/1

Now everything is working fine, thanks!

@herf said in Windows May 2020 (2004) Dimming no longer works:

Do you have an automatic brightness feature on your machine?

In 4.116, we are adding an advanced option to use the "internal" color controls - previously we were forcing it on, but we're trying to stop doing that. So you can see if that fixes it....but mainly I would like to find out what is conflicting instead.

I do not. It's a desktop machine so f.lux is my only brightness control.

Just updated to 4.116 and flipped that option on, which seems to have fixed it 👍

Version 4.115 reinstated the issue for me, so now I'm having the same problem again. :-(

Thank you - we will need to add a toggle for this - it didn't look that good when I tried it. :)