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.
    • M
      malganis
      last edited by

      Just wanted to chime in, after the Windows 18362 update I was having the tinted screen issue when using flux with the next driver info:

      Advanced Micro Devices, Inc. 24.20.12028.4004: AMD Radeon(TM) Vega 8 Mobile Graphics (20181102)
      
      Generic PnP Monitor, 527 x 296mm, built 2017
      Chromaticities: 
        R=0.653320 0.334961
        G=0.323242 0.611328
        B=0.153320 0.061523
        W=0.313477 0.329102
        sRGB gamut: 93%, AdobeRGB gamut: 65%
      
      Generic PnP Monitor, 309 x 173mm, built 2016
      Chromaticities: 
        R=0.589844 0.349609
        G=0.330078 0.554688
        B=0.153320 0.119141
        W=0.313477 0.329102
        sRGB gamut: 63%, AdobeRGB gamut: 40%
      
      Monitor 1 on AMD Radeon(TM) Vega 8 Mobile Graphics: VCGT=0 gamma=1
      Monitor 2 on AMD Radeon(TM) Vega 8 Mobile Graphics: VCGT=0 gamma=1
      
      Windows Build: 18362.418
      

      I've removed the OEM provided (Huawei laptop) AMD Radeon drivers and installed the 19.9.2 version and it's working as expected now.

      I hope this info is helpful for anyone in a similar situation.

      1 Reply Last reply Reply Quote 0
      • U
        User_V1 @herf
        last edited by

        @herf The issue persists even if I install a downgraded version of Readon Graphics (with the 19.7.5 version).
        0_1572267221197_driver settings_28_october_2019.PNG

        1 Reply Last reply Reply Quote 0
        • U
          User_V1
          last edited by

          After making some researches in this thread, I found the following advices given by @AbhiMahant :

          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 tried it on my laptop which has a AMD Rysen 5 2500 U graphics in order to see how it would work.
          On step "4." , I checked AMD website and install the driver that matches the setting of the processors (the processor can be found on Device Manager).
          And it seems that it solved the issue of flux "not changing the colours of the screen".
          I hope this will help others who have AMD Radeon Graphics.

          R 1 Reply Last reply Reply Quote 1
          • L
            locarno
            last edited by

            f.lux v3 on windows 10 also have this problem?

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

              @locarno most problems should be the same - v3 simply brute-forces some things that v4 tries to be more careful about (so your computer should run faster with v4)

              1 Reply Last reply Reply Quote 0
              • M
                mcgulic
                last edited by

                The latest AMD update (12/12) fixed the issue for me.

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

                  I have this issue since yesterday I installed 1903. I even installed all the latest updates, but I do have tinted screenshots:

                  NVIDIA 26.21.14.4166: NVIDIA GeForce GTX 1060 6GB (20191206)
                  
                  PnP-Monitor (Standard), 527 x 296mm, built 2017
                  Chromaticities: 
                    R=0.663086 0.327148
                    G=0.272461 0.627930
                    B=0.147461 0.051758
                    W=0.313477 0.329102
                    sRGB gamut: 100%, AdobeRGB gamut: 75%
                  
                  PnP-Monitor (Standard), 527 x 296mm, built 2017
                  Chromaticities: 
                    R=0.663086 0.327148
                    G=0.272461 0.627930
                    B=0.147461 0.051758
                    W=0.313477 0.329102
                    sRGB gamut: 100%, AdobeRGB gamut: 75%
                  
                  Winlimit=0, 0
                  Monitor 1 on NVIDIA GeForce GTX 1060 6GB: VCGT=0 gamma=0
                  Monitor 2 on NVIDIA GeForce GTX 1060 6GB: VCGT=0 gamma=0
                  
                  Windows Build: 18363.657
                  
                  1 Reply Last reply Reply Quote 0
                  • R
                    RectifiedCircle @User_V1
                    last edited by

                    @User_V1 Reinstalling via Windows solved my issue, thanks alot for the compilation, youre my hero of the day :3!

                    1 Reply Last reply Reply Quote 0
                    • C
                      CTS_AE
                      last edited by

                      Been having this problem ever since the ol windows update from a year or two ago.

                      • Windows: 19043.1586
                      • Flux: 4.120
                      • Sharex: 13.7

                      I kind of figured there was no fix given how long it's been. Then I regained hope today when I saw Window's screen snipping tool seems to get around it somehow 🤔

                      Still doesn't work with sharex or other screen snipping tools hrmmm.

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

                        @CTS_AE please post f.lux options > driver info here. Usually f.lux uses its "fallback" mode due to a lack of driver support, such as with a USB adapter.

                        1 Reply Last reply Reply Quote 0
                        • T
                          tyronjean
                          last edited by

                          I stumbled upon this thread and noticed that it's quite old. Nonetheless, I'll try to help out with your issue.
                          Have you tried updating your NVIDIA drivers to the latest version? That may solve the problem you're experiencing with the ""disable for fullscreen apps"" option. Additionally, you may want to check if there are any updates available for your monitor's drivers.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright © 2014 NodeBB Forums | Contributors