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.
A little off this specific topic but when it comes to flakey USB & updates, I usually check & ensure I am running the latest BIOS for the motherboard. I don't argue the updates from MS causing you grief but I tend to find those type of issues have "two culprits".
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
When did Microsoft say that for users not part of the Insider Program?
Users of the Insider Program need to exercise extra caution as they are being exposed to untested (beta) programs and services that can (in the worst case scenario) destroy their computer. This is the risk they accept as part of the Windows Insider Program. This is not true of the normal user. Anything we get has already been tested and retested by the beta users (the Windows Insiders as well as Microsoft Engineers) and (hopefully) any negatives left over will be minor ones.
Certainly checking for updates is safe. I do it all the time.
On a subsequent "Check for Updates"
Microsoft a while back said that manual checks can result in unstable (for your config) updates showing up. Just wait for and install only pushed updates
