FIX for problems with the Windows 10 May update (1903/18362)
-
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.329102sRGB gamut: 93%, AdobeRGB gamut: 63%
Windows Build: 18362
-
@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.329102sRGB gamut: 100%, AdobeRGB gamut: 69%
Windows Build: 18362
-
@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?
-
@herf I attempted to manually update both display adapters, but both said they had the newest update available. Same with my monitors.
-
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.
-
@jh211707 we think this problem was fixed in 18362.207 and later, so the remaining issues are due to graphics drivers.
-
The issues with the Vega 8 persist on 18362.267
-
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.
-
Not working for me as well. Since I updated the OS today. Going to try updating my drivers for NVIDIA.
-
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.
-
Our 4.106 beta should partially fix older DisplayLink adapters that were not changing at all.
-
This post is deleted! -
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. -
@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.
-
4.107 rolling out now to beta - is a bit more careful with multiple monitor setups, should fix most cases.
-
@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?
-
@phantom do you have two monitors on the same GPU? This is a bug we are working around in Windows right now. Does it work if you disable one?
-
@phantom can you also check if your GPU is running in 8-bit or 10-bit mode on the desktop? https://www.amd.com/en/support/kb/faq/dh-008
-
@herf Yes, I'm using two monitors. I disabled them but nothing changes on either monitor. Both monitors are running in 8-bit mode.
I've reinstalled flux and I'm back to 4.104 and can't update to beta version, even though the option in about menu is checked. I tried to check and uncheck the option, and to turn flux on/off multiple times but it doesn't seem to work this time. -
@phantom I found a note online that older drivers are working, like
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-18-10-2
