Windows 10: Windows 10 KB4556799 causes BSOD and network issues

Windows 10 KB4556799 is causing a host of new problems for some configurations. In addition to audio issues, temporary user profile and FPS drops, Windows 10’s latest cumulative update is also causing Blue Screen of Death, crashes, and network issues for some users.

As often is the case with Windows 10 updates, users are facing a range of different issues, but not everyone is experiencing these bugs and update runs without causing any problems for most of the users.

Given the nature of Windows 10 and its diverse ecosystem, it’s not yet clear how widespread these reported bugs are.

“I am also having the explorer refresh bug and it gets to the point where anything explorer related (everything) lags really bad or just doesnt respond,” one user wrote in a thread on Reddit.

“Seeing this on a couple of 1909 devices now – triggered when opening File Explorer, ends with a shell crash and eventually explorer.exe prompting for a process end,” another user noted.



The other issues with Windows 10 cumulative update have been detailed on Microsoft’s forum, Reddit and social media. Many users have reported about Blue Screen of Death errors with different stop codes and a bug that causes a black screen.

Some have also reported issues with Windows 10 network adapters and Microsoft is investigating a bug where internet might not be available on PCs with some LTE modem:

“After installing this update on a Windows 10 device with a wireless wide area network (WWAN) LTE modem, reaching the internet might not be possible,” Microsoft said and promised to fix the issues in an upcoming release.

Users have also reported performance issues after installing Windows 10 KB4556799.

If your PC has slowed down or you have noticed any new bugs in May, the easiest way to fix your system is to revert to an older version of Windows 10.

To revert back to an older version of Windows 10, head to the Settings > Update and Security and select Windows Update on the left-hand side. Click on “View Update History” and select the first option “Uninstall update” and choose KB4556799n in Control Panel window.

Your system will restart for one or two times and Windows will remove the patch. To prevent the update from being reinstalled, download and run troubleshooter when the update shows up for download again.

The troubleshooter blocks this particular update only and you can still download or install May 2020 Update, which could be released between May 26 and May 28.

The post Windows 10 KB4556799 causes BSOD and network issues appeared first on Windows Latest

Weiterlesen...

 

KB4556799 issue and bugs

Had read that KB4556799 has issues and bugs.

Latest Windows 10 Updates Breaks Wireless LTE Connectivity
Windows 10 update is wrecking laptops — now Microsoft is investigating | Laptop Mag
Windows 10 Warning: Users Hit By Serious New Failure
Nasty Windows 10 update is crashing systems and hiding files: What to do | Tom's Guide

I avoided to install KB4556799.

Does anyone here can confirm the issues?

 

KB4556799 issue and bugs

I have installed KB4556799 on more than half a dozen machines, various makes and models, some x86, others x64. None have had any issues whatsoever.

Microsoft have also read the same reports that you have. They don't seem to be able to verify these reported issues. If anyone has such issues, then MS are asking them to provide feedback...

KB4556799 CU Win 10 v1903 build 18362.836 and v1909 build 18363.836

 

Random BSOD while browsing internet


BitDefender is nothing special. mwac.sys causes BSODs anywhere.
A tiny documentation can be found here: Solved Random BSODs - Windows 10 Forums
In that very thread, the suggested action apparently worked.

The storage and network filters of any third party antivirus can cause BSODs. Neither MBAM nor BitDefender is any special. For a regular antivirus, it may be shifted to an alternative; but MBAM has no alternative. So a clean install of the said program is the most feasible first step.
As far as the first step is not failing, it is better to not think for the second step. Because the BSODs are not universal, failure at the first step is not universal; and success at the second step is also not universal.
That is why I posted that my suggestion may work, or may not. Let us see where it goes.