Windows Update_Same Problem_Two Computers
Problem description: “Getting Windows Ready” Stuck Error
Problem occurs during Windows Update, after clicking “restart now”. I got the blue screen with message “Getting Windows Ready” “Don’t turn off your computer” and will not proceed.
Note: I have built two computers using the same hardware components. MOBO, SSD’s, HDD, memory, graphics card, etc.
Processor AMD Ryzen 5 3600 6-Core Processor 3.60 GHz
Installed RAM 16.0 GB
System type 64-bit operating system, x64-based processor
Edition Windows 10 Pro
Version 21H2
Installed on 1/24/2021
OS build 19044.1466
Experience Windows Feature Experience Pack 120.2212.3920.0
Details:
02/01/2022, first computer. Reconfigured Group Policy editor to allow for Windows Update. Intention was to install January 2022 updates. Clicked “check for updates”. Windows Update determined I needed
KB5009543 2022-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems
KB5008876 2022-01 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64
Also driver for Intel bluetooth and AMD graphics.
I believe I remember KB5008876, NET Framework, downloaded 100%. Then I got the “restart needed” message. I noted that KB5009543 Cumulative Update for Windows 10 HAD NOT completed.
I clicked “restart now”. Booted to the “Getting Windows Ready” screen and would not proceed. I waited for 15 minutes, actually a bit longer while on my other computer looking for solution. The fist article I read listed as first step to completely disconnect from internet. I disconnected this problem computer from the internet and within a couple minutes, fairly quickly, the computer rebooted to the usual blue screen with message about updating Windows lasting the typical short time and then continued to boot to Windows normally.
02/04/2022, second computer. I spent a couple days but did not find a lot of discussion regarding this issue so I figured I just got unlucky. Windows Update found the same updates that were needed for first computer. When I clicked check for updates the same exact events happened. KB5009543 Cumulative Update for Windows 10 was not finished downloading when I got the “restart needed” message. I clicked “restart now” and booted to the same “Getting Windows Ready” screen. Waited 15 minutes then turned off my gateway, disconnected from internet and private network. Things went a bit different. After a couple minutes instead of rebooting the screen message changed, adding “Progress 0%” to the message. Waited another several minutes, maybe 10 minutes, but computer did not proceed. Based on a hunch, I restarted the gateway. Soon after the gateway finished starting the message “Progress 0%” changed to “Progress 30%” then the computer booted normally, starting with the “finishing updates” screen, then to Windows 10.
Both computers:
I clicked “check for updates” (second time), results were “Windows is up to date”.
I checked Windows settings, Update & Security, view update history and saw that both KB5009543, and KB5008876 installed successfully. Checked “About” PC and noted that OS build 19044.1466 is specifically related to KB5008876.
I checked control panel / Security and Maintenance / Maintenance / View reliability history and noted
a critical event logged “Windows Update Stopped working”. Below, in list of Informational events, only KB5008876 2022-01 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows was on the list, summery was Successful Windows Update. Both computers.
Also for both computers the driver for Intel bluetooth and AMD graphics were installed.
I ran sfc /scannow as administrator, results were “Windows Resource Protection found corrupt files and successfully repaired them.”
Bottom line question is “did I just get really unlucky, or is there a problem common to both computers”
What is really interesting is when I searched the Ask Woody forums I found a recent post by JC Zorkoff where, in response to a different issue, he describes exactly the same problem I experienced. In his case, he used a disk image he created prior to Windows Update to get up and running. Link to his post,
I also create a fresh disk image of the OS drive before any Windows Update.
Any suggestions as to what caused this? I’m worried about the next time I update Windows.