Win 10 Pro 22H2 OS fails to boot after updates

Topic

New Reply

[Mike]

OS: Windows 10 Pro 22H2.  Device: Lenovo Z580 Laptop with upgraded SSD and memory. The laptop is not hardware compatible with Windows 11. 

You may have to be logged in to see images.

I’m currently using WUMgr, but for some reason three upgrades came through (a whole other problem) with a requested restart on 12/13

KB5019959, KB5020872, KB5015684 and Stack Service 10.0.19041.2300

I’m not sure which one caused the problem or if it was a combination, but after installation and a reboot I got a BSD.

After several attempts to auto repair, I was finally able to boot to safe mode. In safe mode, I was able to uninstall everything but KB5019959 and the stack service.

After restarting, it still did not boot normally. Now I’m thinking it may be two recent security dates.

I’ll update later.

Mike

• This topic was modified 2 years, 4 months ago by Mike.

Reply | Quote

Replies

See if anything at How to Fix the 0xc000021a update error on Windows 10? – Troubleshooting Central helps.

--Joe

1 user thanked author for this post.

Mike

Reply | Quote

Rather than start a new topic, I will add my current situation by pasting in the post I made on another forum (SDMB)

 

I have a PowerSpec desktop, not compatible with Windows 11:

Processor Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz 2.81 GHz
Installed RAM 16.0 GB (15.7 GB usable)
System type 64-bit operating system, x64-based processor
Windows 10 Pro

So, I came home and my computer had a little orange dot in the bottom taskbar, indicating it had installed an update (2022-12 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5021233)) and would restart later in the evening. So, I decided to restart while I was sitting there (my preferred method).

On “Update and Restart” the usual updating windows with a percentage came up and the computer shut off and started back up. So far, so good.

Then it all went south. The boot screen appeared, but then a blue screen with a “we’re sorry, go to Troubleshoot blue screen errors – Microsoft Support to see the problem associated with the code below (0xC000021a)” It then dumped me into a screen with Continue and Troubleshoot. Continue (to Windows 10) just resulted in the same screen (eventually)

So, I then tried a number of options in Troubleshoot/Advanced Settings, including Startup Repair, System Restore (point), trying command line “bootrec” suggestions from the net,and booting to Safe Mode (wouldn’t boot to Safe Mode, just went through the same error process dumping back in the Continue/Troubleshoot screen).

It seemed that all was lost and I’d have to do a System Reset (and have to reinstall all my non Windows programs, which is a PITA). I then tried a hail mary- I unplugged all my USB connections except for the mouse and keyboard and tried restarting. It restarted!

Except for the fact that Chrome will no longer launch (shows in my Programs but nothing shows up in Task Manager), the system seems to be back.

Except for the little orange dot in the taskbar…

So now I’m afraid to let the update finish installing. I’d like to Uninstall the update, but the Uninstall Updates window doesn’t show this update (only Updates as late as November). I’ve set the restart time to 24 hours from now, just to buy time, but that’s just a delaying tactic.

So, I’d like:

1. Help on how to roll back this partially installed update
2. Some words of wisdom talking me off the ledge of being afraid to Update and Restart
3. Advice on what I should do to avoid being forced to Reset if Update and Restart doesn’t lead to another blue screen
4. Any thoughts on why Chrome is borked (I suspect a successful restart might fix this, though)

Thanks, and please let me know if this should be in its own thread, as I’m new here

Reply | Quote

I finally had to do a reset which re-installed Windows based on my computer.  I kept my personal files (data).  Anyway what I was left with was version 21H2.  I’m almost certain that KB5021233 was what bricked the OS.  Using WuMgr I was able to keep that from installing and my current configuration is working fine.

Help on how to roll back this partially installed update

I was not able to roll back any update that resolved the problem

Some words of wisdom talking me off the ledge of being afraid to Update and Restart

I manually control the update process (although this troublemaker slipped by due to my own fault) using WuMgr (Windows Update Manager) or WuShowHide.  Both have extensive documation here on AskWoody.

Screenshot of the WU Manager I’m using.

Advice on what I should do to avoid being forced to Reset if Update and Restart doesn’t lead to another blue screen

I could not find any other method other than a reset.

Any thoughts on why Chrome is borked (I suspect a successful restart might fix this, though)

Several of my applications or programs had to be re-installed due to the reset corruption.

My key to a successful restart was to have all my data and applications backed up. I was able to use Windows “Safe Mode” to boot to and then copy anything else of importance to a flash thumb drive, but in that case—I was very lucky that safe mode even was an option.

Reply | Quote

You got a bsod?  Do you remember the error code?

I’m not seeing trending reports of bsods and normally bsods are driver related.  When is the last time you updated video cards, etc?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Did you catch the secure boot patch?

