How to Fix WiFi Not Working After Connecting a VPN on Windows 11: Adapter, DNS, and Route Fixes

You connect your VPN, and your internet dies. WiFi still shows as connected, but nothing loads. Websites time out, DNS fails, or your speed drops to nearly zero. This is one of the most frustrating Windows 11 networking problems — and it has several distinct causes, each with a specific fix. Work through these in order.

Why Does a VPN Break WiFi on Windows 11?

A VPN doesn’t just encrypt your traffic — it installs a virtual network adapter, modifies your routing table, and sometimes overwrites your DNS settings. Any one of these changes can go wrong:

• Routing conflicts: The VPN adapter claims a metric lower than your WiFi adapter, so all traffic tries to flow through the VPN tunnel even if the tunnel isn’t fully established.
• DNS leakage and overrides: The VPN client pushes its own DNS servers and Windows routes all DNS queries through the tunnel. If the tunnel drops, DNS resolution fails entirely.
• TAP/TUN driver issues: Legacy OpenVPN-based clients install a TAP virtual adapter. If the driver is outdated or corrupted, the adapter can block traffic rather than route it.
• IPv6 leaking outside the tunnel: VPN clients that only tunnel IPv4 leave IPv6 traffic unprotected — or worse, cause IPv6 to stop working entirely, breaking dual-stack sites.
• Windows Firewall blocks: After a Windows update, the firewall may reclassify the VPN adapter as a public network and block traffic from passing through.

Fix 1: Reset the Network Stack

The fastest first step is a full network stack reset. Open Command Prompt as Administrator (right-click the Start menu → Terminal (Admin)) and run each command in order:

netsh winsock reset
netsh interface ipv4 reset
netsh interface ipv6 reset
ipconfig /release
ipconfig /flushdns
ipconfig /renew

Then restart your PC. This clears corrupt Winsock entries, resets TCP/IP stack state, and forces Windows to re-acquire a fresh DHCP lease. A Windows update or VPN installation can leave the stack in a broken intermediate state — this resets it cleanly. After the reboot, reconnect your VPN and test internet access again.

Fix 2: Change the VPN Adapter Interface Metric

Windows uses interface metrics to decide which adapter handles outbound traffic. Lower metric = higher priority. When a VPN connects, it often assigns itself a very low metric (sometimes 1), which means all traffic routes through the VPN tunnel even if your WiFi is also active. If the tunnel has a problem, nothing gets through.

To fix this:

1. Open Settings → Network & Internet → Advanced network settings → More network adapter options.
2. Right-click your WiFi adapter → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → Advanced.
3. Uncheck “Automatic metric” and set the interface metric to 10.
4. Do the same for your VPN adapter, but set its metric to 100.

This tells Windows to prefer your physical WiFi connection for routing while still sending VPN-destined traffic through the tunnel. Reconnect your VPN after making this change.

Fix 3: Disable “Use Default Gateway on Remote Network”

If you’re using the built-in Windows VPN client (not a third-party app), there’s a setting that routes all your internet traffic through the corporate or remote VPN gateway. Disabling it enables split tunneling, keeping VPN traffic in the tunnel and regular browsing on your local connection.

1. Go to Settings → Network & Internet → VPN.
2. Click your VPN connection → Advanced options → Edit.
3. Under connection properties, click More adapter options.
4. Right-click the VPN adapter → Properties → Networking → Internet Protocol Version 4 → Properties → Advanced.
5. Uncheck “Use default gateway on remote network.”

Note: your network administrator may block this setting for security reasons on work VPNs. If this option is grayed out, skip to Fix 5.

Fix 4: Fix DNS After VPN Connect

A VPN that pushes its own DNS servers can leave Windows pointing at unreachable DNS addresses after the tunnel drops — breaking name resolution even though the WiFi link is healthy. Here’s how to recover:

First, flush and renew DNS manually: open an admin terminal and run ipconfig /flushdns followed by ipconfig /registerdns.

If that doesn’t fix it, manually set your DNS servers to a reliable public resolver:

