Patch Tuesday security patch causes blue screen errors and slows down Windows 10

In mid-August, Microsoft released Patch Tuesday monthly security patch for Windows 10 to fix two zero-day vulnerabilities and 120 other vulnerabilities. However, after fixing the security holes, this update causes other problems for some users.

Specifically, on the Microsoft support forum recently appeared a series of user complaints about Patch Tuesday, code-named KB4566782 . Accordingly, after the update, users experience crashes, slow processing or even annoying blue screen errors.

Patch Tuesday security patch causes blue screen errors and slows down Windows 10 Picture 1 Patch Tuesday security patch causes Windows 10 blue screen error

"Both versions 19041.450 and 19041.423 cause annoying problems for my Thinkpad X390 when I install Hyper-V. The camera stops working when Windows Hello is activated and the blue screen of death appears every time the machine switches. goes to sleep mode or when the Lenovo Vantage application is opened , " reports one user.

"I just installed Patch Tuesday and it crashed the infrared camera on my Thinkpad X1EG2. The blue screen of death also appeared when I tried to open the Lenovo Vantage," another user posted.

In addition, this update also has other performance issues such as system slowdown compared to before, lower frames per second when gaming, external hard drive not connecting and File Explorer is slow. In particular, the system will be very slow if the user uses the 3rd or 4th account on the system.

"When I open any application, my screen freezes for a few seconds before responding. It often freezes when I try to open folders, videos, music, code editor, Android Emulator, Adobe XD or any other windows, " user reports.

The only solution at the moment for those affected is to uninstall the Tueday Patch by going to Windows Update> View update history> Uninstall updates then right-clicking on the KB4566782 update and selecting Uninstall . After that, you should temporarily stop the update until Microsoft claims to have fixed the problem.

Samuel Daniel

Update 25 August 2020