@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.

I installed the beta yesterday on my fresh formatted notebook, let's see ^^ Thanks for the awesome work

@potato FIXED: I updated my Intel VGA Driver for Windows 10 and now it works perfectly. If you have lenovo and have the same problem try to go on the lenovo support page, select your model and then download the newest driver. Worked for me :)

I have a TN panel, and even with f.lux set to 2300K, or 1900K or even 1200K, I'm not seeing it. I mean sure, I see the gamma shift, but I'm not really seeing anything all that bad. My monitor is the AOC G2460PG. I have a GTX 780. I don't know if these parts make any difference.

Update: the current dev version of flux (3.11) fixes the flickering issue! Just in time too, since school is just started back up. So now I can use flux on my main monitor! Sadly there still isn't support for USB adapters, but maybe one day... Thank you flux team for fixing this issue. This change will have a huge positive impact on my sleep/health/academic quality.

Forgot to mention that the old laptop was attached to these same two monitors through the Dell docking station, and both monitors dimmed as expected with f.lux. Also, when connected to the dock, the laptop is generally closed, so the laptop monitor is turned off, and the Dell monitor (Monitor #1) is the main screen. Uninstalled and reinstalled f.lux, and expanded the color range again. Still doesn't work.

Hello guys, i come back with BIG News! I managed to fix this issue on my Lenovo y700. You have to go to Lenovo support page, select your device model and download the latest Intel HD VGA drivers. I had installed a version from 2015 and the latest was from 2016. Unpack the archive but do not run setup because it will fail. Now go to Device Manager, right-click on Intel HD and choose to upgrade drivers. Click: Browse My computer - Next - Let me pick from a list of device drivers on my computer - Click on Have Disk -> Browse and open the path where the drivers were unpacked (C:\drivers\Intel VGA Driver\Graphics) and select igdlh64.inf fro x64 OS or igdlh32.inf for X86 OS. After installation is completed reboot your computer once or twice. After the first reboot i had a problem with my desktop files missing but it might be due to other things i did to my system. If you encounter this issues just go to C:\windows\system32\config\systemprofile\ and create here a new folder called Desktop. Reboot and everything should be ok. PS: flux works great after this.

You may want to clear your browser cache and download again. Sounds like the download didn't finish.

Hi Bigfan, I have the Hue lights and use them with f.lux. I use a windows desktop too and I didn't have my speakers plugged in when I first synced the hub. I just imagined it was like syncing anything else - once you press the button you've got anywhere from 60 to 30 seconds to pair the other device. So once I checked the box and clicked done in f.lux, I rushed over to my hub and pressed the button. It worked, but every now and then f.lux will not take over the system. A workaround is to check the box and click done again whenever it doesn't and that usually fixes it until it stops working again. So maybe try that.

@kristoffer Hmm, new app? I can't comment on that as I recently wiped my phone in hopes of better battery life as the 5.0 update just destroyed it. Something about "mobile network" eating up all my battery. Going back to older versions has only brought back my ability to change the ringer volume on the lock screen by holding the power button. It also has a much easier (and intuitive) way to access emergency call. I'm on 4.4. Hue pro is a good app if you don't mind paying a bit for it. I like it but I'm sure you can find something very similar for free.

@sebadinator Reboot in safe mode - then you can uninstall f.lux. I'd love to know more about your video drivers.

@sebadinator We'll it's actually a big work around to find the problem of bsod... U can do a clean boot.. And stop Flux from starting at boot and then see if the Flux is causing.. It which I doubt... U can search Google for a clean boot and check if that's what's doing it... Or even safe mode would work better... If Flux is doing it... U should check ur video driver too... If it's updated or not.. If nothing helps... Make a backup and refresh ur pc 1st..if that doesn't help.. Then reset... It! Hope it helps! :D

@Tungsten_smooth said: @TwoCables O.K. that's cool. I knew you know hardware but wasn't sure where you are on the software side. Cool, now I know you're very good at both. Oh. I mistakenly assumed you had figured that out by now. Sorry about that.

@herf I changed my processor to an i7 6700k, intel HD 530 with driver version 20.19.15.4380. selected the 60m transition, but when turn on the pc at night f.lux do the transition in seconds and there is a lot of slowdown.