I'm pretty new to being a SysAdmin but have over 27 years of tech experience. Right now, I'm facing a challenge with our HyperVisor server that's running Server 2022 Standard. It has stopped accepting cumulative updates, whether I try through the Windows Update application or manually from the online catalog. Each attempt fails with error code 0x8024200B. I've exported the update logs and even had a session with ChatGPT to devise an action plan, which I carried out yesterday but didn't yield any results.
Here's what I've tried so far: 1) Restarting the server and retrying the installation. 2) Resetting update components with various command prompts followed by another reboot. 3) Running a repair on the Component Store and then using the SFC command, followed by a reboot and retry. 4) Attempting a manual install from the catalog. 5) Verifying the Servicing Stack Update (SSU), but I couldn't confirm if it's up to date. 6) Finally, considering a reinstallation of Server 2022 while keeping settings and apps, but that option is greyed out, likely due to corrupt system components.
I'm hoping to resolve this issue without taking the drastic step of backing up my VMs and wiping the hard drive. Any insights or help would be greatly appreciated!
5 Answers
I suggest trying to install the cumulative update using DISM instead of WUSA. Make sure to check the CBS.log file for any '0x8' error codes before and after you reboot; you'll likely get a more detailed error report that might reveal what's going wrong.
Regarding your point about the servicing stack, it used to be a separate KB but has since been merged into cumulative updates. For your setup, it might be KB5068787. Before anything else, I’d definitely recommend diving into the CBS.log to get a clearer picture of what’s happening.
Check if the update is suitable for your server. If you can, try booting into Safe Mode to install the update – sometimes that helps bypass issues with regular installs.
The error 0x8024200B is quite generic, indicating that there's a failure during the update process. You might want to check the CBS or DISM log files for more specific errors, as they often reveal additional details that can help pinpoint the problem.
It sounds like you've done quite a bit already! If you haven't tried it yet, grab the update logs and run them through ChatGPT. It often suggests running SFC /scannow, but it's a solid step, so don't skip that.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures