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

W

WindowsConnoisseur

Member
Joined
Nov 23, 2024
Posts
23
Hello,

I upgraded from Windows 10 (all latest updates) few days ago to Windows 11. I'm used to do DISM /Online /Cleanup-Image /StartComponentCleanup which worked without problems on W10 but after the upgraded to W11 suddenly I started to get this Error 1726 on 5% of the command.

From what I read so far it seems this error usually prevents also other DISM commands or Windows updates - but they work fine for me from what I've seen.

It seems only the /startcomponentcleanup and the /resetbase get this error.

Event Logs show:
Faulting application name: TiWorker.exe, version: 10.0.26100.2303, time stamp: 0x50945f65
Faulting module name: ucrtbase.dll, version: 10.0.26100.1882, time stamp: 0x52db7a2d

I've tried the ProcMon and PE already without any success to understand what's going on. And an hour ago I found out about the C:\Windows\System32\config\systemprofile\AppData\Local\CrashDumps that store the TiWorks.exe crash dumps that I can read with the WinDbg.

Here is the dmp log attached:

The CBS/DISM.logs show also the clr.dll faulting but now in the dmp it says CbsCore.dll also I have noticed it says as OS Name Windows 10? Shouldn't is be Windows 11?

Any ideas what is really going on and how to fix it? I'm all out of ideas.


PS: Just noticed that I actually have 5 directories "C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.XXXX" with different versions. Is this normal?

5dirs.webp
 

Attachments

Last edited:
Faulting application path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.26100.2303_none_a52bce0377496620\TiWorker.exe
 
I have the feeling it has something to do with the PCR7 Binding Not Possible. Before the upgrade my previous Windows10 had PCR7 on Bound. Yesterday after I created this thread and I read about the "Stack overflow" that it has something to do with protected memory I thought about TPM. I started System Information and saw that PCR7 now is not bound.

Problem is I can't fix it now. My TPM 2.0 is fine, Secure Boot is ON, even enabled the S0 standby mode - but PCR7 is staying on not possible. I don't know what happened with Windows 11.

I also installed my new 9800x3d yesterday night and was hoping that it might fix things but no, no difference.

1.webp
 
Hi,

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

Hello, sorry for my late reply I was on a little holiday. Thank you so much for the time and help.

The /RestoreHealth command has been working from the beginning. It's the /StartComponentCleanup that isn't.

The SFCFix asked for a restart to finish the job but after that I still get error 1726.

1.webp
 

Attachments

Rich (BB code): 
2024-12-04 19:39:43, Error                 DISM   DISM Package Manager: PID=13672 TID=13664 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)
2024-12-04 19:39:43, Info                  DISM   DISM Package Manager: PID=13672 TID=13664 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2024-12-04 19:39:43, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

WindowsConnoisseur said:
It's the /StartComponentCleanup that isn't.
Click to expand...

There's no need to run such commands or with the "/resetbase" parameter! However, post also the CBS logs since the DISM log is not very helpful.
 
Maybe a newer one that says "HyperV-OptionalFeature-VirtualMachinePlatform-Client-Disabled-FOD-Package~31bf3856ad364e35~amd64~~10.0.26100.2314 is self-owned with other owner, this indicates PBR has been used and the LCU wrapper has been re-applied." is better?

I'll just add it in any case. Not sure if it is redundant. Sorry if it is.
 

Attachments

Hi,

Open an elevated prompt, run the following command and copy paste the result in your next post.
Code: 
reg query "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs"
 
Code: 
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs
    DependOnService    REG_MULTI_SZ    RpcEptMapper\0DcomLaunch
    Description    REG_SZ    @combase.dll,-5011
    DisplayName    REG_SZ    @combase.dll,-5010
    ErrorControl    REG_DWORD    0x1
    FailureActions    REG_BINARY    00000000000000000000000001000000000000000200000060EA0000
    Group    REG_SZ    COM Infrastructure
    ImagePath    REG_EXPAND_SZ    %SystemRoot%\system32\svchost.exe -k rpcss -p
    MitigationFlags    REG_DWORD    0x32
    ObjectName    REG_SZ    NT AUTHORITY\NetworkService
    RequiredPrivileges    REG_MULTI_SZ    SeChangeNotifyPrivilege\0SeCreateGlobalPrivilege\0SeImpersonatePrivilege
    ServiceSidType    REG_DWORD    0x1
    Start    REG_DWORD    0x2
    SvcHostSplitDisable    REG_DWORD    0x1
    Type    REG_DWORD    0x20

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RpcSs\Security
 
This looks good, so please do the following.

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.
 
Please run the DISM command again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Run the DISM command just like you have in the past.
3. Stop Process Monitor a minute after it fails, just to be sure everything is logged. You can simply do this by clicking the capture icon (CTRL +E) on the toolbar as shown below.

Process-Monitor.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer | Send Large Files Fast - Up To 2GB Free and provide the link.
6. Upload also the latest CBS log for the time stamps.
 
Hi again,

I tried and I was able to upload the LogFile.PML zip directly as attachment as max compression made it 19MB. If it's a problem I'll re-upload it to WeTransfer.
 

Attachments

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Right-click on the file FRST64.exe and choose Run as administrator.
  • Copy and paste the following (code) into the Search box and click the Search Files button.
Code: 
HyperV-OptionalFeature-VirtualMachinePlatform-Client-Disabled-FOD-Package-Wrapper~31bf3856ad364e35~amd64~~10.0.26100.2161.cat
  • When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
  • Post the logfile Search.txt as attachment in your next reply.
 
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.
 

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