More bugses with the July Win10 version 1903 cumulative update

Topic

New Reply

Microsoft has officially acknowledged two bugs created by the May 29 “optional” Win10 version 1903 cumulative update, then sent out for general consum
[See the full post at: More bugses with the July Win10 version 1903 cumulative update]

2 users thanked author for this post.

abbodi86

Reply | Quote

Replies

Don’t have a whole lot of confidence in Microsoft when it cannot support its own devices properly. With all this Insider testing and telemetry collection, why isn’t it helping?

Reply | Quote

woody wrote:

How did the bugs make it through all of that fancy Win10 1903 beta testing?

All that fancy beta testing that could have taken place in five days after installing an optional preview update that you profess no one should touch with a barge-pole?

The RDP bug is for anyone connecting TO an updated 1903 computer (not enabled by default). How many ignorant gluttons amongst the unwashed masses would you expect to try that with outdated graphics drivers?

(I’m not sure what this has to do with KB4507453 on July 9. These bugs were in KB4497935 on May 29.)

Reply | Quote

The Group Policy workaround for the RDP black screen sounds simple and effective:

Use WDDM graphics display driver for Remote Desktop Connection = Disabled

(And gpedit should be available on any edition which can enable RDP host locally.)

Reply | Quote

Security Update will always carry bugs

Reply | Quote

I’m curious to know why Microsoft hasn’t acknowledged the 1903 + NVidia colour banding issue yet.

There’s a thread on NVidia’s forums about it:

https://forums.geforce.com/default/topic/1152704/geforce-drivers/visible-stripes-in-gradients-with-windows-10-update-1903-using-any-of-the-430-x-drivers/post/6109417/

Eizo, the manufacturer of high-end monitors, is advising customers to not upgrade to 1903 because of this issue, too.
https://www.eizoglobal.com/support/compatibility/software/problem_windows10_may_2019_update/index.html

Hard to tell at this point how widespread the problem is, but when a hardware manufacturer starts saying “Hey, don’t upgrade”, it’s time for Microsoft to say something.

Reply | Quote