Beware KB5058379 security update on Windows 10.

1NGIBITOR

Hi. Yesterday it was forcefully installed on my PC at work. Now it looks like either I find a way to get rid of it in domain controlled environment or I have to find a new job which preferably does not require looking at screens at all. My pc at work was good for working via RDP or with DVI connected monitor till this update (I used it for 5 years without issues). PC is built on Intel i5-10400 CPU @ 2.90GHz with build-in intel graphics win version 22h2 business. Update description contains the following: Graphics/WSL2: Case-sensitivity fix for GPU paravirtualization detection in WSL2. Some bug fix and my eyes say bye bye. What a luck. It's not completely intolerable like nvidia graphics but still looking at screen for more than 30 minutes makes an urge to stop irresistible.

JTL

1NGIBITOR Some bug fix and my eyes say bye bye. What a luck

In general, updates can certainly contain "undocumented changes" that wouldn't necessarily be listed in a changelog or description.

JTL

1NGIBITOR If this is the correct list of files changed in this update, it's MUCH larger than a mere WSL2 update. Over 54k files changed. Talk about a needle in a haystack.

simplex

If KB brings up new smoothing, can eyes be tolerant for it in 1-2 weeks? You use same monitor for 5 year, and nerve is adapted for "old" pixel dance of GPU + monitor FRC. Now, they react for new GPU dance. Yes it will strain you, but can you adapt again…?

In my theory, LED is issue. Pixel dance increase sensitivity for LED spectrums. Nerves adapted to old pixel dance so strong as we get eye-strain / brainfog etc

ocean10

simplex

I had something similar happen in May of last year with whatever Windows 10 update came out toward the end of May. Previously I had two Windows 10 computers that could use with no issues at all. Unfortunately never have been able to adapt. My eyes/brain seem to be a little more tolerant at this point but it's still bad.

AshX

simplex Now, they react for new GPU dance. Yes it will strain you, but can you adapt again…?

In my theory, LED is issue. Pixel dance increase sensitivity for LED spectrums. Nerves adapted to old pixel dance so strong as we get eye-strain / brainfog etc

Interesting theory. The question I have then is how to gradually test this without putting yourself in a world of pain 😂

1NGIBITOR

ocean10 Yes. I have never been able to adapt to any software related screen disturbances too. Be it game engine, OS video driver or display port / HDMI connection flicker. They are the worst. Even strobing pwm backlight on my worst android TV is tolerable to an extent. But win 10 with nvidia graphics plugged to a monitor via hdmi/display port that's a combo which literally destroys my eyes in minutes. No way to adapt to this. It also works for rdp connections. If I connect from system graphics of which my eyes tolerate well to a system with incompatible graphics it's still intolerable. But compressed video stream from screen casting can help. Looks like video compression suppresses flicker somehow.

simplex

AshX

I wish I could know 🙁 personally for me, issue is nerve adaptation.

I also found, anti-allergy pills, food glycerine decrease nerve sensitivity

1NGIBITOR

simplex I have always suspected that our problem was nerve-related. After all, every signal in the brain is an electrical current, and some of those signals can have harmful effects. For instance, people with epilepsy also cannot tolerate flicker, but the consequences are even more severe for them.

There are many drugs that reduce nerve sensitivity—mostly antidepressants—but they come at a price. One common side-effect is orthostatic hypotension: when the nerves react too slowly to tell the heart to speed up, the heart cannot pump blood to the brain quickly enough when you rise suddenly from bed. Reduced genital sensitivity is another unwanted effect.

1NGIBITOR

JTL

Yes. It's cumulative update after all. And very big one to boot. I see even basicDisplay and basicRender were reworked in the list of files.

But official changelog contains only 4 fixes.

[Graphics] Fix: The check for GPU paravirtualization was case-sensitive in Windows Subsystem for Linux 2 (WSL2). This issue might potentially cause GPU paravirtualization support to fail.
[OS Security] Updates to the Windows Kernel Vulnerable Driver Blocklist (DriverSiPolicy.p7b). Additions have been made to blocklist drivers with security vulnerabilities that have been used in Bring Your Own Vulnerable Driver (BYOVD) attacks.
[System Guard Runtime Monitor Broker service (Known issue)] Fixed: The Windows Event Viewer might display an error related to SgrmBroker.exe, on devices that have installed Windows updates released January 14, 2025, or later. This error can be found under Windows Logs > System as Event 7023, with text similar to ‘The System Guard Runtime Monitor Broker service terminated with the following error: %%3489660935’.
21H2 only - [Secure Boot Advanced Targeting (SBAT) and Linux Extensible Firmware Interface (EFI)] This update applies improvements to SBAT for the detection of Linux systems.

simplex

1NGIBITOR But compressed video stream from screen casting can help

For example, nvenc of nvidia stays before main grapfic pipeline ( lets name it "smoothing" stage )

Win10 also use DIGI / additional grapfic stage when you compress video with CPU, before " smoothing " stage.

Thats why captured or streamed video is okay

You can get " smoothed " output only in grapfic card port

RDP also have some configs, but it is not pure video compression. And I noticed it strain-free when I set 16-bit color depth

1NGIBITOR

simplex My rdp client was always in 16 bit color depth mode. But since this update it's not strain-free anymore.