VPN Not Working on PC: 10 Causes and Fixes

In short: VPN not working on your Windows PC is most commonly caused by antivirus or Windows Defender blocking the client, incorrect Windows Firewall rules, a broken TAP/TUN adapter, DNS issues, or a corrupted VPN profile. In most cases, adding the VPN client to antivirus exclusions, running ipconfig /flushdns, and reinstalling the TAP adapter restores the connection.

Before diving into diagnostics, confirm your internet works without VPN: how to verify VPN is working — ipleak.net will show whether your real IP is exposed. If internet is also broken without VPN, the issue is your ISP or router, not the VPN client.

How to Diagnose the Problem: 5-Minute Checklist

Five quick questions narrow down the root cause within minutes and save you from testing the wrong things.

1. Does internet work without VPN? Open Command Prompt and run ping 8.8.8.8. No reply — the problem is your base connection, not VPN.
2. Does VPN show "Connected" or an error? "Connected but no internet" and "can't connect at all" are different problems with different solutions.
3. Is the problem on all sites or just some? If some sites work — likely a DNS or split tunnelling issue.
4. Is the problem in one specific app or in the browser too? Only in one app — likely an antivirus conflict for that specific process.
5. Did this start after a Windows, antivirus, or VPN client update? Updates often reset the TAP adapter or change firewall rules.

Symptom	Likely Cause	Section
VPN connects but internet is completely broken	Firewall or routing	Causes 2, 9
VPN won't connect at all (error)	Antivirus, service, profile	Causes 1, 4, 10
VPN connected but very slow	Overloaded server or MTU	Cause 6
Connection drops after one minute	TAP adapter, timeout	Cause 3
VPN worked, then broke after a Windows update	Service or TAP driver	Causes 3, 4
Specific sites or apps don't work through VPN	Split tunnelling, DNS	Causes 5, 9

Cause 1 — Antivirus or Windows Defender Blocking VPN

Antivirus software is the most frequent reason VPN stops working on a Windows PC: security tools intercept the network stack and may flag VPN clients as suspicious software altering network settings.

Why Antivirus Interferes with VPN

Antivirus operates at the network driver level and inspects all outgoing connections. When a VPN client creates an encrypted tunnel, the antivirus may block it as atypical network behaviour. The most common offenders are Kaspersky Internet Security, ESET NOD32, Bitdefender, and Windows Defender in "Network Protection" mode. Symptoms: VPN shows a connection error, or it connects but internet doesn't work.

Fastest test: temporarily disable the antivirus and try connecting to VPN. If it works — the cause is confirmed. Don't leave the antivirus off — add the VPN client to its exclusions.

How to Add VPN to Antivirus Exclusions

• Windows Defender / Windows Security: Windows Security → Virus & threat protection → Manage settings → Exclusions → Add or remove exclusions → add the VPN client folder.
• Kaspersky: Settings → General → Exclusions → Manage exclusions → add the VPN executable.
• ESET NOD32: Setup → Advanced Setup → Exclusions → add the VPN client .exe file.
• Bitdefender: Protection → Online Threat Prevention → Exceptions → add the VPN client path.

Cause 2 — Windows Firewall Blocking VPN Ports

Windows Firewall may block the UDP or TCP ports used by your VPN protocol — preventing the tunnel from forming, or letting VPN show "Connected" while packets can't actually pass through.

Which Ports Each Protocol Needs

Protocol	Port and Transport
WireGuard	UDP 51820 (or custom — depends on your provider)
OpenVPN	UDP 1194 or TCP 443
IKEv2/IPsec	UDP 500, UDP 4500, ESP protocol (50)
L2TP/IPsec	UDP 1701, UDP 500, UDP 4500

How to Create an Allow Rule in Windows Firewall

1. Start → "Windows Defender Firewall with Advanced Security" → Inbound Rules → New Rule.
2. Select "Port" → UDP → enter the required port → "Allow the connection" → apply to all profiles → name the rule.
3. For quick diagnostics: Firewall → Turn Windows Defender Firewall on or off → select "Turn off". If VPN works — create an allow rule and re-enable the firewall.

Cause 3 — TAP/TUN Adapter Issues

The TAP/TUN adapter is a virtual network device Windows installs for VPN tunnelling. This Windows-specific cause is overlooked by most troubleshooting articles, yet it drives a significant share of PC-only connection failures.

