FixTechUSA
🔨 Tested & Verified Fix Guide · 2026
VPN fails to connect, shows error, or connects but breaks internet? Here are 9 tested fixes — from firewall rules to protocol changes — for every type of VPN failure.
💬 VPN failures in Windows 11 fall into 3 patterns: won’t connect at all, connects then drops, or connects but kills internet. Each has a different root cause. In my experience, 80% of VPN connection failures are caused by just two things: Windows Firewall blocking the VPN client, and IPsec services being stopped. Both are fixed in under 3 minutes without reinstalling anything.
— Bharat Choudhary, FixTechUSA · Windows Networking Specialist
❌ Common VPN Errors in Windows 11:
VPN connection failed — Error 789, 800, 868, or connection timeout
VPN won’t connect · Connects then disconnects · Connected but no internet
VPN Not Working
VPN not connecting in Windows 11 covers three scenarios: the VPN refuses to connect (firewall, services, wrong protocol), connects but immediately drops (driver or MTU issue), or connects but breaks internet (DNS or routing issue). These 9 fixes address every scenario — work through them in order and you will identify your exact cause.
🔎 Quick Diagnosis — Identify Your VPN Failure Type
✅ VPN refuses to connect at all?Firewall blocking. Fix 1 (allow through firewall) + Fix 4 (enable services).
❌ Connects but drops after few seconds?Protocol or MTU issue. Fix 2 (change protocol) solves most cases.
✅ Error 789 or L2TP error?NAT traversal fix needed. Fix 6 (registry key) is your specific solution.
❌ Connects but internet stops working?DNS routing conflict. Fix 3 (flush DNS) + check VPN split-tunnel settings.
📋 Table of Contents
🔍 Why Does VPN Fail in Windows 11?
🛡
Firewall blocking — Windows Firewall blocking VPN ports or client
⚙
Services stopped — IPsec or IKE services not running
🔄
Wrong protocol — VPN protocol incompatible with current network
🔒
Antivirus block — Security software intercepting VPN traffic
🔧
NAT traversal — L2TP behind NAT router requiring registry fix
🖥
Driver conflict — Network driver conflicting with VPN adapter
🔧 9 Fixes — Start From #1
1
Allow VPN Through Windows Firewall — Most Common Fix
⏱ 2 min | 🟢 Easy | Fixes 50% of VPN failures
Windows Firewall is the most common reason VPN fails in Windows 11. It blocks VPN client connections and VPN-specific ports without any notification.
Allow VPN client through Firewall:
- Press
Win + I→ Privacy & Security → Windows Security - Click Firewall & network protection
- Click Allow an app through firewall
- Find your VPN client (NordVPN, ExpressVPN, ProtonVPN etc.)
- Check both Private and Public checkboxes
- If not listed: click Allow another app → browse to VPN executable → Add
- Click OK → try VPN again
✅Also temporarily disable Windows Firewall completely to test: if VPN connects with firewall off, the firewall is definitely the issue and you need to add the proper rule.
2
Change VPN Protocol
⏱ 2 min | 🟢 Easy | Fixes protocol-specific failures
Different VPN protocols work better on different networks. Some ISPs or networks block specific protocols. Switching often instantly resolves connection failures.
In your VPN client app settings:
- Try IKEv2 — most stable for Windows 11, fast and reliable
- Try OpenVPN TCP — most reliable for bypassing ISP restrictions
- Try L2TP/IPsec — works on almost all networks
- Try WireGuard — fastest if supported by your VPN provider
For Windows built-in VPN:
- Press
Win + I→ Network & Internet → VPN - Click your VPN connection → Advanced options
- Change VPN type from Automatic to IKEv2 first, then try others
📌If on a hotel, school, or corporate network — try OpenVPN TCP port 443 which is nearly impossible to block as it uses the same port as HTTPS.
→ Related Fix
If VPN connects but DNS stops working:
DNS Server Not Responding Windows 11 — 10 Fixes
3
Flush DNS and Reset TCP/IP Stack
⏱ 3 min | 🟡 Medium | Fixes DNS and routing conflicts
Corrupted DNS cache and TCP/IP settings cause VPN authentication failures and post-connection internet breakage. A reset clears all conflicts.
// Run all in admin Command Prompt
ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew
netsh int ip reset
netsh winsock reset
Restart PC → try VPN connection again.
✅This is especially effective when VPN connects successfully but internet stops working — the DNS cache from before the VPN conflicts with VPN DNS servers.
4
Enable Required IPsec and VPN Services
⏱ 2 min | 🟢 Easy | Critical for L2TP and IKEv2 VPN
Windows VPN (especially L2TP and IKEv2) requires specific Windows services to be running. If they are stopped or set to Manual, VPN connection fails silently.
- Press
Win + R→ typeservices.msc→ Enter - Find and set these services to Automatic and Started:
- IKE and AuthIP IPsec Keying Modules → Automatic + Start
- IPsec Policy Agent → Automatic + Start
- Remote Access Connection Manager → Manual + Start
- Routing and Remote Access → Manual (start only when needed)
- For each: double-click → set Startup type → click Start → OK
- Try VPN connection again
✅This fix is essential for Windows built-in VPN using L2TP/IPsec or IKEv2 protocols. Third-party VPN clients (NordVPN, ExpressVPN) install their own services but may still need IPsec Policy Agent.
5
Disable Antivirus and Third-Party Firewall
⏱ 2 min | 🟢 Easy | Test for security software conflict
Antivirus programs like Avast, Kaspersky, McAfee, and Norton often include firewalls that intercept VPN traffic without notification.
- Temporarily disable your antivirus (right-click system tray icon → Disable)
- Try VPN connection
- If it connects — antivirus is blocking it
- Re-enable antivirus → add VPN client to antivirus exclusion/whitelist
⚠️Only disable antivirus for testing (maximum 5 minutes). Re-enable immediately after testing. Add VPN to exclusions rather than keeping antivirus off.
6
Fix VPN Error 789 — L2TP Registry Fix
⏱ 3 min | 🟡 Medium | Specific fix for Error 789
Error 789 is a specific L2TP/IPsec failure caused by NAT traversal issues. Windows requires a registry key to allow L2TP VPN behind a NAT router.
// Run in admin Command Prompt to add registry fix
reg add “HKLM\SYSTEM\CurrentControlSet\Services\PolicyAgent” /v “AssumeUDPEncapsulationContextOnSendRule” /t REG_DWORD /d 2 /f
Restart PC after running this command → try L2TP VPN again.
✅This registry fix is the official Microsoft solution for Error 789 and Error 809. It resolves L2TP VPN failures behind home routers using NAT.
→ Related Fix
If VPN causes internet to show Limited Access after connecting:
Windows 11 Limited Internet Access — 8 Fixes
7
Reinstall VPN Client Completely
⏱ 10 min | 🟡 Medium | Fixes corrupted VPN installation
Corrupted VPN client installations cause persistent connection failures that no setting change can fix. A clean reinstall resolves all installation-level issues.
- Press
Win + I→ Apps → find your VPN app → Uninstall - After uninstall, restart PC
- Press
Win + R→ typencpa.cpl→ confirm no leftover VPN adapter remains - Download latest version from your VPN provider’s official website
- Install fresh → login → test connection
📌Before reinstalling, check your VPN provider’s website for Windows 11-specific installation notes — some providers have special steps for Windows 11 compatibility.
8
Update Network Adapter Driver
⏱ 5 min | 🟡 Medium
Outdated network drivers can conflict with VPN virtual adapter creation, causing connection failures especially for OpenVPN and WireGuard.
- Press
Win + X→ Device Manager → Network Adapters - Right-click your main network adapter → Update driver
- If no update available → Uninstall → restart → Windows reinstalls
- Also check for any VPN adapter entries with yellow warning icons → right-click → Uninstall to clean up
9
Full Network Reset — Last Resort
⏱ 5 min | 🟡 Medium
Removes all VPN adapters, network configurations, and resets all networking to Windows 11 factory defaults. Start completely fresh.
- Press
Win + I→ Network & Internet → Advanced network settings - Click Network reset → Reset now → PC restarts in 5 minutes
- After restart → reinstall VPN client → connect
⚠️Removes saved WiFi passwords. VPN settings also reset. Personal files completely safe.
| # | Fix | Level | Time | Best For |
|---|---|---|---|---|
| 1 | Allow VPN Through Firewall | Easy | 2 min | VPN blocked — most common cause |
| 2 | Change VPN Protocol | Easy | 2 min | Protocol blocked by ISP or network |
| 3 | Flush DNS + Reset TCP/IP | Medium | 3 min | DNS/routing conflicts |
| 4 | Enable IPsec Services | Easy | 2 min | L2TP or IKEv2 failures |
| 5 | Disable Antivirus | Easy | 2 min | Security software interference |
| 6 | Fix Error 789 Registry | Medium | 3 min | L2TP Error 789 behind NAT |
| 7 | Reinstall VPN Client | Medium | 10 min | Corrupted VPN installation |
| 8 | Update Network Driver | Medium | 5 min | Driver conflicting with VPN adapter |
| 9 | Full Network Reset | Medium | 5 min | Nothing else worked |
❓ Frequently Asked Questions
Why is my VPN not connecting in Windows 11?
VPN not connecting is most commonly caused by Windows Firewall blocking the VPN client or ports, or required IPsec services being stopped. Allow the VPN through firewall (Fix 1) and restart IPsec services in Windows Services (Fix 4) — these two together fix 70% of VPN connection failures.
How do I fix VPN Error 789 in Windows 11?
Error 789 is an L2TP NAT traversal issue. Fix it by running this command in admin Command Prompt: reg add “HKLM\SYSTEM\CurrentControlSet\Services\PolicyAgent” /v “AssumeUDPEncapsulationContextOnSendRule” /t REG_DWORD /d 2 /f then restart your PC. This is the official Microsoft fix for this specific error.
VPN connects but internet stops working in Windows 11 — why?
VPN connected but no internet usually means the VPN is routing all traffic through the tunnel but DNS is failing. Flush DNS with ipconfig /flushdns. If your VPN client has a split-tunnel option, enable it to only route VPN traffic through the tunnel while keeping regular internet on your normal connection.
Can Windows Defender block VPN connections?
Yes. Windows Defender Firewall blocks VPN clients and VPN-specific ports. Go to Windows Security, Firewall and network protection, Allow an app through firewall, find your VPN client and check both Private and Public. This single change resolves most VPN firewall blocking issues.
Which VPN protocol works best in Windows 11 in 2026?
IKEv2 is the most stable VPN protocol for Windows 11, offering excellent speed and automatic reconnection. WireGuard is the fastest if your VPN provider supports it. OpenVPN TCP port 443 is the most reliable for bypassing network restrictions. L2TP/IPsec works everywhere but is slower than the other options.
→ Related FixIf VPN causes “Can’t Connect to This Network” error:Windows 11 Can’t Connect to This Network — 9 Fixes
→ Complete GuideAll Windows 11 network problems:Windows 11 Internet Problems — Complete Fix Guide
✅ Bottom Line
VPN not connecting in Windows 11 is almost always caused by Windows Firewall blocking the client or IPsec services being stopped. Apply Fix 1 (allow through firewall) and Fix 4 (enable IPsec services) — these two together resolve most VPN failures in under 5 minutes. For L2TP Error 789, the Fix 6 registry key is the specific Microsoft-recommended solution. You do not need to change your ISP or buy a new router.