DISM error 1726

BrianInEngland · Feb 7, 2025

I'm getting this error when I run DISM /startcomponentcleanup

Error 1726 the remote procedure call failed

DISM /scanhealth works and shows no component store corruption

This is after running a Repair install

antspants · Feb 7, 2025

BrianInEngland said:
This is after running a Repair install

Not sure why that would be. But if it is a constant issue:

A possible fix I found online

Change Remote Procedure Call (RPC) Service Settings

In most situations, the DISM /Online /Cleanup-Image /RestoreHealth error 1726 occurs because of the disabled related service – Remote Procedure Call (RPC) service. You can fix DISM error 1726 by changing the startup type of the Remote Procedure Call (RPC) service.

Step 1: Open the Run dialog box by pressing the Win + R keys and input services.msc to enter the Services window.

Step 2: Scroll down to locate and right-click on the Remote Procedure Call (RPC) service and then choose Properties.

Step 3: In the General tab, make sure the Startup type option is Automatic. If not, change it and choose Apply and OK to save your choice.

Then you can restart your computer and check if the error is still there.

Fix 2: Modify the RpcSs Registry Key

Another method to enable the Remote Procedure Call (RPC) service is via Registry Editor. If the last fix can’t work, you can try this one.

But be careful, the registry editor is quite an important component for normal system operation, so you’d better back up your registry first to avoid any mistaken deletion. For details, you can refer to this post: How to Backup and Restore Registry in Windows 10.

Step 1: Open Run and input regedit to enter Registry Editor.

Step 2: Go to the following registry key by using the left panel.

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ RpcSs

Step 3: Select RpcSs and double-click Start from the right panel to type 2 in Value dataand click OK to save it.

Step 3: Select RpcSs and double-click Start from the right panel to type 2 in Value dataand click OK to save it.

[Fixed] DISM Error 1726 - The Remote Procedure Call Failed - MiniTool

What should you do when you encountered the DISM error code 1726 – “The remote procedure call failed”? If you have a similar issue, this post will be helpful.

www.minitool.com

As mentioned, it’s something I found online. I’m sure there will be other input.

Anibor_11 · Feb 7, 2025

Last year, I encountered this error repeatedly when I installed 24H2 in a unsupported computer, using an UFD customized by Rufus. I eventually found that the error appeared when I selected the option “Remove requirements for an online Microsoft account” in Rufus. When I left this option unmarked, the error disappeared.

Note that problem was not caused by Rufus, but either by the ISO (obtained via Media Creation Tool), or by the method specified by MS to implement the option (a Registry change).

BrianInEngland · Feb 8, 2025

antspants said:
Not sure why that would be. But if it is a constant issue:

A possible fix I found online

Change Remote Procedure Call (RPC) Service Settings
In most situations, the DISM /Online /Cleanup-Image /RestoreHealth error 1726 occurs because of the disabled related service – Remote Procedure Call (RPC) service. You can fix DISM error 1726 by changing the startup type of the Remote Procedure Call (RPC) service.

Step 1: Open the Run dialog box by pressing the Win + R keys and input services.msc to enter the Services window.

Step 2: Scroll down to locate and right-click on the Remote Procedure Call (RPC) service and then choose Properties.

View attachment 124673

Step 3: In the General tab, make sure the Startup type option is Automatic. If not, change it and choose Apply and OK to save your choice.

View attachment 124674

Then you can restart your computer and check if the error is still there.

Fix 2: Modify the RpcSs Registry Key
Another method to enable the Remote Procedure Call (RPC) service is via Registry Editor. If the last fix can’t work, you can try this one.

But be careful, the registry editor is quite an important component for normal system operation, so you’d better back up your registry first to avoid any mistaken deletion. For details, you can refer to this post: How to Backup and Restore Registry in Windows 10.

Step 1: Open Run and input regedit to enter Registry Editor.

Step 2: Go to the following registry key by using the left panel.

HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ RpcSs

View attachment 124675

Step 3: Select RpcSs and double-click Start from the right panel to type 2 in Value dataand click OK to save it.

View attachment 124676

Step 3: Select RpcSs and double-click Start from the right panel to type 2 in Value dataand click OK to save it.

[Fixed] DISM Error 1726 - The Remote Procedure Call Failed - MiniTool

What should you do when you encountered the DISM error code 1726 – “The remote procedure call failed”? If you have a similar issue, this post will be helpful.

www.minitool.com

As mentioned, it’s something I found online. I’m sure there will be other input.

Already set as Automatic service

BrianInEngland · Feb 15, 2025

Well I've not been able to fix this, I think the problem started when I rolled back from Beta to RP and did a repair install to .1742.
DISM /cleanup options don't work.

I'm seeing a lot of registry keys like this, which don't look right to me

Hopefully a repair using .3194 UUP Dump ISO will fix it

BrianInEngland · Feb 16, 2025

OK I've fixed it.
I uninstalled the .Net update that I think caused the initial problem
Ran a Repair install using the official MS ISO .1742
Used the 'wushowhide' to hide the .Net update. Interesting that this also showed the Beta cumulative update. I hid that as well
Used the WU catalogue standalone file to get back to .3194
Cleaned up the disk, all good, DISM now working properly
Re-installed the .net update using the standalone

All seems fixed, for now!

DISM error 1726

BrianInEngland

Well-known member

My Computer

System One

antspants

Like a rolling drone.