I figured out how to do it manually within the monitor, with Custom RGB settings (please see below)

I'm doing ok with two monitors, and these two settings: 2400K and 3400K

For more details, please see my post titled: Flickering screen, again, with the latest version: f.lux (v4.118) . . . (08/04/20 I accidentally put this in the V3 forum)

Research suggests that f.lux must talk directly to display hardware to work – no remote desktops

I'm curious to see if you get good results also!

2400 K #ff9d3f Standard incandescent lamps . . . HP E272q
255,157,63
(255,157,63)
rgb(255,157,63)
rgb(100%,62%,25%)

3400 K #ffc184 HALOGEN . . . Per f.lux . . . HP 1755 . . . These settings work on the HP 1755, but aren't very orange on the HP E272q
255,193,132
(255,193,132)
rgb(255,193,132)
rgb(100%,76%,52%)

And a correction to my first post, in case anyone else reads this. The conflict only goes from 9:00PM to 9:02PM (not 9:20)

Andy

@herf With the recent update, my f.lux started to not work through to the monitors on my docking station. I followed your steps and it now works perfectly! Thank you!

Same issue but it goes deeper. Since Windows updated to 2004, f.lux has had a habit of switching itself off intermittently when I open notifications, the settings app, and other Windows accessories. When I start my laptop it's active, and within a few seconds it switches off and I can only turn it back on by clicking on my taskbar, and if I'm active for a long time, it'll sometimes switch off again. Night light mode is off and I use f.lux as my default blue light filter at 4000K during the day, so it's incredibly noticeable. MSI GP63 Leopard 8RD, Intel Core i7-8750H CPU @ 2.20GHz, NVIDIA GeForce 1050 Ti.

@pepesilvia said in Flux stopped working along with the newest Windows update:

Well, I just got another Windows update and that seems to have fixed the issue, thankfully.

Well, things have changed. Specifically back to not working. So that's weird. It worked last night. I haven't done anything with my settings, but I have reset.

@hNSaChJ4zbrct2qx said in Multiple concurrent instances running simultaneously:

@herf said in Multiple concurrent instances running simultaneously:

We do not allow multiple copies of f.lux to run.

If you have a lenovo vantage control panel, or windows night light, these can conflict with f.lux - more likely what is going on.

Hi, this has been occurring for me over the past few days.
The screen begins to flicker and when I look at my task bar there are between 2-8 f.lux icons, all active.
If I close all but one the issue goes away.

These seem to spawn at random, I will be using the computer and suddenly they'll appear.

Just happened again.

4e93edb9-c43a-4d6a-9168-e640c82d0936-image.png

Hi, this problem has resurfaced, at least for me, in version 4.118:

My zip code, which used to work, puts me in Wichita, KS. I am located in South Carolina! It doesn't seem to accept states, so if I try Anderson, SC, I get an Anderson apparently in New York! I am currently using Atlanta, which is 150 miles to the West, which might skew the dimming time a bit.

I have the same issue through the game Gwent. I'm on f.lux 4.118 and similar setup as OP.

Find the best app or software on internet which may help you in receiving the correct version of your computer back to screen.

I experienced the same issue. Alt+End doesn't help! What do I do?

I am having this issue as well, I tried the "turn off fast startup" per a prior thread I found and that did not solve either... If anyone finds an answer look forward to solving this.https://forum.justgetflux.com/topic/7043/fix-for-problems-with-the-windows-10-may-update-1903-18362

I tried turining off "fast startup" and still getting tinted while taking screenshot using lightshot. If anyone finds a fix please let me know.

 flux sunset.png