[SOLVED] Unable to install Cumulative updates on the 2022 Windows Server Standard

P

plevko

Active member
Joined
Aug 24, 2022
Posts
29
Hello,

I have not been able to install any cumulative updates on the Windows 2022 Standard server since the 2023-04 package. I have tried to reset store, remove other language updates but no luck. Component store not returns any corruption nor SFC scan. I have tried different cumulative updates after 04 and none seems to install. Error I am getting 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: (0x80073701). Reviewing CBS logs shown some SXS corruption and missing Package_for_ServicingStack_1780~31bf3856ad364e35~amd64~~20348.1780.1.0 this file. SFC and DISM /restorehealth comes out clean.

Jerry
 

Attachments

Would be ok to try Tweaking Windows repairs on the 2022 server as well? I have used this on 2012 R2 and it fixed the Windows updates issue. Any recommendations?
 
Hi,

Sorry, but you're thread must have been overlooked in the amount of threads in this section. The Components.zip file in post #3 is not the COMPONENTS hive but a copy of the Components Based servicing hive! However, here's the first fix based on your latest CBS log.

Step 1. Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-Eng.gif

  • 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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Hi, thanks for the update! I do appreciate it. I did ran SFCfix and attached is the text file.

When re-run dism command it did failed. Attaching new cbs.log as well in zip format
 

Attachments

Hi,

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.
650c22f99662d-6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

HI, SFCFix.txt is attached. DISM restorehealth command completed successfully.

dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.2113

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
 

Attachments

Hi,

Great, please attempt to update again. If it fails attach a new copy of the CBS logs.
 
Please upload a new copy of the COMPONENTS hive.

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.

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Hi there,

Attached is export of the component based servicing hive. I will grab and upload Component file later on when can restart server as it is in use.
 

Attachments

Please provide the Components Based Servicing export as *.hiv file instead of *.reg.
 
Hi,

This is an odd issue (bug) with Server 2022 versions, a large number of RTM keys are missing as well as keys for other cumulative updates. So I recommend to perform an in-place-upgrade with the server 2022 ISO. This is the most effective way to fix this server.

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.

    653263088a599-windows-server-2022-setup.png

  • 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.
 
This was mentioned to me also by some techs from Microsoft. Thanks for looking into this! I will have to stand up some other system as this is production server with AD DC role on it.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top