VPN Error 633 on Windows 10/11? 5 Fixes That Work (2026)

 

Quick answer: VPN Error 633 on Windows means "The modem (or other connecting device) is already in use." In plain English, Windows thinks another program is already using the specific network port (usually port 1723) that your VPN needs to connect. The fastest fix is to restart the Windows "Remote Access Connection Manager" service, which clears the stuck port and lets your VPN connect instantly.

If you are staring at Error 633 and cannot get online, this guide walks through the 5 documented fixes based on Microsoft's network troubleshooting protocols, plus the permanent solution if your current VPN software is outdated.

What Exactly is Error 633?

When you connect to a VPN using the older PPTP protocol, Windows routes the connection through TCP Port 1723. Error 633 triggers when Windows detects that Port 1723 is either blocked by a firewall, stuck in a "zombie" state from a previous dropped connection, or actively being used by another background application.

Because the port is occupied, Windows refuses to let the VPN initialize the modem or network adapter, resulting in the Error 633 pop-up.

Fix 1: Restart the Remote Access Connection Manager (The 60-Second Fix)

This solves Error 633 in the vast majority of cases. The "RasMan" service handles all dial-up and VPN connections in Windows. Restarting it clears out any stuck "zombie" connections holding the port hostage.

1. Press the Windows Key + R on your keyboard to open the Run dialog.
2. Type services.msc and press Enter.
3. Scroll down the list until you find Remote Access Connection Manager.
4. Right-click it and select Restart (if it is stopped, click Start).
5. Do the exact same thing for the service right below it: Remote Access Auto Connection Manager.
6. Close the window and try connecting your VPN again.

Fix 2: Clear Port 1723 Using Command Prompt

If restarting the service didn't work, a background program might be actively hogging the port. We can find out exactly what it is and close it.

1. Click the Windows Start button, type cmd.
2. Right-click "Command Prompt" and select Run as administrator.
3. Type this exact command and press Enter: netstat -aon | findstr 1723
4. If any results show up, look at the very last number on the right (the PID).
5. Open Task Manager (Ctrl + Shift + Esc), go to the Details tab, and find the process with that matching PID number.
6. Right-click that process and select End Task.

Fix 3: Reinstall the WAN Miniport Adapters

Windows uses virtual network adapters called "WAN Miniports" to handle VPN traffic. If these drivers become corrupted, Error 633 is the standard result.

1. Right-click the Windows Start button and select Device Manager.
2. Expand the Network adapters section.
3. Look for anything named WAN Miniport (PPTP) or WAN Miniport (IKEv2).
4. Right-click them and select Uninstall device. (Do not check the box to delete the driver software, just uninstall).
5. At the top of the Device Manager window, click the Action menu and select Scan for hardware changes.
6. Windows will automatically reinstall fresh, uncorrupted versions of the adapters. Restart your PC and try again.

Fix 4: Switch Your VPN Protocol (The Permanent Fix)

Error 633 is almost exclusively a problem for older VPN protocols like PPTP or L2TP, which rely on easily blocked ports like 1723. Modern VPN protocols like WireGuard and OpenVPN use different ports and are vastly more stable on Windows 10 and 11.

If you are manually configuring a work VPN using PPTP, ask your IT department if they support IKEv2 or WireGuard instead.

If you are using a personal VPN and constantly fighting Error 633, it is a sign that the software is outdated. Premium providers like NordVPN and Surfshark use modern, lightweight protocols (NordLynx and WireGuard) that bypass these legacy Windows port conflicts entirely. Switching to a modern provider often eliminates Error 633 permanently without needing to touch Windows services.

Fix 5: Allow the VPN Through Windows Defender Firewall

Sometimes Windows Defender aggressively blocks the VPN executable from opening the necessary port.

1. Press the Windows Key, type Allow an app through Windows Firewall, and press Enter.
2. Click the Change settings button at the top right (requires admin rights).
3. Scroll down and find your VPN application in the list.
4. Ensure both the Private and Public checkboxes next to your VPN are checked.
5. If your VPN isn't on the list, click Allow another app, browse to your VPN's installation folder, and add the .exe file.
6. Click OK and restart your computer.

FAQ

Is Error 633 a problem with my internet?

No. Error 633 is strictly an internal Windows configuration issue. Your router, modem, and internet service provider are fine. The problem is entirely inside your PC's network services.

Does this fix work on Windows 11?

Yes. The underlying network architecture for VPNs in Windows 11 is identical to Windows 10. All five fixes above apply perfectly to Windows 11 machines.

Why does the error happen after my PC wakes from sleep?

When a Windows PC goes to sleep, it sometimes fails to properly disconnect the active VPN session, leaving the port "stuck" in an open state. When you wake the PC and try to connect again, Windows throws Error 633 because the port never actually closed. Fix #1 (Restarting RasMan) is the standard solution for this.

Final Verdict

VPN Error 633 is a frustrating but easily solvable Windows port conflict. In 90% of cases, simply restarting the Remote Access Connection Manager service in Windows clears the stuck port and allows your connection to proceed. If the error keeps returning every time you boot your PC, switching to a modern VPN provider that uses the WireGuard protocol will bypass legacy port issues entirely.

This guide is based on Microsoft Windows network troubleshooting documentation and standard VPN protocol specifications. Facts are checked and updated as Windows updates change network behaviors.