[SOLVED] Failed to install 22-09 CU

[Remy]

Hello Sysnative,

I got problems installing the latest CU update on my system.
Can you guys help me out?

See the attachment for the latest cbs log after running dism and sfc scans

Regards,
Remy

 

[Maxstar]

Hi,

Please post a copy of the CBS folder to look at the older log(s).

• 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.

 

[Remy]

Goodmorning Maxstar,

See attachment for the log.

Regards,
Remy

 

[Maxstar]

Hi,

All older logs missing, did you delete them yourself?

Please attempt to update this system, and post the latest CBS log(s).

 

[Remy]

Im sorry, i uploaded only the latest log. i uploaded it again. See the attachment for all the logs.

 

[Maxstar]

Thanks.

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

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

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing

• Once selected, click File > Export....
• Change the Save as type: to Registry Hive Files (*.*).
  
  
  
  
  
• 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.

 

[Remy]

Hi,

See attachment and download link. https://wetransfer.com/downloads/138a4a1316d4760284e82a412af1b6c420221003094206/c2be4cc3a8fb9cad70000583f32e791020221003094225/d65e89

 

[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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt 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. Reboot the server and perform the following:

Step 3. Download

ComponentsScanner and save it to your desktop.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[Remy]

Hi Maxstar,

De see the attachment for the logs.

Regards,
Remy

 

[Maxstar]

== Missing Registry Values ==
CanonicalData\Deployments\21be8e1cd45..8b3febfb26c_31bf3856ad364e35_10.0.17763.1457_928a2cc6e520dd5f | appid

Hi,

The above error is now fixed, please attempt to install the latest LCU, if it fails attach a new copy of the CBS log.

 

[Remy]

The update has succesfully installed. Thanks again Maxstar!

Regards,
Remy

 

[Maxstar]

You're welcome. Glad to hear we could fix this issue as well...
I'll mark this thread as solved