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

Anonymous
2020-02-12T01:43:44+00:00

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

Windows for home | Windows 10 | Windows update

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.

0 comments No comments

179 answers

Sort by: Most helpful
  1. Anonymous
    2020-02-14T01:46:40+00:00

    Same but on a PC.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-02-14T01:29:03+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-02-14T00:44:45+00:00

     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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-02-13T22:56:14+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-02-13T21:14:51+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments