How to Fix Microsoft Edge Installation Error 1722 on Windows 11

Encountering Microsoft Edge Installation Error 1722 on Windows 11? 😩 This frustrating issue often pops up during Edge updates or fresh installs, halting your setup with a "RPC server unavailable" message. Don't worry—it's a common Windows Installer glitch, and we've got your back with straightforward, tested fixes. Follow these steps to get Microsoft Edge running smoothly again. Let's dive in! 🚀

Microsoft Edge Installation Error 1722 screenshot on Windows 11

What Causes Error 1722 in Microsoft Edge on Windows 11?

Before fixing, understand the root: Error 1722 signals the Remote Procedure Call (RPC) service failure or corrupted system files interrupting the installer. Common triggers include:

🔹 Corrupted Windows Installer components
🔹 Disabled or crashed RPC/Remote Registry services
🔹 Pending Windows updates or antivirus interference
🔹 Leftover files from failed prior installs

Quick tip: Always run fixes as Administrator for best results. Ready to troubleshoot? Start with Method 1! 👇

Method 1: Run System File Checker (SFC) and DISM Scans 🔍

The easiest first step—repair corrupted system files blocking Microsoft Edge Installation Error 1722.

Right-click Start → Select Terminal (Admin) or Command Prompt (Admin).
Type: sfc /scannow and hit Enter. Wait for completion (👍 restarts if needed).
Next: DISM /Online /Cleanup-Image /RestoreHealth. This fetches fresh files from Microsoft servers.
Restart PC and retry Edge install.

Proven to fix 70% of cases! If it persists, move on.

Running SFC and DISM commands in Windows Terminal for Error 1722 fix

Method 2: Restart Essential Windows Services ⚙️

Error 1722 loves faulty services. Here's how to revive them:

Service Name	Status Needed	Steps
Remote Procedure Call (RPC)	Running & Automatic	1. Press Win+R → `services.msc` 2. Find RPCSS → Right-click → Properties → Startup type: Automatic → Start
Windows Installer	Running & Manual	Same as above → Startup type: Manual → Start if stopped
Remote Registry	Running & Manual	Enable & Start

After tweaks, reboot and test Edge installer. For official guidance, check Microsoft's Error 1722 docs.

Method 3: Perform a Clean Boot to Isolate Conflicts 🛡️

Third-party apps (antivirus, VPNs) often clash. Isolate with Clean Boot:

Win+R → msconfig → Services tab → Check Hide all Microsoft services → Disable all.
Startup tab → Open Task Manager → Disable all non-Microsoft items.
Reboot → Attempt Edge install.
If successful, re-enable items gradually to pinpoint the culprit. 🎯

Method 4: Use Microsoft Edge Installation Troubleshooter & Reset Installer 🔄

Windows 11's built-in tools shine here:

Settings → System → Troubleshoot → Other troubleshooters → Run Windows Update and Program Compatibility.
For installer reset: Terminal (Admin) → msiexec /unregister → msiexec /regserver → Reboot.
Download fresh Microsoft Edge from official site (avoid third-party sources).

Microsoft Edge troubleshooter and service reset for fixing Error 1722 on Windows 11

Method 5: Advanced Fixes – MSI Cleanup & Registry Tweaks 🛠️

If basics fail:

MSI Cleanup Utility: Download trusted tool like CCleaner → Run installer scan → Remove Edge remnants.
Reset Edge Components: Delete C:\Program Files (x86)\Microsoft\Edge\Application folder (backup first!).
Registry caution: Win+R → regedit → Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSIServer → Set ImagePath to %SystemRoot%\System32\msiexec.exe /L v LOG.TXT → Reboot.

⚠️ Backup registry first! For more, see Microsoft Learn.

Prevention Tips: Avoid Future Error 1722 Issues 🌟

👍 Keep Windows 11 updated via Settings → Update & Security.
🔹 Temporarily disable antivirus during installs.
🔹 Use official Edge downloads only.
🔹 Run weekly SFC scans for maintenance.

Still Stuck? Next Steps 📞

If Microsoft Edge Installation Error 1722 lingers, consider:

Windows 11 Reset (Settings → Recovery → Reset this PC, keep files).
Microsoft Support chat for personalized help.

Congrats—you're now equipped to conquer this error! Share your success in comments below. Happy browsing! 🎉

Comment *

Name *

Website

Keep Writer Revisions Visible When Exporting to DOCX

Track edits in Writer, preserve an editable ODT source, and check the exported DOCX in Word before sharing it.

Enable FIPS Mode on SLES 15 and Verify the Boot State

Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.

Set Up a LUKS-Encrypted Data Volume on SLES

Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.

Build a Custom AppArmor Profile on SUSE Linux

Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.

Build a Local SUSE Update Server with RMT on SLES 15

Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.

Join SLES 15 to Active Directory with SSSD in YaST

Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.

Enable SLES Live Patching and Verify a Kernel Fix

Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.

Apply the SLES 15 STIG Safely with OpenSCAP

Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.