So all Cumulative updates for a single Server 2019 since January 2024 has had issues.
This specific environment is mostly 2022 and some 2016 servers - Not many 2019’s - I’ll have to double check if there are others or not.
Last successful on this environment on this specific server August 2023.
error code 0xc000021a immediately after rebooting
WinRE is only 450m - but not getting that error.
Enabled Safemode and after a few attempts as it tries to boot into safemode it ends up removing the cumulative update and boots - and shows the update failed.
Seems like a similar timeline - as above thread - Our 2022s no issue
is Secure boot Enabled - doesn’t help to disable - no change
vCenter Server 7.0 U3t 2024-10-21 7.0.3.02200 24322018 24322018
DISM /Online /Cleanup-Image /RestoreHealth - litlte difficult here as the system is in a secure, no internet environment
updates pushed via parent child wsus setup -
SFC /SCANNOW
Neither reports any errors when being run before hand. all checks out.
Anyway -
haven’t inspected the memory dump
Minidump via
windbg - shows this:
FAULTING_THREAD: ffffb90f82503040
PROCESS_NAME: smss.exe
ADDITIONAL_DEBUG_TEXT: Verification of a KnownDLL failed.
IMAGE_NAME: ntkrnlmp.exe
MODULE_NAME: nt
CUSTOMER_CRASH_COUNT: 1
Have you looked at the event viewer to see if there are failures? Might lead you to which DLL is having the problem.
I would suggest to get this system temporarily online to run your DISM. Or you might be able to mount a windows 2019 ISO and the be able to run the following.
Awesome suggestions -
System is online - so its not major - Just annoying that it won’t update and sfc finds no errors - but can’t run sfc after the update due to the BSOD…
Then safemode a few times - removes the update - takes 2-3 times - then will boot back up without issue, but shows Cumulative update failed - which makes sense.
I’ll give those a shot and report back and see if anything helps.
Do have the ISO - thank you for the DISM - source command! - always forget that one
Re-install VMware tools - will do
resetting - Update Components nice thought!
Initially when I had issues late last year -
Noticed - that disabling Secure Boot helped… but after Jan 24 no difference.
Which is partly why I’m looking at the WinRE partition.
issue with that -
Partition is at the start of the drive.
WinRE Partition > EFI > OS
I prefer them to be EFI > WinRE > OS
22 Default does it - EFI > OS > WinRE
Would have to boot to a partition manager and edit all of those up to fix it correctly - not major.
When I still had some 2019 running, I had a similar issue… Trying to remember how I resolved it.
For the partitions, I would shrink the OS partition by a bit in windows, boot to a linux disk and run gparted. Move the EFI and OS which ever way they need to be moved to make contiguous space for recovery, and then expand the recovery partition to be big enough.
Boot back into windows and I think there were some commands that need to be done to “prepare” the extra space for that update, a reboot might also do this. It was documented on the KB about the problems with this update, but again I think another reboot forces it to scan and adjust.
I did this same thing to all my 2022 and that update no longer plagues me, so either they pulled it, or it did it’s thing. Mine were also on XCP-NG, I haven’t had my vSphere lab up long enough to do anything like this.