What the TAP Adapter Does and Why VPN Needs It

The TAP adapter is a network-layer driver the VPN client installs to route traffic through the encrypted tunnel. OpenVPN uses TAP-Windows6; WireGuard uses WinTUN. After Windows updates, the adapter can stop initialising: VPN shows "Connected" but no traffic flows through the tunnel.

Check it: Device Manager → Network Adapters → look for "TAP-Windows Adapter" or "WireGuard Tunnel". A yellow exclamation mark means the driver is broken. A greyed-out icon with an X means the adapter is disabled.

How to Reinstall the TAP Adapter via Device Manager

1. Device Manager → Network Adapters → right-click the TAP adapter → Uninstall device → check "Delete the driver software for this device".
2. Restart your PC.
3. Run the VPN client installer again — it automatically reinstalls the TAP adapter. Alternatively, download TAP-Windows6 from the official OpenVPN website.
4. Check Device Manager: the adapter should appear without any error icons.

Windows KB updates sometimes overwrite TAP drivers — reinstalling usually resolves it in under 5 minutes. See also Microsoft VPN troubleshooting documentation.

Cause 4 — VPN Service Not Running

VPN clients on Windows depend on several system services. If any of them is stopped or disabled, the VPN won't connect — even if the client is running and your credentials are correct.

Which Windows Services VPN Requires

• IKEv2 / L2TP: IKE and AuthIP IPsec Keying Modules, IPsec Policy Agent.
• OpenVPN: OpenVPN Interactive Service (if installed as a system service).
• WireGuard: registers its own service when a tunnel is installed.
• All protocols: Base Filtering Engine (BFE) — if disabled, no VPN will work at all.

How to Start a Service and Set Auto-start

1. Win + R → services.msc → find the required service → right-click → Properties → Startup type: "Automatic" → click "Start".
2. PowerShell (as administrator): Get-Service -Name IKEext | Start-Service
3. If Base Filtering Engine is disabled: sc config BFE start= auto, then net start BFE as administrator (requires a reboot).

Cause 5 — DNS Cache or DNS Server Problems

A stale DNS cache is one of the fastest fixes when VPN is not working on Windows 10 or 11: the ipconfig /flushdns command takes 10 seconds and often fully restores network connectivity.

ipconfig /flushdns — First Diagnostic Step

1. Win + R → type cmd → right-click and "Run as administrator".
2. Run: ipconfig /flushdns
3. Output: "Successfully flushed the DNS Resolver Cache."
4. Also useful: ipconfig /release → ipconfig /renew — renews the IP address from your ISP.
5. Then restart the VPN client.

How to Set a Reliable Public DNS

If the problem recurs, your ISP's DNS may be unreliable. Change it: Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings → right-click the active adapter → Properties → IPv4 → "Use the following DNS server addresses": preferred 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare), alternate 8.8.4.4 or 1.0.0.1. To check for DNS leaks through your VPN tunnel, see the DNS leak test guide.

Cause 6 — MTU Mismatch

An MTU mismatch is a technically obscure but reliably reproducible cause: small sites load fine while heavy pages and video freeze halfway — because large packets don't fit the tunnel without fragmentation.

What MTU Is and Why It Breaks VPN

MTU (Maximum Transmission Unit) is the maximum packet size in bytes. Standard Ethernet MTU is 1500 bytes. A VPN tunnel adds encryption headers, reducing the usable MTU inside the tunnel: typically 1380–1420 bytes for WireGuard, 1420–1450 for OpenVPN. With an incorrect MTU, large packets (HTTP responses, video streams) fragment or get dropped — the page freezes mid-load even though the server connection is alive.

How to Find the Optimal MTU and Apply It

Diagnose with ping (Command Prompt as administrator):

ping -f -l 1400 8.8.8.8

The -f flag disables fragmentation, -l 1400 sets the packet size. If you get "Packet needs to be fragmented but DF set" — reduce the value by 10 until you get a successful reply. Apply the optimal value to the TAP adapter:

netsh interface ipv4 set subinterface "TAP-Windows Adapter V9" mtu=1400 store=persistent

For WireGuard: add MTU = 1380 to the [Interface] section of your tunnel configuration file.

Cause 7 — Wrong VPN Protocol

