This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I received the Patch Tuesday releases today. KB4532693, KB4537759 and KB4538674 dropped in the first wave and all installed successfully. On a subsequent "Check for Updates" KB4524244 downloaded and installed but on the reboot, it rebooted the first time but froze hard on the second re-boot with Step 2 information and a frozen spinner on my screen, no keyboard or any access. After about 15 mins I finally forced the system down. On the reboot, my Secure Boot flagged me that the keys were corrupted. I was able to get those repaired and reboot into the system. I rebooted a couple more times but no updates attempted to install. On a third "Check for updates, the same (KB4524244) update attempted to download but freezes the system at 94% on the download. Again freezes hard requiring a hard re-set. I tried flushing the Software Distribution cache but get the same results.
FYI: I am running Windows defender with VBS (Credential Guard and Hypervisor enforced Code Integrity on an HP EliteDesk 705 G4 MT with a AMD Ryzen 5 PRO 2400G with Radeon Vega Graphics. I also have a similar set up running on an HP laptop (Intel i5), but the update installed fine on it.
Help
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
We have run into the same issue. 12 computers...
AMD Ryzen 5 Pro 2400GE w/ Radeon Vega Graphics
8 GB RAM and running on build 1909.
All computers get to 96% on the installation and hard lock. The screens will eventually time out and go dark, other than that they are completely unresponsive.
Added bonus, some get EXTREMELY hot if left alone for too long after locking up.
Blocking the update seems to be the only fix as of now.
Same issue as the others but on an i3 Dell machine running Windows build 1909 as the second OS to Pop_OS. 498 MB EFI partition with 204 MB available. No issues installing Windows updates other than this one with this setup. Have had it hidden with WSUHOWHIDE for a couple of days already, but I had assumed this would get resolved.
Same but on a PC.
Minimal risk (from what information offered), you are better off to isolate & disconnect then apply this patch if you really think this is a high-level threat. The irony is anyone without "Secure Boot" is no less at risk & doesn't have the issue. I am in legacy mode with a UEFI BIOS, this patch isn't that critical.
Stability trumps here. There is no remote access or non user intervention scope that they reported to the issue.
Or perhaps give them the benefit of doubt & perhaps it is "so sever" they couldn't publish a legible definition of what this patch is supposed to protect against.
Like the "Spectre" scope, that patch caused way more harm to stability than it resolved. Albeit thanks to A Google engineer for reportedly releasing the details before a patch was properly tested. How long did it take & how many W10 OS builds to sort that out.
Block it with tools to do so as per the URL above. Clearly not a good patch.
That block tool also works for Server 2019. I blocked that already.
Unfortunately this is a security update rather than a usability/feature update. We are at security risk without the patch installed. @Microsoft/Apple Please fix it as soon as possible.
