Windows 10 April 2018 Update issues

  • Latest information

    June 3
    We are updating 17134 and later users to 4.73.

    v4.73: has a workaround that seems to fix the issue
    v4.72: tried to look for the problem and fix it as quickly as possible has the latest version, and we are posting new builds to the main page also.


    Windows 1803 (build 17134, the April 2018 update) has a bug that resets color adapter settings every time a driver is added to the system. Bluetooth headphones, network adapters, etc. all do this.

    Some people who have devices attach and re-attach frequently have been experiencing f.lux flashing or disabling unexpectedly.

  • Using 4.73 on Win10 1803 and still experience f.lux getting unresponsive after a while. It happens constantly. The only way to stop f.lux is by killing the job in task manager. But after a while, screen colours revert to standard and f.lux is again unresponsive.
    nVidia GeForce 650M and Intel HD 4000 (Optimus)
    Displaylink USB3 docking station with 2 FHD neovo displays
    8GB RAM

    Intel Corporation Intel(R) HD Graphics 4000 (20171211)
    DisplayLink 8.5.3459.0: DisplayLink USB Device (20180511)
    DisplayLink 8.5.3459.0: DisplayLink USB Device (20180511)
    NVIDIA NVIDIA GeForce GT 650M (20160215)

    Standard PnP-skærm, 344 x 194mm, built 2011
    R=0.613281 0.361328
    G=0.307617 0.602539
    B=0.155273 0.103516
    W=0.313477 0.329102

    sRGB gamut: 78%, AdobeRGB gamut: 53%

    Standard PnP-skærm, 531 x 299mm, built 2016
    R=0.629883 0.349609
    G=0.339844 0.634766
    B=0.150391 0.049805
    W=0.313477 0.329102

    sRGB gamut: 76%, AdobeRGB gamut: 54%

    Standard PnP-skærm, 531 x 299mm, built 2016
    R=0.629883 0.349609
    G=0.339844 0.634766
    B=0.150391 0.049805
    W=0.313477 0.329102

    sRGB gamut: 76%, AdobeRGB gamut: 54%

    Windows Build: 17134

  • It is possible that the NVIDIA driver has an available update.

    Also, do you happen to know if the same issue occurs with the Displaylink monitors unplugged?

  • It's the latest nVidia-driver.
    I'll try running it without Displaylink dock and return.

  • Same here.
    Win 10 1803 and 4.73

    Lenovo 510s.
    Intel HD Graphics 620

    The constant flashing seems to occur more after unplugging 2nd monitor.

  • @rtbbj can you post your driver information too? This is presumably with Displaylink (USB) adapter?

  • I've now run without Displaylink dock for 40 min and still no crash. It does look like a problem with Displaylink. A little weird as Displaylink is recommending using f.lux instead of standard Windows (

  • I am not seeing any new bugs due to Displaylink when testing, so maybe it isn't that.

    Our crash logs are very good for this version (maybe some are not getting through) - but there is one for the notifiers. Do you have any apps disabled/etc. that would show a notifier?

  • I don't understand. Which notifiers?

  • I believe I am having a similar problem to @hba66 and @RtBBJ . Flux v4 randomly freezes and becomes unresponsive after 20-40 minutes of use.

    I posted it about in a separate topic ( Driver Info output is located there as well.

    I had no issues with the same setup for Flux v3 - issues started immediately after upgrading to v4.

  • 4.74 seems to have fixed the problem with crashes when connected to Displaylink. Great! Thanks!

  • When the most recent update came out, I have Windows 10, I have a strobe effect thing happening just as the evening change happens.

  • @deanawat I am also having the same issue. I am using Windows 10 on a laptop with nothing else plugged in except a mouse. I do most of my computer time at night when the filter is most needed. I don't want to have to disable it but the strobe effect is making me sick.

  • Okay this is likely due to Windows Night Light.

    We pushed 4.75 which might fix it:

  • @herf I can confirm that the issues that @deanawat and @danaandpete were facing are actually resolved in the latest update that 4.75 Thanks team!

  • Windows 10 1803 has been available to download since April and has been pushed out by Microsoft since May.

    Speedy adoption could be a sign the update is being welcomed by Windows 10 users, which might be true if it weren't for all the problems they have been facing.

  • I'm not able to install version 4. I'm getting a "Windows cannot access the specified device, path, or file" message. I've tried both the "flux-setup.exe" and the "flux-setup4.exe".

    I've also tried the version 3 install and it worked (from the same download location on my PC.)

    Any suggestions?

  • @baritonejp Do you have antivirus?

  • @herf Yes, I do.
    Remember that version 3 installed without any issues.

  • @baritonejp yes, many programs are whitelisted by AV companies by hand (especially old ones), so anytime we ship a new version, there is a risk that it is accidentally flagged.

    Could you could post information about which AV you have, and if f.lux installs properly when it is disabled?

  • @haanuman rel 4.76 still strobing.

  • I am also experiencing strobing with the latest nVidia drivers on both Windows 10 (build 17672) and Windows 8.1.

    Both PCs use a GTX 970 display adapter.

  • Just wanted to mention I am also seeing the strobe affect on 4.76 . Not quite sure what triggers it. It might be happening when a color change occurs?
    I usually go to the icon and settings and just toy with things a bit and eventually something I do (or maybe randomly) stops it?
    I have a GTX 1060 video card with driver version 391.35 .
    I just went and turned off the DCI or whatever it was I saw mentioned elsewhere (in my monitor settings). monitor is HP Omen 32" 2560x1440.
    Hope that helps....

  • Continue to see the strobe as well. Very frustrating, especially since I donated money to flux. Hope this gets fixed soon so I don't have to continue to disable it.

Log in to reply