How to Fix DISM Error 1726 “The remote procedure call failed”

Looking for easy solutions to fix DISM error 1726 “The remote procedure call failed”?

Windows has several built-in scanners that scan for issues and provide reliable solutions. One such scanner is the System File Checker (SFC). SFC checks the system for corruption files and replaces the corrupted file with cached copies. If SFC is unable to solve the issue, users move towards the DISM tool. 

DISM is one of the most powerful Windows diagnostic tools available, but it can sometimes fail to respond, like every other program. One such common DISM error is the error 1726. This error occurs right before the completion of a process. 

 

Fix: DISM Error 1726 “The remote procedure call failed”

 

The DISM Error 1726 “The remote procedure call failed” occurs when one of the following conditions is true:

  1. A third-party software interrupts the DISM operation. 
  2. The Remote Procedure Call (RPC) is disabled on your PC. 
  3. There is a pending corruption repair. This means that the previous DISM command was terminated unexpectedly. 

This guide will walk you through the process of fixing the DISM Error 1726 “The remote procedure call failed” in detail. 

Let’s get started.

 

1. Update Your PC. 

Microsoft updates Windows regularly. The newer versions add improved features into Windows, but unfortunately, some versions can have bugs. These bugs cause errors when you are trying to execute a command or launch a program in your PC. 

The DISM error 1726 occurs in some specific builds of Windows 10. Before trying any of the troubleshooting steps, it is essential to make sure that your Windows version is up-to-date. 

Follow the steps mentioned below to install any pending Windows updates on your PC: 

  1. Press Windows + R keys simultaneously to open a Run dialogue box. 
  2. Type “ms-settings:windowsupdate” in the dialogue box and hit Enter to open the “Windows Update” screen.

Fix: DISM Error 1726 “The remote procedure call failed”

 

  1. Click on Check for Updates and follow the on-screen instructions to install the updates successfully. 
  2. Once the pending updates are installed, reboot your PC and run the DISM command again to see if this method resolved the issue. 

That’s it. If a bug was causing the error, installing the latest Windows updates would solve the issue. If the problem persists, see the next method mentioned below. 

 

 

2. Change the Startup Type Of the Remote Procedure Call Service. 

The Remote Procedure Call (RPC) is a server that enables the programs using the Component Object Model (COM) and the Distributed Component Object Model (DCOM) to function properly. If RPC is disabled in your PC, several programs including DISM commands will fail to work. 

If you have been facing the DISM error 1726, you should try enabling Remote Procedure Call Service. For this, follow the steps mentioned below:

  1. Press Windows + R keys simultaneously to open a Run dialogue box. 
  2. Type  “services.msc” in the dialogue box and hit Enter

Fix: DISM Error 1726 “The remote procedure call failed”

 

  1. This will open the Services window. Find the Remote Procedure Call option and right-click on it.  

Remote Procedure Call Settings

 

  1. Select Properties and go to the General tab. 

Remote Procedure Call Properties

 

  1. Now change the Startup type to Automatic and click on Apply.
  2. Finally, hit OK and restart your PC. 

Changing the startup type will enable the RPC service automatically when you boot the system. This will solve the DISM 1726 error. 

 

 

3. Modify the RpcSs Registry Key. 

You can also enable the Remote Procedure Call (RPC) service via Registry Editor. If you could not solve the error using the method mentioned above, you should try modifying the RpcSs registry key using this method.

However, it is essential to back up the registry before moving forward with this method since improper execution can harm your system. 

To modify the RpcSs registry key using Registry Editor, follow the steps mentioned below:

  1. Press Windows + R keys simultaneously to open a Run dialogue box. 
  2. Type “regedit” in the dialogue box and hit Enter.

Fix: DISM Error 1726 “The remote procedure call failed”

 

  1. Next, click on Yes in the User Account Control (UAC) prompt to open the Registry Editor. 
  2. In the Registry Editor, navigate to the key mentioned below. 
HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet\ Services\ RpcSs

 

  1. After selecting the RpcSs registry key, double-click on the Start on the right panel.
  2. Type 2 in value data of Start and click on OK to save changes.

Windows Registry Editor

 

  1. Finally, close the Registry Editor and try running the commands again.

Enabling RPC service via Registry Editor will hopefully solve the issue and you will be able to run DISM commands successfully. 

 

 

4. Disable Windows Search Service Temporarily. 

Windows Search service is a platform that enables users to search for files and data within the system. This service is enabled by default and can sometimes interrupt the DISM process. 

If you have been facing the DISM error 1726, disabling Windows Search service can help resolve the issue. To disable the service, follow the steps mentioned below:

  1. Press Windows + R keys simultaneously to open a Run dialogue box. 
  2. Type “services.msc” in the dialogue box and click on OK. 

Fix: DISM Error 1726 “The remote procedure call failed”

 

  1. In the Services window, find Windows Search and click on it. 
  2. Click on Properties and under the General tab, select Stop to disable the service temporarily. 

Remote Procedure Call Properties

 

  1. Run the DISM commands again to check if the commands are running without any issues. 

We suggest you to temporarily disable the Windows Search service whenever the error occurs. You can enable it when the commands are executed successfully. 

This wraps up our guide about fixing DISM error 1726 “The remote procedure call failed”. We hope that the methods mentioned above solved the error in your PC. In our previous post, we have also introduced DISM error 1009 in Windows 10. Don’t forget to check that out if you have been facing the initialization error. If you have any confusion, feel free to let us know in the comment section below.

 

 

If this guide helped you, please share it. 🙂

Author

  • Zainab Falak

    Zainab Falak is a staff writer for Saint and an expert in Microsoft Windows, having authored more than 200 posts. She has a Bachelors in Actuarial Sciences and her passion for computers extends to exploring various aspects, from UI customization to the Windows registry and exploring error codes. Twitter LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *