@pietroi thanks - I have a UHD 620 on the exact same driver version and windows build (with no failures of course). Presumably the driver is failing shortly after wake and then working some time later.

Thanks for the quick support.

Update: Had a planned reinstall of Windows today, so waited for that instead. Monitors are without driver/profile now. It seems Flux behaves as normal again.

@ralvydc Just tested Gradual Transition and it appears to start the Transition 1 hour before the target time. So if my Bedtime is 9pm (9 hours before my WakeUp time of 6am), with Gradual Transitions set, f.lux starts decreasing blue light at about 8pm, taking 1 hour to get to my Bedtime setting. Perfect.

They're just monitor drivers. Being "old" is fine. If you don't like the drivers, then you can uninstall them, but I guarantee you that they won't do any harm because they can't. They're specifically designed for these monitors, and you'll get the results you want. F.lux gets the name from the drivers. Check Device Manager. Go to the Display settings in Windows. You'll see "Generic PnP Monitor" there too - until you install these drivers.

Thank you! It does reappear in Process Monitor when clicking the disable option.

There were updates performed yesterday and it seems to be working now. Thank you.

f.lux tries to load your default color profile, and this is not usually something that we disable. To see which one is installed: Start Menu > "Color Management" -> see if there is a profile there.

Ohh, yep, same problem!

I found f.lux Location search didn't work well, so I resorted to typing in my city name and that worked fine. However, I'm on a Mac.

We ask the system about the installed profile for each display and try to use the profile correctly. So in our tests here, with a Thunderbolt display (standard gamut) and a Macbook (wide gamut) the two look identical, because we use different transforms for each display. Is it possible that the external display is actually wide gamut, but macOS does not know about this? If this were true you may see other apps displaying colors that were extra saturated, and the fix would be to install a good ICC profile for the external display.

I have the same problem. I found that if I toggle the windows notification sidebar open and close it again, or minimize a browser window and maximize again, flux starts working. I have flux set to disable on fullscreen apps, and I think it's reading the screen turn off as a full screen app for some reason. Going to test by turning off disable for full screen apps and see if the issue still occurs.

Which system process do you mean? I have not heard of this. If you have an incompatible video card, f.lux does a GPU fallback which may have some impact, but I have never seen it use CPU like this.