This is an option right below the Hue setting called "Allow f.lux to keep this computer awake to adjust lights." You are welcome to turn it off, but it won't work as well.

Also, we do this only when the computer is plugged in (or has a nearly-full battery).

Hi Herf, thank you for explaining this! It sounds like for now the 'darkmode-ing' is still best done app-wise, imperfect as this is in Chrome and Office apps (and suboptimal as it is to have to switch to apps for which no dark mode exists altogether). It would be fantastic if at some point a more upstream, lower-level solution were available, perhaps once GPU makers, Windows devs and other devs have code that is more compatible with others.

@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

Thanks for the note. We did try in our beta to do this for "most" notifications but we wound up messing up the notification center pretty badly, so we stopped.

The interaction between "native" apps and the "modern" APIs is still a little difficult on Windows. For instance, we never had much luck handling notification clicks and other cases like that, especially if someone clicked a notifier after we updated.

We made the notifiers as they are to support Windows 7, and to handle the notifiers we make that animate over time (which isn't possible that I know of with the system). Then we wound up using them for everything due to the notification center problems.

Also we used every API we could to see if Windows is in "do not disturb" mode (presentation mode, fullscreen, etc.), and tried to suppress notifications -- there are like three different things we check there. I would assume that the "modern" side of Windows is not talking to the native side again there -- possibly even the "do not disturb" feature is quite new, since we shipped this version of f.lux.

Will look into it more.

@hounddogrock said in Windows 10 always starts with pop-up screen of f.lux.:

@twocables Great! That seems to have fixed it! Thanks a bunch!

You're welcome. The reason why it fixes it is, having f.lux in the Startup folder is identical to just double-clicking a shortcut to f.lux after Windows starts. That's how the Startup folder works.

When you install f.lux, it doesn't place a shortcut there because it creates an entry in the Registry for its startup because it uses a special command in the Registry called "NoShow" to keep the f.lux window from opening on Windows startup.

So, if it stops starting with Windows, then somehow that Registry entry was deleted. Usually, the only way to get it back is by reinstalling f.lux. Putting it in the Startup folder will only run the shortcut. To see what I mean, create a shortcut to f.lux and just double-click it. That's the same thing, only you're running the shortcut manually. The Startup folder runs shortcuts for you automatically, but it's not anywhere near the same thing as the way f.lux gets itself to start up with Windows without its window opening (that is, with the "NoShow" command in the Registry).

Thanks all. Installing the newest Nvidia driver also fixed it for me.