Voluminous reports of problems with this month’s Win10 Cumulative Update – but many appear random

Topic

New Reply

Yes, there are lots and lots (and lots) of reports of problems with this month’s Win10 version 1903 and 1909 cumulative update, KB 4549951. I’ll be ha
[See the full post at: Voluminous reports of problems with this month’s Win10 Cumulative Update – but many appear random]

2 users thanked author for this post.

rontpxz81, Elly

Reply | Quote

Replies

“Have you figured out the root cause(s)?”

Windows 10?

 

4 users thanked author for this post.

FakeNinja, ryegrass, T, jburk07

Reply | Quote

Haven’t had any problems from it on either of my two Win10H machines, thankfully.

Reply | Quote

Zero problems with 5 installations of Windows 10 Pro.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

rontpxz81, rexr

Reply | Quote

I haven’t hit any problems, either, nor have I talked with anyone who has – except the one poster who got bit by the temporary profile bug when upgrading from 1903 to 1909.

2 users thanked author for this post.

rontpxz81, rexr

Reply | Quote

We are having issues with it breaking printers that use v4 drivers, including Microsoft Print to PDF and Microsoft XPS Document Writer which QuickBooks Desktop relies on for creating PDF’s. It appears that uninstalling the latest update and then using Intuit’s QuickBooks Hub Tool to repair the PDF components fixes the issue for now.

2 users thanked author for this post.

Great Lake Bunyip, woody

Reply | Quote

Susan has reported these printer problems, on the Patchmanagement.org mailing list:

I have multiple credible reports of issues with v4 printer drivers.

I think it’s related to group policy deployment of them but heads up there is one issue that I’ve seen credibly reported.

https://twitter.com/squimjay/status/1253750574815690752

https://twitter.com/dbeato/status/1250946663562326017

2 users thanked author for this post.

rontpxz81, HiFlyer

Reply | Quote

Happened to me on just one of about a dozen PCs I updated. Thought it was just a HP driver issue but when it also affected native Print to PDF, I knew there was more to it. The HP printer was locally deployed (not GP) and uninstalling the update corrected both.

2 users thanked author for this post.

woody, rontpxz81

Reply | Quote

I am not adept at this stuff but since I did some update I am having a black flashing screen.

I have done the usual checked the monitor refresh and the graphics driver and the apps but still I get a black flash once in awhile…most infuriating!

Reply | Quote

Hmmmm. Looks like you installed one of the non-Security “Preview” CUs for 1909.
We usually recommend passing up the C/D week patches and sticking with just the Security CUs issued on Patch Tuesday.

1 user thanked author for this post.

woody

Reply | Quote

I read the Woody On Windows news article and the listed causes of blue screens. What does this remind me of? Intel’s initial yet faulty CPU microcode updates to mitigate Meltdown and Spectre. I also note that it seems that only Windows 10 computers are affected by this month’s updates? The DPC_Watchdog_Violation catches my attention since this may indicate memory corruption. Does anybody know if new CPU microcode mitigations from Intel were pushed out in this month’s Windows 10 update?

Reply | Quote

After installing KB4549949 on 1809 yesterday the dns just stopped working today.

Tried flushing dns, restarting modem, adding custom dns ips. I could still ping google dns and other ips, just resolve stopped working. Only reboot helped and now I installed KB4550969 also.

Maybe they broke something in KB4549949 with: – A denial of service vulnerability exists in Windows DNS when it fails to properly handle queries. An attacker who successfully exploited this vulnerability could cause the DNS service to become nonresponsive.
(CVE-2020-0993)

Before I had more than 20 days of uptime on march patches.

Reply | Quote

Did installing KB4550969 fix the DNS problem, or is it still there?

Reply | Quote

This just happened like a hour ago while browsing. The dns broke after about 30 hours from the update so heres to hoping it wont again, otherwise ill just try uninstalling I guess.

Reply | Quote

Also just before applying the first update I did change some reg keys for uk and us keyboard layouts so they stopped being added automatically.

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00000409 to 00000409-no

And installed RTL8156 Win10 Auto Installation Program 10.38 for 2.5gbe usb eth but its not used for internet or shared, just for connection to nas.

Hopefully kb layouts dont have anything to do with dns

 

Reply | Quote

USB ethernet adapter is a network device and is most likely to have caused the DNS problem.

What symptoms / errors are you seeing?

cheers, Paul

Reply | Quote

It happened again for a good 20-30min no dns functionality at all until reboot. Pinging google dns and isp dns ips works but everything else, clients, browsers that use dns dont work.

Usb eth digitus DN-3025 is used for local network to connect to nas. Been using it for a month before updating drivers. Bought one with a virtual drive for drivers, that was a mistake i think and one without for nas.

Internet is on a integrated intel 1219-v connected directly to modem and shared to another integrated intel I211 eth.

Uninstalled april patches KB4550969 and KB4549949 now to see what happens.

Reply | Quote

When DNS fails what messages do you get in the browser?

Try a manual lookup: in a Command Prompt type “nslookup nwtools.com”, without the quotes. What you you get in response?

cheers, Paul

Reply | Quote

It seems the cause was the realtek drivers somehow. DNS died 3 more times before I uninstalled them 2 days ago.

Nslookup would just timeout in 2s while same name server could be pinged. Cant post more here because of bot detection scrips.

1 user thanked author for this post.

woody

Reply | Quote

If you’re having trouble posting because Wordfence won’t let you – there’s a reason. We’ve been under very heavy attack lately. Wordfence is doing its job.

If you have something important to post but can’t get through, send me email: CustomerSupport@ AskWoody.com and be sure to include the Reply number (upper right corner) that you want to respond to.

Reply | Quote

No worries. Just a weird bug, nothing important, especially now that it seems to be resolved. Sent you a replay 3 days ago that I still couldnt post, but figured it cant be adjusted without spam coming through. Thanks.

Reply | Quote

Known issues in this update

Symptom

We have seen social media reports related to KB4549951 that mention Bluetooth, a stop error with a blue screen, and other related issues.

Workaround

To date, we have not seen these issues reflected in telemetry, support data, or customer feedback channels. We continuously investigate all customer feedback and are closely monitoring this situation.

Note If you experience any issues, we’d like to know. Please provide feedback using the keyboard shortcut Windows + F or go to the Start menu and select Feedback Hub so that we can investigate.

April 14, 2020—KB4549951 (OS Builds 18362.778 and 18363.778)

1 user thanked author for this post.

woody

Reply | Quote

[numike]

HA! I cannot even uninstall KB4551762 So I guess if its there its there to stay!

• This reply was modified 5 years, 1 month ago by numike.

1 user thanked author for this post.

woody

Reply | Quote

That’s the second March cumulative update for Win10 1903 and 1909.

Don’t worry about it. Chances are good you’ve already installed one of the subsequent Win10 1903/1909 patches.

Reply | Quote

The one having issue is there any 3. party VPN Client  installed? I have installed KB4549951 on 471 Windows 1909 machine no issue.

Reply | Quote

Hmmm! Updated yesterday. KB 4549951 didn’t appear when I used wushowide, so couldn’t be hidden, but did download and install regardless, as soon as I started updating. Haven’t had any problems yet, but I suppose it’s early days. Reinforces my deep doubts about the mess(es) Microsoft is imposing on users, without any effective comeback. Honestly, though I’m not a Pro but a Home user (why waste good money on this ‘product’?), it’s time we had a more focused and nuanced approach to this stuff. I speak as someone bitten by this scourge very early on.

Reply | Quote