[SOLVED] Server 2022: Cannot update anymore to the latest monthly CU

[hdservices]

Good evening,

On 1 server I can not update anymore to the latest monthly CU.
Other updates for Microsoft Exchange is still succeeding. It only refers to the monthly Cumulative Update.

Current version is 20348.768 (June 2022)

When I run SFCFix it says:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-06-04 23:33:54.033
Microsoft Windows Server 10 Build 20348 - amd64
Not using a script file.




SFCFix version 3.0.2.1 by niemiro has encountered an unhandled exception.
Currently storing 0 datablocks.
Finish time: 2024-06-04 23:34:06.887
----------------------EOF-----------------------

Attached you can find the logs, hope you can help me out.

 

[hdservices]

Is there anyone who can help me out?

Thanks! :)

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[hdservices]

Thank you for making time for this!

I did both steps, after that I tried to run the update but fails with: 0x80073701

Attached output of step 1.

 

[Maxstar]

Hi,

Upload a copy of the CBS folder

• Open Windows Explorer and browse to the C:\Windows\Logs folder.
• Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
• Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
• Click on the Yes button here.

• Attach the file CBS.zip to your next reply. If the file is too large to attach, upload the CBS.zip file to www.wetransfer.com and post the link in your next reply.

 

[hdservices]

Attached!

 

[Maxstar]

Upload your COMPONENTS hive.

• Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
• Please copy this file to your desktop.
• Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
• Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
• If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

 

[hdservices]

Attached!

 

[Maxstar]

A large number of RTM registry keys as well as keys for other (preview) updates are completely missing.Te most reliable way to resolve this is to perfom an in-place-upgrade, particularly because the server hasn't been updated for two years now.

In-place upgrade Server 2022 with the MSDN (Retail) ISO.

• Navigate to the URL below and sign-in with your MSDN registered account.
• https://msdn.microsoft.com/subscriptions/securedownloads/
• Use the search field to find and download the correct ISO file.
• Mount the Windows Server ISO and run Setup.exe.
• Use the option Download updates, drivers, and optional features (recommended) and click Next.
• Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
• When the following screen is prompted enter your (25 digit) product key. Note: Do not use the public KMS key as listed here.
  
  
  
  
  
• In the next screen, select the image of the installed Windows Server edition and click Next.
• Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
• After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.

 

[hdservices]

Awesome! This fixed it :)
Atleast I dont know if the NEW Cu goes well next month, but I guess it will!

Thank you again!

 

[Maxstar]

You're welcome. Glad to hear the issue has been resolved, I've seen similar cases with Server 2022 and an in-place-upgrade is most effective solution to get the server up-and-running again.

For now I will mark this thread as solved. But you can always leave a reply here if you have problems with the upcoming LCU...