1. Open Network adapter settings (as in Fix 2).
2. Right-click WiFi → Properties → IPv4 → Properties.
3. Select “Use the following DNS server addresses.”
4. Enter 1.1.1.1 (preferred) and 1.0.0.1 (alternate) for Cloudflare DNS, or 8.8.8.8 and 8.8.4.4 for Google DNS.

This ensures DNS resolution works via your local WiFi connection regardless of what the VPN client does. See our guide on fixing WiFi DNS errors for more detail.

Fix 5: Disable IPv6 on the VPN Adapter

Many VPN clients only tunnel IPv4 traffic. IPv6 packets either leak outside the tunnel (a privacy issue) or get blocked entirely (a connectivity issue). Disabling IPv6 on the VPN adapter forces all traffic through the IPv4 tunnel and eliminates the conflict.

1. Open Network adapter settings.
2. Right-click your VPN adapter → Properties.
3. Uncheck “Internet Protocol Version 6 (TCP/IPv6).”
4. Click OK and reconnect the VPN.

Fix 6: Reinstall the VPN Client and TAP Driver

OpenVPN-based VPN clients (many commercial VPNs, corporate clients) install a TAP-Windows virtual adapter. If this driver is outdated or was corrupted by a Windows update, it will prevent traffic from flowing even though the VPN appears connected.

1. Fully uninstall your VPN client via Settings → Apps → Installed apps.
2. Open Device Manager → Network Adapters and look for any TAP-Windows Adapter V9 entries. Right-click each and choose Uninstall device, checking the box to delete the driver software.
3. Restart your PC.
4. Download the latest version of your VPN client from the vendor’s official website and reinstall.

Modern VPN clients using WireGuard don’t use TAP adapters and are significantly less prone to this class of problem. If your VPN provider supports WireGuard, switching to it often eliminates persistent connectivity issues.

Fix 7: Reinstall WAN Miniport Drivers

If you use the Windows built-in VPN (IKEv2, PPTP, L2TP), it relies on WAN Miniport drivers. A Windows update sometimes corrupts these. Open Device Manager → Network Adapters and look for entries named WAN Miniport (IP), WAN Miniport (IPv6), and WAN Miniport (PPTP). Right-click each → Uninstall device. Then click Action → Scan for hardware changes — Windows will reinstall fresh copies of these miniport drivers automatically.

Fix 8: Check Windows Firewall Network Profiles

When your VPN adapter connects for the first time after a Windows reinstall or update, Windows may prompt you to classify the network as Public, Private, or Domain. If the VPN is set to Public, Windows Defender Firewall blocks most inbound and outbound traffic on that adapter.

To check: open Windows Security → Firewall & network protection and look for your VPN adapter under the listed network profiles. If it shows as Public, click on it and toggle “Private network” (or Domain, if connecting to a corporate network). Alternatively, temporarily disable the firewall to test if it’s the cause, then re-enable it once you’ve identified the profile issue.

Last Resort: Full Network Reset

If none of the targeted fixes work, Windows 11’s built-in network reset removes all network adapters and reinstalls them, returning every network setting to its factory default. Go to Settings → Network & Internet → Advanced network settings → Network reset and click Reset now. Your PC will restart. You’ll need to reconnect to your WiFi network and reinstall your VPN client afterward, but this approach clears virtually any software-level networking problem.

Quick Diagnosis Table

• WiFi shows connected but no internet on VPN connect → Fix 1 (network stack reset) or Fix 3 (default gateway setting).
• DNS fails but ping by IP works → Fix 4 (DNS settings).
• VPN connected but some sites work and others don’t → Fix 5 (IPv6 conflict).
• Problem started after a Windows update → Fix 1, then Fix 7 (WAN miniport reinstall).
• Third-party VPN app seems connected but no traffic flows → Fix 6 (TAP driver reinstall).

Once your VPN is running cleanly, run a speed test to confirm your throughput. VPNs inherently add some overhead; if speeds are still slow after fixing connectivity, check our guide on why your VPN is slow and how to fix it.