• 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.

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. 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.

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.

@chaoscreater said in FIX for problems with the Windows 10 May update (1903/18362):

I tried everything, reg fixes, reinstalling Flux, disabling fast startup, resetting color profiles under Color Management, making sure night light is off, reinstalling Intel graphics drivers, etc.

Turns out, it was the stupid Lenovo Vantage app on my laptop that was causing the issue. You guys might wanna verify there are no apps controlling the brightness/colour.

Well, looks like Lenovo and MS took my fix and posted it without giving me credit. I posted this on the 6th and Lenovo and MS posted the same fix on the 9th and 10th respectively. Oh well..

Anyway, this is slightly unrelated but might still help others. An alternative solution is to download Autohotkey, then create a .ahk script file and add the following into it and just run the script:

#+s::
{
Send !{End}
;Send #+S
Run, explorer.exe ms-screenclip:
;msgbox, test

;if WinActive("ahk_class Windows.UI.Core.CoreWindow")
;msgbox, test

sleep 4000
Send !{End}

}
return

Damn it, can't edit anymore. This is the updated script, use this instead. Thanks to @7empest from Autohotkey Discord for the help:

#+s::
wintitle := "Screen snipping ahk_class Windows.UI.Core.CoreWindow ahk_exe ShellExperienceHost.exe"
Send !{End}
Run, ms-screenclip:
WinWaitActive, % wintitle
While WinActive(winTitle)
sleep 10
;MsgBox, test
Send !{End}
return

I tried everything, reg fixes, reinstalling Flux, disabling fast startup, resetting color profiles under Color Management, making sure night light is off, reinstalling Intel graphics drivers, etc.

Turns out, it was the stupid Lenovo Vantage app on my laptop that was causing the issue. You guys might wanna verify there are no apps controlling the brightness/colour.

Well, looks like Lenovo and MS took my fix and posted it without giving me credit. I posted this on the 6th and Lenovo and MS posted the same fix on the 9th and 10th respectively. Oh well..

Anyway, this is slightly unrelated but might still help others. An alternative solution is to download Autohotkey, then create a .ahk script file and add the following into it and just run the script:

#+s::
{
Send !{End}
;Send #+S
Run, explorer.exe ms-screenclip:
;msgbox, test

;if WinActive("ahk_class Windows.UI.Core.CoreWindow")
;msgbox, test

sleep 4000
Send !{End}

}
return

Turn off Night Light on Windows 10 if you're using it.

The software stops running exactly 9pm. every day and has to be restarted to resume normal state.

And indeed I also have the Lenovo Vantage app which is part of the issue.
Disabling it fixes it, however is indeed painful for the eyes.

So, the question is, why did it only break now. I hope the lenovo and microsoft guys can figure this one out.

Turns out, it was the stupid Lenovo Vantage app on my laptop that was causing the issue. You guys might wanna verify there are no apps controlling the brightness/colour.