Windows 11 24H2 DISM Error 1726 "The remote procedure call failed."

[fingertrigger]

Hi!

My Windows 11 installation seems unable to cleanup its updates (both via Disk Cleanup and DISM). Surprisingly, CheckHealt and AnalyzeComponentStore DISM commands work as expected and find zero issues, but StartComponentCleanup throws the following error:

> DISM /Online /Cleanup-image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26100.4202

[==                         4.3%                           ]
Error: 1726

The remote procedure call failed.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

In the DISM log file the errors are

Error                 DISM   DISM Package Manager: PID=12852 TID=8748 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)
Error                 DISM   DISM Package Manager: PID=12852 TID=8748 Failed processing package changes - CDISMPackageManager::StartComponentCleanupEx(hr:0x800706be)
Error                 DISM   DISM Package Manager: PID=12852 TID=8748 Failed to start component cleanup. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800706be)
Error                 DISM   DISM Package Manager: PID=12852 TID=8748 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)
Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

And in the CBS Log file its just

"Info                  CBS    Failed to FinalizeEx using worker session [HRESULT = 0x800706be]"

Everything else looks normal, there are no missing files, broken components or the like. I've gone as far as running Procmon and capturing activity from TiWorker.exe, which revealed this:

"TiWorker.exe","1412","Process Exit","","SUCCESS","Exit Status: -1073741571, User Time: 4.2968750 seconds, Kernel Time: 8.5468750 seconds, Private Bytes: 79 634 432, Peak Private Bytes: 80 236 544, Working Set: 95 412 224, Peak Working Set: 95 997 952"

As far as I can tell -1073741571 is 0xFFFFFFFFC00000FD, which is a generic Stack Overflow exception. This seems to happen at a random point while TiWorker reads .manifest files in \Windows\WinSxS\Manifests\ directory, but I cannot identify a single "corrupt" manifest file that causes this. I've tried running SFC Scan, DISM RestoreHealth, ComponentsScanner, SFCFix, but none of them have found any issues or made any improvements.
Your help will be greatly appreciated!

 

[Windows Update Bot]

Hi @fingertrigger,

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