How to Fix the Error 1722 the RPC Server is unavailable

Error 1722: The RPC Server is Unavailable generally means that your computer is trying to send a command to another service (either on your own computer or a remote one), but that service isn’t listening or is blocked.

This most commonly happens during Windows Updates, Printing, or Active Directory tasks.

Here is how to fix it, ordered from the most common solution to the most advanced.

How to Fix the Error 1722

1. The Service Fix (Most Common)

The service responsible for handling these requests may be stopped or disabled.

1. Press Windows Key + R, type services.msc, and hit Enter.

2. Scroll down and find Remote Procedure Call (RPC).

   • Status: Must be Running.

   • Startup Type: Must be Automatic.

   • Note: If these are greyed out and you can’t change them, that is normal for the main RPC service.

3. Find DCOM Server Process Launcher. Ensure it is Running and set to Automatic.

4. Find RPC Endpoint Mapper. Ensure it is Running and set to Automatic.

5. Crucial: If you were trying to print when this happened, find the Print Spooler service. Right-click it and select Restart..

Also Read : How To Fix Roomba Error 15

2. The Firewall Fix (Blocked Connections)

If the services are running, your Firewall might be blocking the communication.

1. Press the Start button and type “Allow an app through Windows Firewall”. Click the result.

2. Click the Change settings button (you may need Admin rights).

3. Scroll down the list and ensure these boxes are checked:

   • Remote Service Management

   • File and Printer Sharing (especially if this is a printing error)

4. Click OK and try your task again.

3. Enable Network Discovery

If your computer thinks it is on a “Public” network, it will block RPC to protect you.

1. Go to Settings > Network & Internet.

2. Check your connection properties (Ethernet or Wi-Fi).

3. Ensure the Network Profile is set to Private (not Public).

4. Go back to Network & Internet > Advanced network settings > Advanced sharing settings.

5. Turn On “Network discovery” and “File and printer sharing”.

4. The Registry Fix (Advanced)

If the service is truly stuck, you may need to force a refresh via the registry/command line.

1. Open Command Prompt as Administrator.

2. Type the following command and press Enter: sc config Rpcss start= auto

3. Then type this to refresh the DNS (often resolves connectivity confusion): ipconfig /flushdns

4. Restart your computer immediately after.

Context Check:

• If this happened while printing: The issue is almost certainly the Print Spooler service (Step 1) or the printer’s IP address changing.

• If this happened during a Windows Update: It is likely a temporary glitch; a restart + Step 3 usually fixes it.