Giveaway of the Day Forums

1. 

   mikiem2
   Moderator

   The update that can cause the biggest problems is kb4524244, which was offered if you checked for updates once this month's cumulative update had been installed, and did not require a restart. Originally when it was offered the only thing I could find from Microsoft was that it improved the servicing stack, IOW improved the update process. Now it's being reported that it plugs a security hole in 3rd party UEFI software -- UEFI is the way or method that newer device BIOS use when starting the device. This has broken some PCs & laptops, mostly AMD but some Intel, and the HP brand seems more effected. For HP PCs/Laptops that will no longer start, users need to turn off secure boot in the BIOS, start Windows, uninstall the update, then turn secure boot back on. Other users are experiencing problems installing the update, with the update throwing errors or freezing.

   Microsoft ***may*** have reissued the patch, hopefully fixed of course, since it showed up again for me this morning in Windows Update & installed. Or that could be just another thing that's broken with the update. I researched it because while everything initially said there would be no restart required, I had one copy of Windows 10 1909 that required a restart, then went through 3 steps, then restarted, went through 2 steps etc. before it finally restarted Windows. I've since seen this process reported by others.

   bleepingcomputer[.]com/news/microsoft/windows-10-kb4524244-update-causes-freezes-installation-issues/

   While researching that update I came across a lot of reports of kb4532693, the cumulative update, changing the account user name, then starting Win10 using the default user account. For some people restarting the PC/laptop [up to 3 times] apparently got things working. Others reported uninstalling the update worked.

   Posted 4 years ago #
2. 

   mikiem2
   Moderator

   Microsoft has now pulled KB4524244. In Win10 1909, clicking on that update in Update History opens a page on Microsoft's site for an older Win8 update instead. The purpose of the update may have been to fix a vulnerability from April 2019, adding keys for secure boot from a Kaspersky rescue disc to the Revocation Key List. While some people have reported additional problems, and I experienced several restarts, officially Microsoft only says it may not install or may break "Reset This PC". Muddying the waters a bit, some reports seem to tie the renamed account problems to KV4524244, while other attribute it to the cumulative update, KB4532693. On my older tablet, originally Win8.1 updated to Win10, now v. 1909, KB4532693 caused it to show attempting to repair Windows after restarting. That didn't seem to be working -- after a long while I restarted, it removed the updates, and Windows Update reported all the updates had failed. Downloading & installing KB4532693 manually worked, and the rest of the updates then worked, but then twice restarting afterward it wanted to do repairs again -- I immediately shut it back down & restarted, & each time it then started normally. Haven't had the problem since.

   zdnet[.]com/article/microsoft-pulls-security-update-after-reports-of-issues-affecting-some-pcs/

   neowin[.]net/news/microsoft-fumbles-another-windows-10-security-update-removes-it

   bleepingcomputer[.]com/news/microsoft/microsoft-confirms-windows-10-kb4524244-issues-and-pulls-the-update/

   betanews[.]com/2020/02/13/windows-10-kb4532693-lost-user-profile/

   Posted 4 years ago #

RSS feed for this topic

Reply

You must log in to post.