If you see “Error 1726: The remote procedure call failed” while running DISM in Windows 10, it usually means the Windows Update service or the DISM process couldn’t communicate with a required system component. The fix is to ensure the relevant Windows services are running, repair the system files, and then retry the DISM command with proper admin rights.
What Is DISM and Why Does Error 1726 Happen?
DISM (Deployment Imaging Service and Management) is a built-in Windows 10 tool used to repair system image files, prepare Windows images, and fix component store corruption. When you run DISM /Online /Cleanup-Image /RestoreHealth, it contacts the Windows Update service to download healthy files. Error 1726 occurs when that remote procedure call (RPC) between DISM and the Windows Update service fails—often because the service is stopped, disabled, or its dependencies are broken.
Common triggers include:
- Windows Update service (wuauserv) is set to Disabled or Manual but not started.
- Background Intelligent Transfer Service (BITS) or Cryptographic Services are stopped.
- System file corruption in the RPC subsystem itself.
- Third-party security software blocking the RPC ports.
- Running DISM without administrator privileges.
Before You Start: Check Your Windows Version and Permissions
DISM commands differ slightly between Windows 10 versions. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or Windows PowerShell (Admin)). The exact DISM syntax is the same for all recent Windows 10 builds, but the underlying servicing stack may need updating first.
Make sure you have a stable internet connection. If DISM can’t reach Windows Update, it will fail with a different error (usually 0x800f0906), but 1726 specifically points to the RPC layer. Also, temporarily disable any third-party firewall or antivirus that might be interfering, but re-enable it after testing.
Step-by-Step Fix for Error 1726
Follow these steps in order. Most users resolve the error with the first two steps.
- Start the required services manually. Open an elevated Command Prompt and run these commands one by one:
net start wuauservnet start bitsnet start cryptsvcnet start msiserver
If any service fails to start, note the error and continue. - Set services to Automatic and start them. Use
sc config wuauserv start= autoand similarly forbits,cryptsvc, andmsiserver. Then runnet startfor each again. - Run the System File Checker (SFC). Type
sfc /scannowand wait for it to complete. This repairs corrupted system files that might be breaking RPC. - Retry DISM. Now run the original command:
DISM /Online /Cleanup-Image /RestoreHealth. If it still fails with 1726, proceed to step 5. - Check the RPC service itself. Open Services (Win+R, type
services.msc), find “Remote Procedure Call (RPC)”, ensure it’s running and set to Automatic. Also check “DCOM Server Process Launcher” and “RPC Endpoint Mapper”. - Boot into Safe Mode with Networking. Restart, hold Shift and click Restart, then choose Troubleshoot > Advanced Options > Startup Settings > Restart, then press 5. In Safe Mode, run the DISM command again. This eliminates third-party driver/software interference.
- Use the Windows Update Troubleshooter. Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. Run it and restart, then try DISM again.
If DISM Still Fails: Use an Alternate Source
When the online repair path is broken, you can point DISM to a local Windows image. You’ll need a Windows 10 installation USB or ISO. Mount the ISO (right-click > Mount) and note the drive letter (e.g., E:). Then run:
DISM /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\install.wim /LimitAccess
If you only have an install.esd file, you need to convert it first—that’s more advanced. A simpler workaround is to use the Windows Media Creation Tool to create a bootable USB, then boot from it and choose “Repair your computer” > “Troubleshoot” > “Command Prompt” and run DISM from there against the offline Windows installation (using the /Image: parameter). This bypasses the running system’s RPC issues entirely.
Why Does This Happen After a Windows Update?
Error 1726 often appears after a failed or partially installed Windows Update. The servicing stack (the component that installs updates) may be corrupted, which breaks the RPC connection that DISM relies on. In such cases, the fix is to first install the latest servicing stack update (SSU) manually from Microsoft Update Catalog, then retry DISM. Search for “Windows 10 servicing stack update” for your build number (e.g., 1903, 20H2, 21H2) and install the .msu file. After that, the RPC call usually succeeds.
Another common scenario is after using third-party “debloater” scripts that disable Windows Update services. Those scripts often set wuauserv to Disabled, which directly causes 1726. Reverting those services to Automatic is the permanent fix.
Frequently Asked Questions
What does “remote procedure call failed” mean in plain English?
It means DISM tried to ask another Windows component (like Windows Update) to do something, but the two couldn’t communicate. It’s like calling a phone number that’s disconnected—the request never gets through.
Can I run DISM without admin rights?
No. DISM requires elevated privileges. If you run it in a normal Command Prompt, you’ll get “You must be an administrator running a console session” or similar. Always right-click and select “Run as administrator.”
How long does DISM take to finish?
Typically between 10 and 30 minutes, but it can take over an hour on older hard drives. It may appear stuck at 20% or 40%—that’s normal. Don’t close the window; let it complete.
Is error 1726 the same as 0x800f081f?
No. 0x800f081f means DISM couldn’t find the source files, while 1726 is an RPC communication failure. The fix for 0x800f081f is to specify a valid /Source path, not to restart services.
Will I lose my files by running DISM?
No. DISM only repairs Windows system files. It does not touch your personal documents, photos, or installed programs. However, it’s always wise to back up important data before any system repair.
What if none of these steps work?
If DISM still fails with 1726 after trying all steps, the last resort is to perform a Windows 10 in-place repair upgrade. Download the Media Creation Tool, run it, and choose “Upgrade this PC now.” This reinstalls Windows while keeping your files and apps, and it often fixes deep corruption that DISM can’t.
Preventing Future DISM Errors
To avoid error 1726 in the future:
- Never disable Windows Update services, even to speed up your PC.
- Keep your system clock and date correct—RPC authentication can fail if the time is off.
- Run
sfc /scannowmonthly as a maintenance habit. - Use only trusted system cleanup tools; some “optimizers” break service dependencies.
- If you use a VPN or proxy, temporarily disable it when running DISM, as it can interfere with the RPC endpoint.
Error 1726 is frustrating but almost always fixable within 20 minutes. The key is to systematically restart services, verify RPC dependencies, and if needed, use a local source or safe mode. Once DISM completes successfully, your Windows 10 system image will be healthy, and future updates should install without issues.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Hogwarts Legacy Microsoft Visual C Runtime Error Fix
- Set Up UPI Payments Through WhatsApp
- Pair Oppo Enco Earbuds with Android, iPhone & Windows
- Fix Administrator Account Disabled Error in Windows 11
- How to Play Kodi on Smart TV from PC
- Factory Reset on Samsung Galaxy: What It Erases