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

179 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-02-12T22:43:51+00:00

    More of the same here.  EliteDesk 705 with Ryzen CPU, Sure Start, etc.

    I've read Ryzen CPU's have covered some security vulnerabilities better than Intel, and perhaps that is actually causing this problem, where an Intel will let this update do what it's doing, the Ryzen CPU does not?

    Anyway, I'm blocking this update centrally for now.  What a pain.  I've tried the steps outlined here, all of them, and nothing is correcting the problem, so I'm just moving on.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-02-12T21:46:51+00:00

    We are also having this issue on all of our HP EliteBook 745 G5's with AMD Ryzen APU. Sure Start is enabled on all of them. We can confirm that Lenovo based AMD Ryzen laptops are not having the same issue with KB4524244 with Secure Boot enabled. We have pulled this KB from SCCM. We have sent the issue to Microsoft Platforms DSE and they are looking at the issue internally.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-02-12T18:55:35+00:00

    In our environment, this is happening on all HP AMD based machines with Sure Start Secure Boot Key Protection enabled.  If we turn that off before the initial attempt to install the KB then the KB will install.  After restart we can renable the Sure Start protection.  Each machine we've done this to also has to be rebooted two more times after the patch install for the NIC to be come active properly again.  During the time the NIC isn't working properly an "ipconfig /all" command won't show the NIC adapters, but they appear in Device Manager and in Control Panel/Network Connections.   On PCs where the Sure Start protections are in force at the time of patch install we get the same error Mikael Sillman

     did.  Sure Start then resets the keys and the system will boot up.  Subsequent attempts to install the patch fail.  Most often the error code is 0x80242FFF.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-02-12T17:13:52+00:00

    I'm having the same problem on Apple Bootcamp.

    KB4524244 - Error 0x800f0922

    Tried to manually install it without success.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-02-12T15:34:30+00:00

    Also DELL server "HOSTS" with Server 2019 install having issues. The kb article references all W10 nothing about Server 2019 yet its the same KB even if you manually download the Server 2019 patch from the MS catalog site. Installs fine on VM's & given it's EUFI references I suspect there is fault in how it is communicating to the hardware itself.

     One thing is clear, don't waste your time trying to find "fault" in your local system, I think MS has to pull this & get it right.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments