Windows 10 May update (1903)

Makaveli

after the new update, workkkkkkkk great!

rutra80

Ok so today problems came back and I think I know when - after full system restart everything is ok, but then when you have Fast Startup power option enabled and you shutdown and startup the system, things are borked again. So, it seems like something is wrong with kernel modules being woken up after hibernation, which is what happens when one has Fast Startup power option enabled (which is a default system setting) - only user mode and services get shutdown but the kernel gets hibernated.

herf

@rutra80 thank you thank you thank you. This is 100% right.

herf

I have posted an update at the top of this thread, with instructions for disabling fast startup if you want to:
https://forum.justgetflux.com/topic/7021/windows-10-may-update-1903

darksapex

@herf yeah, that's what I told you here https://forum.justgetflux.com/post/21601 maybe my english is so bad that I couldn't clarify the exact reason xD

I really hope you can fix this problem, I only have a HDD and the fast startup helps me.

herf

@darksapex yes this is what I get for never shutting down my computer. (Hopefully Microsoft will have a fix soon.)

Makaveli

ah shit.. the problem came back.. goddammmit Microsoft

hallow

hi, I am a long time user of f.lux and decided to register in this forum.
what I have found is that on fast startup enabled it is broken (dimming function). But you can simply fix this by signing out (user) and signing in again. No need to restart fully

Hi,

I use a laptop with 2 identical external displays. Ever since the 1903 Win10 update, my primary external monitor has been working fine with f.lux for dimming. My laptop display also has been working fine. However, my other external display does not respond to f.lux dimming.

I tried to disable fast boot, but that did not fix the problem. I am on beta version 4.105.

I have attached my driver info:

0_1560553742106_8194a4e7-9a3f-4046-9e4f-d6efa049ca41-image.png

Rajiv Varma

herf

@rajivvarma I would definitely look for a newer DisplayLink driver and possibly enable the gamma ramp registry feature.

locarno

@herf said in Windows 10 May update (1903):

@locarno tell me exactly what you mean by "turn off and turn on"? like a full system reboot?

@rutra80 already explained this.

@rutra80 said in Windows 10 May update (1903):

Ok so today problems came back and I think I know when - after full system restart everything is ok, but then when you have Fast Startup power option enabled and you shutdown and startup the system, things are borked again. So, it seems like something is wrong with kernel modules being woken up after hibernation, which is what happens when one has Fast Startup power option enabled (which is a default system setting) - only user mode and services get shutdown but the kernel gets hibernated.

herf

Yes we made a post about this here:
https://forum.justgetflux.com/topic/7043/fix-for-problems-with-the-windows-10-may-update-1903-18362/1

locarno

What is fallback mode in f.lux ?

I have f.lux 4.104. It is good version ?

When Microsoft fix kernel or something ? They even know about this problem ?

herf

MS seems to be working on it, yes.

f.lux uses the GPU in fallback mode, which is why screenshots are tinted. This code path was in there for DisplayLink monitors and it worked automatically for this Windows bug.

@herf Seems like my USB3.0 -> HDMI adapter might be the cause of my Win10 problems. I'm gonna try some different adapters from work and see if they make a difference. I also updated to the latest DisplayLink drivers, thanks for the recommendation.

Rajiv

jvaldiviezo

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

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

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

sRGB 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 enableGammaRamp to true using regedit.
--> https://www.displaylink.org/forum/showthread.php?p=82958#post82958

Rajiv

locarno

Microsoft fix this bug in KB4501375 update ?

herf

@locarno said in Windows 10 May update (1903):

KB4501375

Yes that's the one. It is 18362.207

gigel

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

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

sRGB gamut: 84%, AdobeRGB gamut: 59%

Windows Build: 18362.267