No color changes under Windows Insider 19H1

  • F.lux starts as expected, but none of the expected color change is working in the latest Windows Insider builds.

    Driver info

    The information below is already on the clipboard. Paste to the f.lux forum or email us for help.

    MirrorOp MirrorOp Virtual Graphics Adaptor (20180619)
    Intel Corporation Intel(R) HD Graphics 630 (20181210)
    NVIDIA NVIDIA Quadro M1200 (20181101)

    Generic PnP Monitor, 346 x 194mm, built 2016
    R=0.639648 0.329102
    G=0.209961 0.709961
    B=0.149414 0.059570
    W=0.312500 0.328125

    sRGB gamut: 100%, AdobeRGB gamut: 100%

    Windows Build: 18312

  • Same here. Have let M$ know..

  • I am in the same boat.

    NVIDIA NVIDIA GeForce 940MX (20181211)
    Intel Corporation Intel(R) HD Graphics 520 (20171027)

    Generic PnP Monitor, 381 x 214mm, built 2015
    R=0.646484 0.337891
    G=0.316406 0.614258
    B=0.157227 0.043945
    W=0.313477 0.329102

    sRGB gamut: 87%, AdobeRGB gamut: 61%

    Windows Build: 18312

  • temporary fix here:

    We are waiting on MSFT for the real fix.

  • Thank you, that got f.lux working again!

  • Thank you, I've been at a loss without f.lux!

  • Interesting side-effect of using the beta (at least with 4.94) on 19H1 (at least with 18317) is that when you're making a screenshot (the program doesn't seem to matter, but Snipping Tool is handy), at the moment when you're selecting the part of the screen that you want to capture, the color temperature of the screen drops way down until the capture is complete. And the captured image takes on that hue! I've never seen that before, and it doesn't happen with f.lux disabled.

    NVIDIA NVIDIA GeForce GT 730 (20181102)

    Dell U2415(HDMI1), 518 x 324mm, built 2017
    R=0.660156 0.332031
    G=0.301758 0.613281
    B=0.150391 0.063477
    W=0.313477 0.329102

    sRGB gamut: 100%, AdobeRGB gamut: 69%

    Windows Build: 18317

  • That problem went away, but with 18323, I think we're back to the original problem, at least with 4.96.

    MS hinted at it in the release notes:
    "While night light functionality is back up and running, you may still find issues with other blue light reduction software not working."

  • We just pushed up compatibility bits for 18323.
    Restarting f.lux should keep the workaround going.

    Looking into what's new in this build.

  • @rseiler also yes this screenshot thing is expected - we are using the GPU for this mode (not ideal), but we're waiting for the normal windows color plumbing to stabilize before doing anything else. seems like they're making a lot of changes.

  • Hi All,

    using the 18323 and 4.96 version, it works perfectly except for brightness. I was using this feature a lot and now I have to set it manually by going into my screen's settings (Physical buttons).

    Any way to get it working soon ?


  • Looks like 18329 has done its thing, and it wasn't even because of a change relating to fixing the 3rd-party compatibility problem, since they haven't gotten to that yet.

  • ok, restart f.lux - I pushed our compatibility bits for that one too.

  • As if by magic, thanks.

    BTW, I think they broke Night Light again with this build, so everything is very much in flux right now.

  • Reporting in with 18334, same thing. Whenever you get a chance, thanks.

  • pushed - hope they fix it soon.

  • Only getting 4.66 through the Microsoft Store for some reason. Tried 4.91 and it isn't working. Only when I went to 4.96 did it work.

    NVIDIA NVIDIA GeForce GTX 980 Ti (20190130)

    LG HDR 4K(HDMI), 600 x 340mm, built 2018
    R=0.679688 0.315430
    G=0.280273 0.673828
    B=0.152344 0.049805
    W=0.312500 0.329102

    sRGB gamut: 100%, AdobeRGB gamut: 79%

    Windows Build: 18334

  • They're up to old tricks in 18836, the Skip Ahead jump build.

  • @rseiler thanks - included 18336. hope these workarounds are not delaying a "real" fix somehow!

  • @herf It might be just me, but after restarting it doesn't look like it had an effect.

    When I first saw the build #, I read it as 18336 and not 18836, which is what they made it for some reason. Is that possibly the reason?

  • try again

  • @herf Still no effect that I can see.

  • F.lux (and Night Light) stopped working on Insider build 18836.
    Hope you can push a workaround soon, my eyes are so used to always having F.lux in the evenings :)

  • Ok sorry I missed the note about 18836 not 18336. Pushed two blocks of exclusions just now, agh.

  • @herf Thanks! It's working.

  • Yes, all good again.

    Things should get really fun soon, since MS is going to continue pushing out 183xx builds while developing 188xx (two different sets of testers).

  • No real updates in current builds on the general issue beyond statements like:

    "While we’ve done some work to improve night light reliability in this build, we’re continuing to investigate issues in this space."

    Which I take to mean includes 3rd-party, as f.lux doesn't work in today's 18841.

    While I haven't tried the other two builds this week--18342 and 18343--they should be in the same boat.

  • @rseiler thanks again - have updated for these versions also.

  • Build 18343 not working with f.lux. My eyes are on fire 🔥_🔥

  • Works perfectly. Thx!
    I hope Microsoft fixes this soon D:

  • Third message about the brightness still not working and still no answer (little up this thread and here) ....

    Do you plan to fix it ? (details in the link below)


  • @clem0338 we are still in "workaround" mode since the color controls are not working. Hopefully some fixes soon.

  • @herf Soon, but not with today's 18845 and (likely) yesterday's 18346.

  • @rseiler okay I put 18845 under our compatibility just now.

  • Thankfully I found this thread - my F.lux wasn't working with build 18342 and my eyes were burning out staring at my BLUE screen after dark! I just manually closed F.lux and reopened it and it turned on (PHEW)! So glad to have it back. Hope it's fixed in a new build soon.


    Intel Corporation Intel(R) HD Graphics 630 (20190129)

    Generic PnP Monitor, 16 x 9mm, built 2016
    R=0.636719 0.330078
    G=0.272461 0.592773
    B=0.143555 0.066406
    W=0.276367 0.278320

    sRGB gamut: 91%, AdobeRGB gamut: 64%

    Windows Build: 18342

  • Does it make any sense that the workaround mode could possibly cause some black video blotching/tearing in some apps some of the time (Outlook seems to be the main one seeing this)? The black "blocks" randomly flash in a portion of the window and then disappear.

    It took me forever to realize that f.lux was doing it, since it's not a constant thing at all, though only since the workaround has been needed.

  • Well I am not aware that blacks should be affected by it.

    I know about some flashing like this in 1803/1809, due to the way the profiles are loaded/reset from Windows. Generally the bug we are working around in the shipping versions is that the system treats any device change (like a bluetooth headset or USB insert) as a "reset" to the color system, and so we have to race around trying to fix it. I don't know what is going on in this new version yet, but I am watching - guess we have another potential release later today.

  • @herf That's right, 18348 is out.

    Just to explain it a little better in case it matters, it's not that blacks are affected exactly, but black artifacts appear randomly over non-black areas. In this sense, you might say that it's whites being affected, or at least anything not black.

  • @rseiler Downloading, will see what's going on in a couple hours...

  • @rseiler pushed another compatibility update.

  • The problem MAY be fixed.

    I hadn't noticed that 18348 (Mar 1) had this in the release notes:

    "If you use third party apps to adjust the color of your screen, we’ve made a fix with this build to address feedback that certain apps were no longer working. We’re continuing to investigate feedback in this space."

    And today's 18850 has the same note.

    Did you find 18348 still needed the workaround? I'm about to try 18850, so I don't know about it yet, but it should be in the same boat as 18348/18351.

  • Updating our test machine now! 18348 did not work but I am hoping for a fix in the '50s somewhere. :)

  • 18850 doesn't work, either, so maybe they're working their way through third party apps (I'm not aware of any others, though they must exist).

  • 18851 is working. Looking at what is new there.

  • That's surprising, since the release notes for 18351 didn't mention anything about this other than the usual note that they're still looking at issues.

    But based on that trajectory (the build after when they said they fixed it actually does), I'd expect next week's 20H1 (post 18850) build to also have the fix.

  • Pushed 4.97 beta with full compatibility under 18351. Looks like everything is working a lot better now.

    The main (release) build will work also, but this one should be more efficient.

  • Flickering while using 4.97 with 18356 caused me to have to un install f.lux for the time being...

  • @breezewood can you share any details? When does it flicker? I am seeing lots of regressions in these insider builds.

  • Ok I think these things are fixed in the 4.99 beta.

Log in to reply