Windows 11 24H2 2600.2314 DISM /Online /Cleanup-Image /StartComponentCleanup Error 1726

[WindowsConnoisseur]

Hmm :/

 

[Maxstar]

Please provide a new copy of the CBS hive.

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.

 

[WindowsConnoisseur]

Here it is.

 

[Maxstar]

Hi,

Please run ComponentsScanner again.

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.

 

[WindowsConnoisseur]

Seems the same as before.

 

[Maxstar]

Open an elevated command prompt and run the following command. Attach Dirlist.txt to your next post.

dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2303_none_a52bce0377496620 > "%userprofile%\Desktop\Dirlist.txt"

 

[WindowsConnoisseur]

Here it is.

 

[Maxstar]

Step 1. Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

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

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

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

 

[WindowsConnoisseur]

Here they are. No restart was needed.

 

[Maxstar]

Great, please run ComponentsScanner again and attach the result.

 

[WindowsConnoisseur]

Here it is.

 

[Maxstar]

Now run the DISM command again and post the result and the CBS logs if it fails.

 

[WindowsConnoisseur]

 

[Maxstar]

Hmm, I'll need do to some tests on a VM to see if I can reproduce this issue!

 

[WindowsConnoisseur]

Sure. It seems messy. :)

This Hyper-V component that shows up in the logs is something I removed few days after the upgrade from win10 to win11. It shouldn't be the problem because I was getting the error 1726 before I unchecked it in the windows features. If that helps somewhat.

It seems there are few layers of complication. But this issue is definitely above my head.

 

[Maxstar]

I actually think that's the problem, because it's still present under the subkey catalogs to uninstall? Do you have a backup before removing the Hyper-V component.

 

[WindowsConnoisseur]

No I don't.

Maybe you are right. I don't exactly remember why I decided to remove the Hyper-V but maybe it was because there were some errors in the Event Viewer in connection with it. I have such faint memory.

 

[Maxstar]

Then I would suggest to enable the Hyper-V feature first to see if it will resolve this issue.

 

[WindowsConnoisseur]

Same. There's second CBS log now. Maybe a bit different?

 

[Maxstar]

Still the same issue, so I will prepare a VM with some exports of the CBS hive to see if I can reproduce this issue.