Windows 10: DISM Scan Error : 1726

C:\Windows\system32>DISM /Online /Cleanup-Image /CheckHealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19043.928 The component store is repairable. The operation completed successfully. C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19043.928 Error: 1726 The remote procedure call failed. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log How to Fix this Issue?

:)

 

Running DISM Fails with Error: 1726

I can run the following commands and they all run fine and do not find any issues:

• DISM.exe /Online /Cleanup-image /Scanhealth
• DISM.exe /Online /Cleanup-image /Restorehealth
• sfc /scannow
• chkdsk /F C:

But the following fails every time:

• DISM.exe /online /cleanup-image /startcomponentcleanup

Even tried this which works and finds no issues but still fails if i run the above:

• DISM.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase /RestoreHealth

I did not have this issue until after the following update, at least to my knowledge: KB4549951

Running Windows 10 1909 18363.778 x64.

Does this have anything to do with Disk Cleanup being deprecated now?

When I run Disk Cleanup and select Windows Updates there is ~6GB and I select to remove it but it does not. I'm assuming that is the reserved space that I've been reading up on.

The exact error messages:

• Error: 1726 The remote procedure call failed (in cmd after running: DISM.exe /online /cleanup-image /startcomponentcleanup)
• Unable to start a DCOM Server: {0358B920-0AC7-461F-98F4-58E32CD89148}. The error: "2147942767" Happened while starting this command: C:\Windows\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683} (in Event Viewer)

 

DISM Error 1726 at 4.5% Progress

So, brand new clean install of Windows 10!

Drive was formatted, and I know what I'm doing when it comes to installs.

Conclusion:

1. Windows Update will open and the working dots are scrolling from left to right, but nothing ever happens.

1a. Ran troubleshooter tool on Windows Update, it found a corruption and repaired it - still don't work.

2. Windows Store Apps will open, but it doesn't do anything beyond loading with the spinning wheel of death. I ran the troubleshooter and it prompted me to reset and open windows store. So, I did. It just sat there with a moving progress bar to no resolve.
I tried the run command wsreset.exe and the window for it opened, but just sat on the screen. I tried to enter wsreset.exe in an elevated command prompt, it just sat there doing nothing.

I ran chkdsk - no errors.

I ran sfc /scannow - no errors.

I ran DISM - Dism /Online /Cleanup-Image /CheckHealth - no errors.

I ran DISM - Dism /Online /Cleanup-Image /ScanHealth - no errors.

I ran DISM - Dism /Online /Cleanup-Image /RestoreHealth - ERROR 1726 at 4.5% progress.

I WILL REPLY TO THE BOTTOM OF THIS POST WITH MY DISM LOG RESULTS INFO

 

Dism /ScanHealth Results in Error 1726


When I run a 'Dism /Online /Cleanup-Image /ScanHealth' command, I get the following error after reaching the 20% point:

Error: 1726
The remote procedure call failed.

I also had the following errors in my dism.log file:
2016-02-14 17:30:49, Error DISM DISM Package Manager: PID=9328 TID=100 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800706be)
2016-02-14 17:30:49, Error DISM DISM Package Manager: PID=9328 TID=100 Failed processing package changes with session option CbsSessionOptionDetectStoreCorruption - CDISMPackageManager::ScanHealth(hr:0x800706be)
2016-02-14 17:30:50, Error DISM DISM Package Manager: PID=9328 TID=100 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800706be)
2016-02-14 17:30:50, Error DISM DISM Package Manager: PID=9328 TID=100 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800706be)
2016-02-14 17:30:50, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800706BE

Any thoughts? The '/CheckHealth' option worked fine, but I had been having issues with 'sfc /scannow' which led me to trying to see if Dism might be able to resolve things...

Thanks!