Unable to install Latest CU on Windows 11 24H2 Devices.

SuhailNabi007

SuhailNabi007

Active member
Joined
Oct 11, 2024
Posts
37
Unable to install Latest CU on Windows 11 24H2 Devices.

- I ran Component scanner -
- I have performed In place repair twice. One from OCT ISO and another from NOV ISO which is the latest on M365 Center

Please check as I will be be attaching 2 CBS folder of same device.
 

Attachments

Hi @SuhailNabi007,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team
 
Hello Maxstar, Thank you for your response & to be honest its the best thing I have seen today!

I have downloaded the Patch manually and then when trying to install I get this error

1735143937137.webp




Also, If I try to do it with DISM Add package. It given an similar error

I also saw there are so many packages staged on the device SS Below:

1735144042022.webp



Also I tried to remove all packages but it didn't help in any way!

Let me get the CBS logs before the IPU as that's when the error started but I was able to install SSU easily as always.
 

Attachments

Hi,

As said, we don't provide help in private messages and you have tried an in-place-upgrade twice without any luck! So I would suggest to backup all the important data and reinstall this system from scratch. This because deleting packages with DISM was also not an good idea...
 
Hello Maxstar,

I have like 100 Machines having this issue.

And I have been working all on just 1 test machine.

IPU did resolve the staged packages twice but we are still unable to patch the device with DEC CU
 
Hi,

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.
 
Are all the systems based on the same template which should be installed in August this year?
 
Hello,

I believe these machines were deployed from same template

and we have some machines deployed just 2 months back and they are facing same issue.
 
Hmm, please do the following as well on the same machine.

Step 1. Download
61f7aba7309a1-ComponentsScanner_Icon.png
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.


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

    652ff1dfded79-622dbdc454cdb-Export-SBS-hive.png

  • Name this file SideBySide (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.
 
It looks like the template is a custom image from which several components have been removed, is that correct?
 
This is never a good idea, as it always will result in issues like this when components are removed from the base image. So I can only suggest to create an new 'golden' image' with the necessary policies to deploy on multiple systems, without removing components. And then you can re-image all the clients with a reliable build.
 
By any chance Maxstar, please please can you help with these three :

Checked the CBS logs:

2025-01-10 13:29:33, Info CBS =================================
2025-01-10 13:29:33, Info CBS Checking System Update Readiness.
2025-01-10 13:29:33, Info CBS
2025-01-10 13:29:33, Info CBS (p)  CBS MUM Missing        Microsoft-ActiveDirectory-PowerShell-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2025-01-10 13:29:33, Info CBS Repair failed: Missing replacement mum/cat pair.
2025-01-10 13:29:33, Info CBS (p)  CBS MUM Missing        Microsoft-Windows-CredentialManagementRole~31bf3856ad364e35~amd64~~10.0.17763.1
2025-01-10 13:29:33, Info CBS Repair failed: Missing replacement mum/cat pair.
2025-01-10 13:29:33, Info CBS (p)  CBS MUM Missing        Microsoft-Windows-PowerShell-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.17763.1
2025-01-10 13:29:33, Info CBS Repair failed: Missing replacement mum/cat pair.
2025-01-10 13:29:33, Info CBS
2025-01-10 13:29:33, Info CBS Summary:
2025-01-10 13:29:33, Info CBS Operation: Detect and Repair
2025-01-10 13:29:33, Info CBS Operation result: 0x800f081f
2025-01-10 13:29:33, Info CBS Last Successful Step: Entire operation completes.
2025-01-10 13:29:33, Info CBS Total Detected Corruption:  3
2025-01-10 13:29:33, Info CBS   CBS Manifest Corruption:  3
2025-01-10 13:29:33, Info CBS   CBS Metadata Corruption:  0
2025-01-10 13:29:33, Info CBS   CSI Manifest Corruption:  0
2025-01-10 13:29:33, Info CBS   CSI Metadata Corruption:  0
2025-01-10 13:29:33, Info CBS   CSI Payload Corruption:  0
2025-01-10 13:29:33, Info CBS Total Repaired Corruption:  0
2025-01-10 13:29:33, Info CBS   CBS Manifest Repaired:  0
2025-01-10 13:29:33, Info CBS   CSI Manifest Repaired:  0
2025-01-10 13:29:33, Info CBS   CSI Payload Repaired:  0
 
Is this for the same server?

Step 1. Download
67139f7e69a58-SFCFix-ico.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 SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
67139f52b3c1e-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

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