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”.
Some users reported that this DISM problem happens right before the process is supposed to end. According to experts, this error in DISM occurs due to any of the following reasons:
- A third-party program might have interrupted the DISM operation and is the one that triggered the 1726 error: “The remote procedure call failed”.
- The error could also pop up when there is a pending corruption repair. This usually happens when you tried to run a DISM command previously that was terminated manually or was halted because of some malfunction.
- Lastly, the error could also occur because the process that’s responsible for the procedure is disabled or was prevented from running.
Whichever the case is, here are some suggestions that might help you in resolving the 1726 error: “The remote procedure call failed”.
Option 1 – Try updating your PC to the latest Windows build available
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.
- Tap the Win + R keys to open the Run dialog box.
- Then type “ms-settings:windowsupdate” in the field and hit Enter to open the Windows Update screen.
- After that, click on Check for Updates and then follow the next on-screen instructions to apply the latest Windows update.
- Once the update has been installed, restart your PC and run the DISM command again and see if the problem is fixed.
Option 2 – Try to change the Startup Type of the Remote Procedure Call service
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:
- Tap the Win + R keys to open the Run dialog box.
- Type “services.msc” in the field and hit Enter to open Services.
- From there, scroll down until you see the Remote Procedure Call (RPC) service and then right-click on it and select Properties.
- Then go to the General tab and change the drop-down menu next to Startup type to Automatic.
- After that, click the Apply button and then OK to apply the changes made.
- Restart your PC and run the DISM command once again at the next startup.
Option 3 – Try to modify the RpcSs registry key value
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.
- Tap the Win + R keys to open the Run dialog box.
- Type “Regedit” in the field and hit Enter or click OK to open the Registry Editor. And if a User Account Control prompt appears, just click on Yes.
- After that, navigate to this registry key: HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services RpcSs
- After selecting the aforementioned registry key, go to the right pane and double-click on the Start value.
- Next, change the Value data of start to 2 and click OK to save the changes made.
- Exit the Registry Editor and restart your PC and check if the 1726 error in DISM has already been resolved or not.
Option 4 – Try to disable the Windows Search service temporarily
Some users also recommended disabling the Windows Search service for the meantime as it could be the one that’s interrupting the DISM process.
- Tap the Win + R keys to open the Run dialog box.
- In the field, type “services.msc” to open the Services window again and hit Enter to open it.
- Next, scroll down over the services list and double-click on the Windows Update service.
- Afterward, go to Windows Search properties and click the General tab and then click the Stop button to stop the service from running temporarily.
- Now try running the DISM commands again and see if the problem’s fixed or not.
- Restart the Windows Search service and then restart your PC as well.