The kill switch blocking traffic while the VPN tunnel isn’t fully established is the most common cause. Here’s how to identify and resolve it.
The VPN kill switch is designed to block all internet traffic if the VPN tunnel drops — preventing any data from traveling unencrypted. When the kill switch is active and the VPN connection itself fails to fully establish, the kill switch correctly blocks all traffic. The result looks like the VPN is 'on' but the internet is completely unavailable. This is the intended behavior of the kill switch, but it traps users who don't realize the VPN isn't actually connected.
VPN connections typically override the DNS server settings Windows uses, pointing traffic through the VPN provider's DNS. If the VPN's DNS configuration fails to apply — or conflicts with manually set DNS servers — domain names can't resolve, making the internet appear unavailable even though the TCP/IP connection is working. This presents as 'connected' with no web pages loading rather than a complete network failure.
Split tunneling allows some traffic to bypass the VPN tunnel while other traffic routes through it. A misconfigured split tunnel can accidentally route all traffic through the VPN when the tunnel is broken, or block traffic that was meant to bypass the VPN. This is particularly common after updating the VPN client, which may reset split tunneling rules to default.
VPN clients install a virtual network adapter in Windows that all VPN traffic routes through. If this adapter's driver becomes corrupted — after a Windows update, driver conflict, or incomplete VPN update — the adapter can block traffic without the VPN being able to fix it through settings alone. The adapter appears in Device Manager but fails to route traffic correctly. A full uninstall and reinstall of the VPN client removes and recreates the adapter.
Open your VPN client's settings and look for 'Kill Switch,' 'Network Lock,' or 'Internet Kill Switch.' If it's enabled, temporarily turn it off. Then attempt to connect the VPN. If internet access returns when the kill switch is off, the kill switch is working correctly — the underlying VPN connection is failing, which triggers the kill switch to block traffic. Fix the VPN connection issue first (see 'Windows VPN Won't Connect'), then re-enable the kill switch.
Press Win + S and search for 'Command Prompt.' Right-click it and select 'Run as administrator.' In the window, type: `ipconfig /flushdns` and press Enter. You should see 'Successfully flushed the DNS Resolver Cache.' Then disconnect and reconnect the VPN. This clears cached DNS entries that may have become stale or conflicted with the VPN's DNS settings.
Clicking 'Disconnect' in the VPN client may leave background processes running. Right-click the VPN icon in the system tray and choose 'Quit' or 'Exit' to fully close it. Wait 10 seconds. Then relaunch the client from the Start menu and reconnect. This clears any in-memory state where the client believes it's partially connected — which is enough to trigger the kill switch — without actually having a working tunnel.
In your VPN client's settings, look for Split Tunneling (may also be called 'App Exclusions' or 'Bypass VPN'). If enabled, temporarily disable it and reconnect. If internet access returns, a split tunneling rule was routing traffic incorrectly. Review each app exclusion rule and remove any that shouldn't be there, or reset split tunneling to default settings.
A full Windows restart clears routing table state, resets network adapter drivers, and terminates any background VPN processes that may be holding the network in a partially configured state. After restarting, connect the VPN before opening any other applications to give it a clean network state to work with.
Go to Settings > Apps > Installed Apps and search for your VPN client. Uninstall it completely and restart Windows. After restarting, download the latest version from the VPN provider's website and install fresh. This removes and recreates the virtual network adapter and all associated driver files, which is the only way to fully reset a corrupted VPN network configuration that has persisted through client restarts.
Tell our AI your VPN client, what happens when you disconnect the VPN, and whether you've tried reinstalling — it'll help pinpoint the cause.
Describe what happens when you connect and disconnect the VPN — our AI will walk you through a targeted fix.
Start Free Diagnostic Chat →