Different VPN protocols behave differently in corporate, public Wi-Fi, and home networks. Switching the protocol is the second most effective quick test after checking the antivirus.

WireGuard, OpenVPN, IKEv2 — Differences for Windows

• WireGuard: modern, minimal codebase, UDP only, fastest. First choice for Windows 10 and 11.
• OpenVPN TCP (port 443): passes through most corporate firewalls — port 443 is never blocked because HTTPS uses it.
• IKEv2/IPsec: built into Windows, works well in corporate environments, but depends on IPsec services (Cause 4).

A detailed protocol comparison is in the guide on VPN protocols: WireGuard, OpenVPN, IKEv2.

How to Switch Protocol in LiMP VPN

LiMP VPN Settings → "Protocol" → select WireGuard / OpenVPN / IKEv2. If the current protocol is blocked by a corporate firewall, try OpenVPN TCP 443.

Cause 8 — System Clock Out of Sync

A system clock more than 5 minutes off real time breaks TLS handshakes: the VPN client rejects the server certificate as expired. Rare, but instantly verifiable.

Symptoms: "certificate expired", "handshake failed", "TLS error". Check the date and time in the bottom-right corner of Windows.

• Quick fix: right-click the clock → "Adjust date/time" → "Sync now".
• From Command Prompt (as administrator): w32tm /resync /force

Cause 9 — Routing Conflict

Most VPN clients default to a "full tunnel" routing rule: all internet traffic routes through VPN. If the VPN server is unavailable or unstable, your entire internet goes down while the VPN is connected.

Why Routing Can Break Internet with VPN Active

Diagnose with route print in Command Prompt. Find a line with address 0.0.0.0 on the TAP interface — that's the full-tunnel route. If internet disappears the moment VPN connects but works fine without VPN, this routing rule is the cause.

Split Tunnelling as the Solution

Split tunnelling routes only the required traffic through VPN and leaves the rest direct. In LiMP VPN: Settings → "Split Tunnelling" → add apps or sites that should work outside the VPN tunnel. Detailed setup instructions in the split tunnelling guide.

Cause 10 — Corrupted VPN Profile

A corrupted profile is a frequent cause of sudden VPN failure: the connection worked, nothing changed, but VPN won't connect without any obvious reason.

Recovery steps:

1. Delete the current VPN profile: Windows Settings → Network & Internet → VPN → select the profile → Remove.
2. Restart your PC.
3. Recreate the profile or import a configuration file (.ovpn / .conf) from your LiMP VPN account.
4. For OpenVPN: delete the %APPDATA%\OpenVPN Connect folder and reinstall the client from the official website.

Universal Checklist — What to Do First

If VPN is not working on your Windows 10 or Windows 11 PC, go through this list in order. Most issues resolve by step 4.

1. Restart your PC and router — fixes up to 30% of issues without further action.
2. Temporarily disable antivirus → test VPN → if it works, add the VPN client to exclusions.
3. Run ipconfig /flushdns from an administrator command prompt.
4. Open Device Manager → Network Adapters → check for yellow warning icons on the TAP adapter.
5. Open services.msc → confirm IKE and AuthIP IPsec Keying Modules and Base Filtering Engine are running.
6. Switch the VPN protocol in client settings (try WireGuard → OpenVPN → IKEv2).
7. Sync your system clock: right-click clock → "Adjust date/time" → "Sync now".
8. MTU diagnosis: ping -f -l 1400 8.8.8.8 — if fragmentation, lower MTU on the TAP adapter.
9. Delete the VPN profile and recreate it (Settings → Network & Internet → VPN).
10. Confirm internet works without VPN: ping 8.8.8.8 without VPN should return replies.

What to Do If Nothing Works

If all ten steps are done and VPN still won't work on your PC, the issue may be server-side or specific to your network environment.

• Check your VPN provider's server status in the app or on their official website.
• Try a different VPN server — the current one may be temporarily overloaded or unreachable.
• Verify the tunnel is working on ipleak.net: how to verify VPN is working — it should show the VPN server's IP, not your real one.
• Export client logs (LiMP VPN: Settings → Diagnostics → Export Logs) and contact support with a description of the steps you've already taken.

Explore the full feature set of LiMP VPN on the features page, or choose a plan on the pricing page.