The files inside the patch were dated September 2019 - five months ago. You might restart into recovery with “Choose an option” at the top of the screen with various options or you might restart to your desktop and receive the error “There was a problem resetting your PC”. Using the “Reset this PC” feature, also called “Push Button Reset” or PBR, might fail. There’s a second bug in the patches, identified separately in the Windows Release Information status page: HP owners with Secure Boot enabled (more about that later) reported that their PCs wouldn’t reboot normally and, when forced, the HP BIOS said it detected an unauthorized change to the secure boot keys and had to restore. The patch wreaked havoc on many PCs, most notably HP PCs with Ryzen processors. But the Win8.1/1507 patch had the same bugs and met the same fate as its more illustrious co-conspirator, KB 4524244.
#Kaspersky issues with windows 10 update
That buggy patch was accompanied by a parallel patch for older versions of Windows, KB 4502496, called “Security update for Windows 10, version 1507, Windows 8.1, RT 8.1, Server 2012 R2, and Server 2012: February 11, 2020.” This time the name was correct. Win10 version 1909 wasn’t mentioned in the KB article, but the 1909 patch appeared in the Microsoft Catalog. The Knowledge Base article title was clearly wrong.From the KB article:Īddresses an issue in which a third-party Unified Extensible Firmware Interface (UEFI) boot manager might expose UEFI-enabled computers to a security vulnerability.
They’re almost invariably rolled into cumulative updates. We don’t get standalone security patches anymore.