A Windows VPN can say “Connected” and still break your internet—usually because routing or DNS didn’t switch cleanly, or something is blocking traffic after the tunnel comes up.
Start at step 1 and stop as soon as things work.
Before you begin: if you’re on a work/school VPN, some “no internet” situations are actually policy (they may block general browsing and only allow internal sites). Step 2 helps you tell the difference.
1. Fastest reset: disconnect, wait 10 seconds, reconnect (and try one browser)
This sounds basic, but it fixes the common case where the VPN handshake succeeded and Windows didn’t fully update routes or DNS.
- Disconnect the VPN.
- Wait 10 seconds.
- Reconnect.
- Test in a single browser tab (don’t open five apps at once while testing).
If it works briefly and then dies again, keep going—something is likely conflicting with the tunnel.
2. Quick diagnosis: is it “no internet” or “only internal sites”?
When a VPN is set to full-tunnel mode, all traffic goes through it. When it’s split-tunnel, only certain company traffic does. If the VPN server or rules block general web access, Windows will feel “offline” even though the VPN is doing exactly what it’s told.
- Try opening an internal resource you normally use on VPN (an intranet URL, a file share, a corporate portal).
- Then try a public site you rarely have cached (for example, example.com).
If internal works but public doesn’t: it’s likely VPN policy or DNS rules. Jump to step 4 (DNS) and step 6 (support stop point).
If nothing works at all: continue to step 3.
3. Turn off the two usual “traffic hijackers”: proxy and “kill switch” behavior
Two settings can make Windows look disconnected even after the VPN is up: a leftover proxy and a kill switch / firewall rule that blocks traffic when the VPN isn’t fully established.
- Check Windows proxy: Settings → Network & internet → Proxy → turn off “Use a proxy server” (unless you intentionally use one).
- VPN app kill switch: in your VPN app settings, look for Kill Switch / Block internet when disconnected. Temporarily disable it just to test.
If disabling either one restores internet, re-enable carefully and adjust the VPN app settings (or remove the proxy entirely if it wasn’t intentional).
4. Fix the most common deep cause: DNS is pointing the wrong way
VPN “connected but nothing loads” is often DNS. The tunnel comes up, but your PC is still using a DNS server that can’t be reached (or your VPN-provided DNS is blocked).
- Open Command Prompt (or Windows Terminal) as a normal user and run: ipconfig /flushdns
- Then toggle your network adapter off/on: Settings → Network & internet → Advanced network settings → Disable/Enable your Wi‑Fi or Ethernet.
If you’re comfortable doing a targeted change, set DNS temporarily to a known public resolver to test (you can revert later):
- Control Panel → Network and Internet → Network Connections
- Right‑click your active adapter → Properties → Internet Protocol Version 4 (TCP/IPv4)
- Use these DNS servers: 1.1.1.1 and 8.8.8.8
Note: on some work/school VPNs, public DNS is intentionally blocked. If public DNS fixes it, your VPN DNS push/config may be broken; if public DNS breaks internal resources, revert and continue to step 5.
5. Remove conflicts: pause other network filters (security suites, other VPNs, virtual adapters)
Windows can have multiple “filter drivers” attached to the network stack (security software, other VPN clients, packet capture tools). Conflicts can allow the tunnel to connect but block actual traffic.
- Temporarily quit or pause third‑party firewall/AV network protection (test briefly, then re-enable).
- If you have another VPN client installed, make sure it’s fully disconnected and not auto-starting.
- In Settings → Network & internet → Advanced network settings, look for extra adapters (old VPNs, virtual switches). If you recognize an old one you no longer use, disable it for a test.
When you find the conflicting component, the “real” fix is usually updating that software, not leaving protection disabled.
6. Deepest repair: reset the Windows network stack (then know when to stop)
If steps 1–5 didn’t help, do a clean network reset. This is the point where Windows re-writes core networking components that VPNs depend on.
- Restart the PC (do this even if you already did earlier).
- Open Command Prompt as Administrator and run: netsh winsock reset
- Then run: netsh int ip reset
- Restart again.
If you’re on Windows 11/10, you can also use: Settings → Network & internet → Advanced network settings → Network reset (this removes and reinstalls adapters). You may need to re-enter Wi‑Fi passwords afterward.
Stop point for support: if the VPN connects but you still have no traffic, collect these details before contacting your VPN provider or IT: the VPN app name/version, Windows version, whether internal sites work, and whether the issue happens on other networks (home Wi‑Fi vs mobile hotspot). That’s usually enough for them to identify a DNS/routing or policy problem quickly.
Final thoughts
Most “connected but no internet” VPN issues on Windows come down to DNS not switching cleanly, a proxy/killswitch blocking traffic, or a conflict with another network filter.
If step 4 changes the behavior at all, you’re very close—focus on DNS and policy rather than reinstalling everything.