I am not able to update my wimdows10 home and my muose aslo not working
2020-02 Updates KB4524244 Locks Up My Computer and Fails Install
![](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)
Anonymous
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.
179 answers
Sort by: Most helpful
-
Anonymous
2020-02-19T08:11:03+00:00 -
Anonymous
2020-02-19T06:16:02+00:00 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.
Fyi....
Microsoft releases patches in stages. Patches are assigned alpha labels/categories (B, C, D)
(B)Second Tuesday of each month
- new security fixes and previously released security and non-security fixes
(C and D) Third and Fourth week of the month
- validated, production-quality optional releases, primarily for commercial customers and advanced users “seeking” updates. These updates have only non-security fixes
MSFT has multiple programs covering testing of B, C, and D updates.
They are:
Pre-Release Validation(PVP), Depth Test Pass(DTP), Monthly Test Pass(MTP), Windows Insider Program(WIP), and Security Validation Program(SVP).
- the first three are Internal, the fourth WIP - only receives non-security fixes(C and D), the fifth, last is invite only for large commercial customers and ISVs.
C and D as noted are optional and intended primarily for seekers.
- C and D releases purpose(while validated internally) is to provide visibility into, and enable testing of, the non-security fixes that will be included in the next Update Tuesday release.
(i.e. optional field testing by those choosing to install the optional C and/or D updates and for those end-users seeking” to validate the non-security content of the next “B” release.
Thus, not everything we/you(as consumers) receives(automatically or optionally) is tested by Windows Insiders.
This thread is about KB4524244 which was a 'B' security update release.
- Having the 'B' label/category, like all 'B' releases ***are not*** advance tested in advance by Windows Insiders(WIP).
-
Anonymous
2020-02-18T18:22:03+00:00 Hi, looks like it is best to uninstall the update as per this article
Good luck
-
Anonymous
2020-02-18T02:06:27+00:00 It is hard to believe a Windows update could mess with BIOS boot keys. If it really has done that, we'll have to try to restore them by unplugging the computer & removing both batteries including the CMOS battery. After a while, plug it all back in & see what happens.
But I think there are three keys for you to try a few more times before that...
https://pcsupport.lenovo.com/us/en/solutions/ht118361
How to Boot From a USB Drive - ThinkPad
It says indeed it is the PF12 key. I'm thinking you must ensure you have done Step 2. Turn it on once, & do Step 2. Then do the rest. And try pressing PF12 at the black screen just before the Thinkpad logo.
Here are the other two keys...
https://support.lenovo.com/us/en/solutions/ht500222
Recommended ways to enter BIOS - ThinkPad, ThinkCentre, ThinkStation
(a) Does PF1 get it to BIOS Setup?
(b) It also says, "Note: For some models, instead of pressing F1, continuously press Enter during powering on until a Startup Interrupt Menu displays. The screenshot is for reference. The actual menu will be different."
Can you get that Startup Interrupt Menu? Then press PF12.
-
Anonymous
2020-02-17T20:05:06+00:00 I also have a similar set up running on an HP laptop (Intel i5), but the update installed fine on it.
Help
Yeah, I have an HP laptop that never has problems with updates. It successfully updated yesterday.