
What is DISM Error 1726? Every time you encounter some issues in your Windows 10 computer, especially when it comes to corrupted system files, you can always use the SFC scan and if the SFC can isn’t able to resolve the issue, there is also the DISM tool you can use which usually resolve the vast majority of system file corruption sufficiently. However, there are times when even the DISM commands experience issues as well. Such is the case with the 1726 error: “The remote procedure call failed”.
Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.
Since the problem is specific to certain builds in Windows 10, you need to make sure that your computer is updated before you try other troubleshooting steps. Thus, follow the steps below to update your Windows 10 PC.
As stated early on, the error might also be caused by a disabled Remote Procedure Call service or RPC or that it might be prevented from running for some reason.
In case you don’t know, RPC is the service control manager for both COM and DCOM servers and it’s responsible for performing object variation requests, exporting resolution as well as distributing collection for the servers. And so if the server is disabled, all programs that are using COM and DCOM including the DISM commands, will not function correctly. Thus, you need to make sure that the RPC service is scheduled to enable itself on every system boot. To do so, here’s what you have to do:
If the option didn’t work, you can also try enabling the RPC service using the Registry Editor. Before you proceed, make sure to create a System Restore point first and then follow the steps below afterward.
Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.
“C:>Dism /Online /Cleanup-Image /RestoreHealth /Source:c:testmountwindows /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 [==========================100.0% Error: 14098 The component store has been corrupted. The DISM log file can be found at C:WINDOWSLogsDISMdism.log C:>”There are several fixes you can check out to fix the DISM Error 14098, “The component store has been corrupted”. You can try to run the Restore Health command or reset the Windows Update components, or whitelist the dism.exe in your antivirus program, as well as try to uninstall any recently installed updates. Follow the options provided below for more details.