2020-02 Updates KB4524244 Locks Up My Computer and Fails Install

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

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

I'm having exact same issue with 24 HP EliteDesk 705 G4 DM mini PCs running Windows 10 v1909 aka 10.0.18363.657. Other pending updates installs, machines reboots and then this KB4524244 appears and the PCs appears to be halted by HP Sure Start. After a hard reset HP Sure Start reports that it detected unauthorized change to the secure boot keys, then Windows loads, undo changes and restarts again. This is obviously annoying and so HP needs to advise Microsoft that this is indeed happening and figure out what to do about it. Meanwhile I will need to block KB4524244 from systems.


Helping people in business with computers

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I am having the same problem with an HP Desktop, but running Intel Core i5 7400, not AMD. I have secure boot turned off, and the installation runs up to 99% and fails. No locking up, though.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 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.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 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.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

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.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Same but on a PC.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

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.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

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.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Reply In reply to deleted message

Me too .. running on Apple Bootcamp and exactly same error and count not manually install

Have you reported it to Microsoft with "Feedback Hub"?

https://support.microsoft.com/en-us/help/4021566/windows-10-send-feedback-to-microsoft-with-feedback-hub-app

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes I have

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated November 6, 2020 Views 24,069 Applies to: