[SOLVED] Windows Server 2022 no installing Cumulative Update 2023-08

[prolannic]

We have an issue with an Windows Server 2022 and Cumulative Update 2023-08.

Error is:
There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f081f)

DISM /Online /Cleanup-Image /ScanHealth --> no Store corruptions
sfc /scannow --> no errors found
resetted Windows several times --> no improvment

any ideas what to do next?

 

[prolannic]

Has anyone an idea how to solve this? Still facing the problem

 

[Maxstar]

Hi and welcome to Sysnative,

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.

 

[prolannic]

Hi @Maxstar

Find the COMPONENTS.zip attached.

Please let me know, if you need anything further.

 

[Maxstar]

Hi,

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

 

[prolannic]

Hi @Maxstar

I've applied the SFCFix and run the DISM-Command successfully. Unfortunatly, the error still appears when installing KB5029250. It counts to 100% and then the error appears

 

[Maxstar]

Please provide the latest CBS logs to look at.

 

[prolannic]

Attached the latest CBS Logs

 

[Maxstar]

Here's the next fix.

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

 

[prolannic]

Unfortunately still the same error when installing updates

 

[Maxstar]

Is this server recently crashed? It looks like a large number of registry keys got corrupted, including associated keys and payload/manifest files.

 

[prolannic]

Not to my knowledge. I've rebooted it several times in the last 2-3 weeks because of the error but no crashes.

 

[Maxstar]

Okay, here's the next fix.

Step 1.
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

 

[prolannic]

still no success

 

[Maxstar]

Hi,

It seems this is a common bug with Windows Server 2022, so I would suggest to perform a repair install.

In-place upgrade Server 2022.

• Mount the Windows Server ISO and run Setup.exe. You can use the Microsoft Evaluation Centre to download the ISO files.
• 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 !!!
• Depending on your Windows Server version and license, you may see a screen prompting you to enter the licensing key.
• 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.

 

[prolannic]

Inplace Upgrade resolved the issue for us on two servers.
Thanks for your help

 

[Maxstar]

Hi,

You're welcome. Glad to hear the repair install resolved all the issues..