I ran sfc /scannow from Command Prompt with administrator privileges, but the system could not repair itself, even after rebooting. I tried to repair the Windows Store using the Windows 10 install image using†
Dism /Online /Cleanup-Image /RestoreHealth /source:wim:E:\sources\install.wim:1 /limitaccess
but that fails with error message "Error 1726 The remote procedure call failed." Running these commands in safe mode makes no difference. Please help.
Here is a screenshot of the above process and error
, the dism.log file, the CBS.log file, and a list of system services which I have disabled (as compared to default).
† - See Windows cant repair even with sfc /scannow and How to run DISM against a local source?
install.wim:1does something very specific and where a different value then1does something else. Which is the reason I ask these questions – Ramhound Jul 21 '16 at 21:21#define RPC_S_CALL_FAILED 1726L. What likely is happening is there is a lock, on a file, that is blocking the scan from happening. You can determine what that file is with a tool like Process Explorer. The cbs.log will contain, `Unable to move file to pendingDeletes. Filename ......", if that is the case. – Ramhound Jul 21 '16 at 21:26sfc /scannowto attempt to diagnose the issue. – Brandon Lebedev Jul 22 '16 at 15:07install.wim:1. I just copied from the second referenced SuperUser answer. – Brandon Lebedev Jul 22 '16 at 15:10Dism /online /Cleanup-Image /StartComponentCleanup? – Ben N Jul 22 '16 at 18:34Dism /online /Cleanup-Image /StartComponentCleanupworks successfully, but both prior problems still persist. – Brandon Lebedev Jul 24 '16 at 04:32