How to Fix VPN on Windows Not Connecting
If you are trying to figure out how to fix VPN on Windows not connecting, the problem usually comes down to authentication, network settings, or software conflicts.
This guide walks through the most common causes and the fastest ways to restore a stable connection.
VPN failures on Windows can affect Microsoft built-in VPN, OpenVPN, WireGuard, and commercial apps such as NordVPN, ExpressVPN, Proton VPN, and Surfshark.
The same troubleshooting pattern often applies across all of them, which makes it easier to isolate the issue.
Check the Basics First
Before changing advanced settings, confirm that the issue is not caused by the VPN server, account, or internet connection itself.
A quick check can save time and point you in the right direction.
- Verify that your internet connection works without the VPN.
- Try a different VPN server or location.
- Sign out and sign back into the VPN app.
- Check whether your subscription is active and the credentials are correct.
- Look for service outages on the VPN provider’s status page.
If the VPN connects on another device using the same account, the problem is more likely tied to the Windows PC rather than the service.
Restart Windows and the VPN App
Windows networking components and VPN clients can get stuck after updates, sleep mode, or an interrupted connection.
A restart clears temporary states and reloads services that may be blocking the tunnel.
After restarting, open the VPN client and try again.
If the app has a built-in kill switch or auto-connect feature, temporarily disable it to see whether it is preventing reconnection.
Confirm VPN Credentials and Authentication Settings
Incorrect login details are a common reason VPNs fail to connect on Windows.
This is especially true when using manual configurations with usernames, passwords, certificates, or shared secrets.
What to verify
- Username and password are correct.
- Two-factor authentication codes are current and entered before expiry.
- Certificates have not expired or been removed.
- The VPN protocol matches the server requirement.
- Any pre-shared key or secret is entered exactly as provided.
If you recently changed your password, update it in the VPN client and in Windows Credential Manager if the profile stores saved credentials there.
Test Different VPN Protocols
Some Windows VPN connection problems are caused by the protocol itself.
Switching protocols often resolves handshake failures, blocked traffic, or unstable routing.
Popular VPN protocols include OpenVPN, WireGuard, IKEv2, L2TP/IPsec, SSTP, and PPTP.
Not all are equally secure, and some are more likely to work on restrictive networks.
When to switch protocols
- OpenVPN UDP is failing, so try OpenVPN TCP.
- WireGuard is not connecting, so test IKEv2 or OpenVPN.
- You are on a public Wi-Fi network that blocks UDP traffic.
- Your work or school network restricts certain ports.
Protocol support varies by provider.
If you use the built-in Windows VPN client, confirm that the server type and authentication method match the configuration exactly.
Check Windows Firewall and Antivirus Software
Security software can block VPN traffic, especially after an update or when a VPN app is newly installed.
Windows Defender Firewall, third-party antivirus tools, and endpoint protection suites may all interfere with tunneling.
Temporarily disable the firewall or real-time protection only long enough to test the connection.
If the VPN works after disabling security tools, create an exception for the VPN application and its network services.
Useful exception targets
- The VPN app executable
- VPN network adapters
- Relevant ports used by the protocol
- Split tunneling or tunneling helper services
If you are on a managed device, local changes may be overridden by Group Policy or enterprise security software.
In that case, contact your IT administrator.
Reset the Windows Network Stack
When a VPN on Windows will not connect, corrupted Winsock settings, broken DNS cache entries, or damaged IP configurations can be the cause.
Resetting the network stack often fixes these deeper problems.
Open Command Prompt as an administrator and run the following commands one at a time:
- netsh winsock reset
- netsh int ip reset
- ipconfig /flushdns
- ipconfig /release
- ipconfig /renew
After running the commands, restart the computer and try the VPN again.
This can resolve issues caused by stale routing data or a misbehaving network adapter.
Update or Reinstall the VPN Client
Outdated VPN software may not work properly after a Windows update or server-side change.
Newer VPN builds often include compatibility fixes, updated drivers, and protocol improvements.
If the app has an available update, install it first.
If the problem started after an update, a clean reinstall may help more than a simple repair.
Reinstalling safely
- Uninstall the VPN client.
- Restart Windows.
- Download the latest version from the official provider.
- Install it again and re-import your settings if needed.
For enterprise VPNs such as Cisco AnyConnect, Palo Alto GlobalProtect, or FortiClient, use the version approved by your organization to avoid compatibility issues.
Inspect the Network Adapter and Driver
VPN apps rely on virtual network adapters, and those adapters can malfunction after driver updates, power interruptions, or software conflicts.
If the adapter is disabled or corrupted, the VPN may never complete the connection.
Open Device Manager and check for warning symbols next to network adapters.
If needed, disable and re-enable the adapter, or update the driver from the PC manufacturer or chipset vendor.
- Restart the adapter from Network Connections.
- Update Wi-Fi and Ethernet drivers.
- Reinstall the VPN virtual adapter if the app offers it.
- Remove unused old VPN adapters that may conflict.
Review DNS and Server Name Issues
Sometimes the VPN technically connects, but traffic fails because DNS resolution is broken.
In other cases, a manual VPN profile points to an incorrect server name or outdated address.
Check whether the server hostname resolves correctly by trying another server or switching to a numeric IP address if your provider supports it.
If websites load on mobile data but not on the VPN, DNS may be the source of the problem.
You can also test public DNS services such as Google Public DNS or Cloudflare DNS to see whether name resolution improves.
Look for Problems Caused by Windows Updates
Windows 10 and Windows 11 updates can change networking behavior, reset permissions, or alter VPN compatibility.
If the issue began immediately after Patch Tuesday or a feature update, the timing matters.
Check for pending updates, install optional driver updates, and restart again.
If a recent update clearly broke the VPN and no other fix works, rolling back the update may be worth testing on non-managed machines.
Fix Work and School Network Restrictions
Some networks block VPNs by design.
Hotels, campuses, offices, and public hotspots may restrict ports such as 1194, 500, 4500, or 1723, or they may throttle unknown encrypted traffic.
When possible, test the VPN using a different network, such as a mobile hotspot.
If the VPN works there, the original network is likely filtering the connection.
In that case, switching protocols or using TCP-based settings often helps.
Use Windows Built-in VPN Troubleshooting Signals
Windows can provide clues even when it does not offer a dedicated VPN troubleshooter.
Event Viewer, network status icons, and connection logs can show whether the failure is authentication, transport, or name-resolution related.
- Event Viewer: check Windows Logs and the VPN client’s logs.
- Task Manager: confirm the VPN service is running.
- Network Status: verify that the adapter is active.
- Credential Manager: remove stale saved entries.
For corporate VPNs, the logs often reveal whether the remote gateway rejected the connection or the local machine failed before the handshake completed.
When to Contact Support
If you have already tested servers, protocols, credentials, security software, and network resets, the problem may require provider-side support.
A VPN vendor can check gateway status, account limits, certificate problems, or known incompatibilities with specific Windows builds.
Have the following ready when you contact support:
- Your Windows version and build number
- The VPN app version
- The exact error message
- The protocol you were using
- Whether the VPN works on another device or network
Clear details help support teams narrow the issue quickly and avoid repetitive troubleshooting.