Windows 10 May update (1903)
-
This also happens with a External GPU using the latest Os build.
NVIDIA 26.21.14.3086: NVIDIA GeForce GTX 750 Ti (20190522)
Intel Corporation 20.19.15.4531: Intel(R) HD Graphics 4600 (20160929)BenQ BL2410, 477 x 268mm, built 2013
Chromaticities:
R=0.670898 0.313477
G=0.266602 0.636719
B=0.142578 0.080078
W=0.313477 0.329102sRGB gamut: 101%, AdobeRGB gamut: 78%
BenQ BL2410, 477 x 268mm, built 2013
Chromaticities:
R=0.670898 0.313477
G=0.266602 0.636719
B=0.142578 0.080078
W=0.313477 0.329102sRGB gamut: 101%, AdobeRGB gamut: 78%
BenQ BL2410, 477 x 268mm, built 2013
Chromaticities:
R=0.670898 0.313477
G=0.266602 0.636719
B=0.142578 0.080078
W=0.313477 0.329102sRGB gamut: 101%, AdobeRGB gamut: 78%
Windows Build: 18362.175
-
As a followup, the following made my DisplayLink external monitor work with f.lux again:
(1) Upgrade the DisplayLink drivers to the latest stable.
--> https://www.displaylink.com/downloads/windows(2) Set
enableGammaRamptotrueusing regedit.
--> https://www.displaylink.org/forum/showthread.php?p=82958#post82958Rajiv
-
Microsoft fix this bug in KB4501375 update ?
-
-
@herf said in Windows 10 May update (1903):
beta
my screenshots used to have that tint, and I used to get around by temporarily disabling f.lux before screenshot (Alt-End). But I stumbled upon this thread and I'm pleasantly surprised to find that now it works okay using latest beta!
Intel Corporation 22.20.16.4836: Intel(R) HD Graphics 530 (20171017)
LG IPSFULLHD(HDMI), 480 x 270mm, built 2014
Chromaticities:
R=0.644531 0.334961
G=0.304688 0.629883
B=0.148438 0.049805
W=0.313477 0.329102sRGB gamut: 100%, AdobeRGB gamut: 70%
Generic PnP Monitor, 309 x 173mm, built 2015
Chromaticities:
R=0.636719 0.338867
G=0.332031 0.619141
B=0.149414 0.039063
W=0.312500 0.328125sRGB gamut: 84%, AdobeRGB gamut: 59%
Windows Build: 18362.267
-
@gigel said in Windows 10 May update (1903):
@herf said in Windows 10 May update (1903):
beta
my screenshots used to have that tint, and I used to get around by temporarily disabling f.lux before screenshot (Alt-End). But I stumbled upon this thread and I'm pleasantly surprised to find that now it works okay using latest beta!
Intel Corporation 22.20.16.4836: Intel(R) HD Graphics 530 (20171017)
LG IPSFULLHD(HDMI), 480 x 270mm, built 2014
Chromaticities:
R=0.644531 0.334961
G=0.304688 0.629883
B=0.148438 0.049805
W=0.313477 0.329102sRGB gamut: 100%, AdobeRGB gamut: 70%
Generic PnP Monitor, 309 x 173mm, built 2015
Chromaticities:
R=0.636719 0.338867
G=0.332031 0.619141
B=0.149414 0.039063
W=0.312500 0.328125sRGB gamut: 84%, AdobeRGB gamut: 59%
Windows Build: 18362.267
update. it's broken again after a windows restart. 😡
-
@gigel thanks - it looks like your video driver may be older.
Some OEMs hold back the drivers which has been OK in the past, but recently there has been so much going on with Windows color that it is better to update. There are 2019 drivers here for the HD 530:
-
This post is deleted! -
Brand new pc, never had this issue on my win 7 machine. All my drivers appear to be up-to-date "the driver youre using is the newest available". Shame cause ive been sleeping terribly now. It works after a reboot until the pc goes to sleep and ive turned off fast startup (use and SSD) and usually leave on for a week at a time. so now im rebooting every day before supper when the sun goes down.
i test by manually changing the monitor colour via flux to candle light.really hoping this gets fixed by f.lux because MS wont fix anything.
-
@highwayrob We think the "fast startup" bug is fixed now (this is Windows update, not drivers). If you are having trouble, please post f.lux options > driver info in this thread (using the latest build of f.lux).
-
@herf said in Windows 10 May update (1903):
@highwayrob We think the "fast startup" bug is fixed now (this is Windows update, not drivers). If you are having trouble, please post f.lux options > driver info in this thread (using the latest build of f.lux).
thanks for the speedy reply, here's requested infoI think ill leave fast startup turned off anyways, as i leave pc running for a week preferably.( i realize windows caused the issue, but if a workaround cannot be found from flux, i mean then windows wont ever fix their bugs- rarely)
Advanced Micro Devices, Inc. 26.20.13001.25001: Radeon RX 580 Series (20190730)Generic PnP Monitor, 820 x 460mm, built 2010
Chromaticities:
R=0.632813 0.333008
G=0.205078 0.702148
B=0.150391 0.081055
W=0.291992 0.322266sRGB gamut: 100%, AdobeRGB gamut: 96%
Windows Build: 18362
-
@highwayrob got it - okay we do know that the Radeons are giving problems, and the 19.x driver series is the issue. For some people, downgrading to 18.x is working better.
-
@herf hmm, worth a shot, ill look into that this weekend. ty for the suggestion!
-
@herf said in Windows 10 May update (1903):
Radeons
https://www.amd.com/en/support
Dont see my RX 580 there, only "vega" series, and their tool only seems to want to install newest drivers. i cant roll back as these are the drivers the pc came with, so nothing to roll back to (pc is only a few weeks old).I sifted through their drivers and found nothing allowing specific version, or confirming that mine was version 19. (as hardware advises version 26.20.13001.25001)
do you know where i could get the suggested drivers? or do you have any other suggestions?note: when i came home form work the monitor was still in candle light ( i turn off my tv/monitor and dont have an screen saver), but when i moved my mouse full colour came back although f.lux setting said it was still set to candle light. will require a reboot to work again.
-
@highwayrob Sorry but your reply didnt make sense. I am not on version 20, i am version 26, there is not ability to downgrade to ver 18 as no version 18 is available for download.
DO you think you guys will fix this issue for Radeons or am I stuck rebooting every day or do i move to lightbulb, iris mini, redshift, sunset screen, shady, night tone, lumen, brilliance, iris, or one of the alternatives? shame windows stopped support for win 7 else i'd still be running that, as i had no issues with f.lux then. -
@highwayrob sorry we don't yet have the hardware here to test. We have confirmation that the 2018-era drivers do work, but it's possible that some of the 2019 ones do too.
Here is a list of "previous" drivers - are you able to try a couple and see?
-
@herf Thanks for the link, i dont know why i couldnt find these before. I installed the newest one at the top of that list. Rebooted my pc and worked (as reboot always fixes the issue) but i noticed my streamlabs wasn't working properly and i'd get black flashes where my game capture is supposed to go, they suggested, updating to the newest drivers. So I rolled back (forward in my case) drivers to what it previously had via my system restore ( as I dont know/coudlnt find the original drivers).
I don't particularly want to try each driver individually due to the amount of time, and the number of other programs that could go awry as streamlabs did). I think I'll hope you guys get the newest cards/drivers working - any idea on ETA for something like that? - i know you guys are prob busy with a thousand other drivers/bugs that are constantly rolling out/affecting the software as new updates for other 3rd party are created) -
@href @highwayrob Some good news for Radeon Vega owners, the issue seems to be fixed, at least for me, in the newest drivers "Adrenalin 2019 Edition 19.9.1" (release date 2019/09/10).
Details, per Flux:
Advanced Micro Devices, Inc. 26.20.13001.50005: AMD Radeon(TM) Vega 8 Graphics (20190903)
Windows Build: 18362
-
@xafeb23 thank you -adding to FAQ
-
This post is deleted!
