f.lux f.lux forum
    • Recent
    • Popular
    • Register
    • Login

    FIX for problems with the Windows 10 May update (1903/18362)

    Windows v4
    39
    71
    31.5k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      AbhiMahant @AbhiMahant
      last edited by

      @abhimahant Here's what's worked for me after all this trying.

      1. Uninstalled the drives.
      2. Uninstalled display monitor from device manager.
      3. Restart graphics driver using custom resolution utility.
      4. Finally installed drivers again but with windows not amd.
      5. Although the version of my drivers is old now. But i will update my drivers and see what happens.
        I cant confirm if 2nd step is important or not, your wish I guess.
      1 Reply Last reply Reply Quote 0
      • B
        booms1
        last edited by

        Thank you so much for the information you have provided.I do admire the effort and consider this as a great help.

        1 Reply Last reply Reply Quote 0
        • J
          jh211707
          last edited by

          Help! I've read through both of the threads regarding errors with the recent updates. This program has helped so much with my migraines - I Need it!
          I have uninstalled and reinstalled f.lux after each attempt. I have uninstalled and reinstalled my display adapters. I have disabled fast start up. Tried adjusting display properties.
          Here's my driver info:

          Advanced Micro Devices, Inc. 15.201.1151.1008: AMD Radeon HD 5450 (20151104)
          Intel Corporation 10.18.10.4358: Intel(R) HD Graphics (20151221)

          AOC e2252V , 477 x 268mm, built 2013
          Chromaticities:
          R=0.647461 0.333984
          G=0.284180 0.607422
          B=0.151367 0.071289
          W=0.312500 0.329102

          sRGB gamut: 100%, AdobeRGB gamut: 69%

          Windows Build: 18362

          herfH 1 Reply Last reply Reply Quote 0
          • herfH
            herf @jh211707
            last edited by

            @jh211707 these are older drivers - are you able to try updating them?

            R J 2 Replies Last reply Reply Quote 0
            • G
              gnza100
              last edited by

              I have the same problem since updating my CPU to a Ryzen 3 3200g, also updating from windoiw 7 to 10, I hope a solution is found

              Advanced Micro Devices, Inc. 26.20.13001.25001: AMD Radeon (TM) Vega 8 Graphics (20190730)

              Generic PnP Monitor, 410 x 230mm, built 2009
              Chromaticities:
                 R = 0.648438 0.338867
                 G = 0.291992 0.602539
                 B = 0.142578 0.070313
                 W = 0.313477 0.329102

              sRGB gamut: 93%, AdobeRGB gamut: 63%

              Windows Build: 18362

              1 Reply Last reply Reply Quote 0
              • R
                rorix @herf
                last edited by rorix

                @herf I've been using the latest Adrenalin 19.7.5 beta drivers from July 30 to no avail. There are no newer drivers than that.

                Advanced Micro Devices, Inc. 26.20.13001.25001: AMD Radeon(TM) Vega 8 Graphics (20190730)

                HP 23xi IPS LED Backlit Monitor, 509 x 286mm, built 2014
                Chromaticities:
                R=0.635742 0.333984
                G=0.308594 0.623047
                B=0.150391 0.067383
                W=0.313477 0.329102

                sRGB gamut: 100%, AdobeRGB gamut: 69%

                Windows Build: 18362

                1 Reply Last reply Reply Quote 0
                • J
                  jh211707 @herf
                  last edited by

                  @herf In checking for updates, there are none. Updating is what caused my issue. If there is another way to do this, I don't know how other than to manually do it in the Device Manager, but I am new to this. What [drivers] do I need to choose to force an update?

                  J 1 Reply Last reply Reply Quote 0
                  • J
                    jh211707 @jh211707
                    last edited by

                    @herf I attempted to manually update both display adapters, but both said they had the newest update available. Same with my monitors.

                    1 Reply Last reply Reply Quote 0
                    • J
                      jh211707
                      last edited by

                      UPDATE: The newest windows update has a bug that disables f.lux and all programs like it, including the windows built in Night Light. I recovered to a previous version to wait it out until the bug is fixed.

                      herfH 1 Reply Last reply Reply Quote 0
                      • herfH
                        herf @jh211707
                        last edited by

                        @jh211707 we think this problem was fixed in 18362.207 and later, so the remaining issues are due to graphics drivers.

                        1 Reply Last reply Reply Quote 0
                        • R
                          rorix
                          last edited by

                          The issues with the Vega 8 persist on 18362.267

                          1 Reply Last reply Reply Quote 0
                          • D
                            dallersuk
                            last edited by herf

                            Hello

                            We are having the exact same problem.

                            We have been using F.Lux fine and testing this with a view to purchasing licencing for our organisation. We have a lot of users that would benefit from this using multiple screens. We use a multitude of different devices, graphics cards and drivers. I can tell you clearly that none of them matter as this has stopped working for all users since we patched to 1903. We have troubleshooted extensively so it is either Windows that has disabled it or something needs updating in your code and patching.

                            Its disappointing that we have had to stop testing this and maybe hold off purchasing licences for our users because of this bug. Please could you investigate and fix it.

                            Christopher

                            We are all running Windows 10 1903 Build: 18362.267.

                            1 Reply Last reply Reply Quote 0
                            • S
                              saiabinesh
                              last edited by

                              Not working for me as well. Since I updated the OS today. Going to try updating my drivers for NVIDIA.
                              0_1565462066108_8541a23e-0ab6-4ea5-82d5-3942f9dddcc9-image.png

                              1 Reply Last reply Reply Quote 0
                              • A
                                agarcia
                                last edited by agarcia

                                I've tried everything suggested with no luck. Flux only seems to work on my laptop screen but not on either of my external monitors.

                                0_1565796312284_Capture.PNG

                                1 Reply Last reply Reply Quote 0
                                • herfH
                                  herf
                                  last edited by

                                  Our 4.106 beta should partially fix older DisplayLink adapters that were not changing at all.

                                  P 1 Reply Last reply Reply Quote 0
                                  • P
                                    phantom @herf
                                    last edited by

                                    This post is deleted!
                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      AbhiMahant
                                      last edited by AbhiMahant

                                      It finally works good for me after all this time(with latest update)
                                      First i did windows update and then i installed latest drivers from amd
                                      I have acer nitro 5 ryzen laptop btw.

                                      1 Reply Last reply Reply Quote 0
                                      • P
                                        Peggy Rose @herf
                                        last edited by

                                        @herf After the May Windows 10 update my flux would not work. I am not particularly computer savvy but I tried a few of the recommended fixes. I finally gave up and began to wear my computer glasses again. Yesterday I got a notification that updates were available. I have an option to wait until I shut down for the day. Sure enough when I went to shut down I got the choice to update and restart later. Low and behold I booted up my computer at 4 am (couldn't sleep) and my flux was working. It had to be the update that fixed it. It went into see what the update was and here it is. It was Update for Microsoft Windows KB4512508. Hope this helps some people.

                                        1 Reply Last reply Reply Quote 0
                                        • herfH
                                          herf
                                          last edited by

                                          4.107 rolling out now to beta - is a bit more careful with multiple monitor setups, should fix most cases.

                                          P 1 Reply Last reply Reply Quote 0
                                          • P
                                            phantom @herf
                                            last edited by

                                            @herf The 4.107 beta broke it again for me :( Just like before, instead of red tint I get grayscale. I thought that maybe the latest driver from AMD may fix it. But instead atikmdag.sys was causing blue screens on login screen all the time and I ended up rolling back to previous driver in safe mode.

                                            How can I go back to 4.106 which works fine for me?

                                            herfH 2 Replies Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright © 2014 NodeBB Forums | Contributors