secure boot patch KB5012170

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Seeing some here: https://www.reddit.com/r/Windows10/comments/zl2mcr/cumulative_updates_december_13th_2022/

What’s the exact specs on your computer – processor?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Lenovo Z580 IdeaPad

CPU: Intel i5-3210M

Integrated Intel HD Graphics 4000
Updated SSD and memory.

Older model for sure (no TPM).  I suspected that there would be a time when I’d get a issue with an update since the drivers, chipset and bios haven’t been supported by the manufacturer since around 2015.

Perhaps living on borrowed time?  Yet it works fine now (speedy with no issues)…but without the December updates and 22H2.

Mike

Reply | Quote

Show in the original posting.  I believe it is 0 XC000021A.  No, I did not try the secure boot patch… Unless it was included in one of the December updates.

Reply | Quote

Mike,

This is exactly why we push making Image Backups with a reliable program for which you have created and tested Bootable Media (USB). If you had this in place before doing an update you could have been back and running in under a half hour with everything EXACTLY as it was before the update.

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

4 users thanked author for this post.

Coldheart9020, wavy, bbearren, Alex5723

Reply | Quote

Completely agree RetiredGeek.

For me though, backups are just one of the many tools I can use in a situation like this, since I had all the data backed up on a separate external drive and reinstalling my applications is no big deal.

A reset and reinstalling the applications took no more than 20 minutes. In this case, the reset cleaned things up nicely where a image would just put things back the way they were. In fact, what I should have really done was just do a whole new reinstall of the OS. I’m one of those people that thinks I should do that once in a (long) while.

Reply | Quote

If anyone is following this tread, after confirming that everything was working okay, I went ahead and installed 22H2 feature update.  After fairly extensive testing, everything appears to be working fine.  Now all this trouble may not be related to any of the updates, but rather some weird circumstances, unless MS updated one of the updates.

What is left in terms of the updates that I originally installed prior to the BSOD are:

KB4023057 Appearing yet again

KB5021089 Net Framework

Mike

Reply | Quote

Still think it was due to :  KB5012170: Security update for Secure Boot DBX – Microsoft Support

That update is not included in the December cumulative update.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Mike

Reply | Quote

Thanks Susan.  I appreciate your thoughts.  Well if it was KB5012170 then it’s working now.  Perhaps it was a sequence of install order/events?  Who knows at this point.  If there is anything you’d like me to test, I could still do it at this stage….for instance uninstall KB5012170 and then reinstall ?  Not sure if that would be a good test.

Mike

Reply | Quote

Zooming in (second image) gives the stop which says nothing unexpected (though it doesn’t explain why the problem occurred so it might be worth giving the drive and memory a check)

https://answers.microsoft.com/en-us/windows/forum/all/windows-10-bsod-error-0xc000021a/764d25ea-7122-46aa-8acf-9b8de31d6c92

I have seen the “unrepairable” form of that stop as result of loss of significant chunks of the system registry hive on Windows 7 (which meant it was possible to restore those from the C:\Windows\System32\config\RegBack folder by copying them over the active copies (WinPE) to prove the point.)

Next time might be worth investigating the DISM /revertpendingoperations option (https://social.technet.microsoft.com/Forums/windows/en-US/48d20da9-0535-462f-b177-f30f48992203/how-to-removing-a-pending-update-that-is-preventing-a-successful-boot?forum=w7itprogeneral) or maybe just use DISM to view the packages (which usually list in install order) and remove the last batch, after the usual disk check of course.

Worked on Windows 7, still good on Windows 10 as far as I know, fortunately haven’t needed it. That done, /restorehealth should leave it fit should it try updating again.

1 user thanked author for this post.

Mike

Reply | Quote

Microsoft: KB5021233 causes blue screens with 0xc000021a errors
https://www.bleepingcomputer.com/news/microsoft/microsoft-kb5021233-causes-blue-screens-with-0xc000021a-errors/

Moderator edit: HTML removed.
(Reply reinstated as potential solution to specific error of this thread.)

Reply | Quote

On one of my systems, the Win 10 22H2 corrupted the Windows install so that I cannot boot into Windows 10 Pro GUI. After two BIOS screens, the monitor goes black. How can I get a good Windows 10 22H2 or 22H1 installed?

Is there a method  using Windows on a USB stick? I have burned Windows 10 Pro 22H2 onto a USB stick. Can it be used to do an In-Place install?

” I was finally able to boot to safe mode. In safe mode, I was able to uninstall everything but KB5019959 and the stack service…I finally had to do a reset which re-installed Windows based on my computer.  I kept my personal files (data). ”

Mike, how did you uninstall everything recent in Safe Mode; and how did you do a Windows Reset and keep your programs?

Reply | Quote