When NordVPN hangs on "Connecting" on Windows 11, the cause is almost always one of three things: the app or its background service is in a bad state, your network is blocking the default NordLynx protocol, or a Windows 11 networking change has left the VPN adapter broken. The fixes below are ordered by how often they work, so start at the top and stop as soon as you are connected.
Start here: the three highest-yield fixes
- Update the app, then connect to a specific country. Open NordVPN, click the cog (Settings) at the bottom left, and install any update it offers. Then, instead of the big Quick Connect button, pick a single country from the list. A stale app build and an overloaded "best server" pick are the two most common causes, and both clear here.
- Switch the VPN protocol. Go to Settings, then Connection and security, then VPN protocol. If you are on the default NordLynx and it will not connect, choose OpenVPN (TCP). It runs over port 443 and looks like ordinary HTTPS traffic, so restrictive networks rarely block it.
- Reset the network stack. Open Command Prompt as administrator (press Start, type
cmd, right click it, choose Run as administrator) and run the commands in the next section. Restart afterwards.
If those three did not fix it, work through the cause-by-cause list below.
Reset DNS, Winsock and the IP stack
Stale network state is a frequent culprit after you change networks or wake the PC from sleep. In an administrator Command Prompt, run these in order:
ipconfig /flushdns
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renewThen restart Windows. The winsock and IP resets only take full effect after a reboot. One caveat: netsh winsock reset clears third party network filters, so any other VPN or security suite may need to reconnect or be reopened afterwards.
Switch protocol for a restrictive network (and meet NordWhisper)
If NordVPN works on mobile data or another Wi-Fi but not on your office, campus, hotel or some home ISPs, the network is blocking VPN traffic. NordLynx (which is WireGuard based and runs over UDP) is the protocol most often blocked. Two answers, both under Settings, then Connection and security, then VPN protocol:
- OpenVPN (TCP): traffic over port 443 that blends in with normal web browsing. Try this first.
- NordWhisper: NordVPN's newer obfuscation protocol, purpose built to defeat firewalls that block VPNs. Reach for it when even OpenVPN TCP fails. Note that NordWhisper is not compatible with Meshnet, Dedicated IP, Obfuscated servers or Onion Over VPN, so turn those off if you use them.
Windows Firewall or your antivirus is blocking it
This one is easy to miss, and it is genuinely ironic: a third party antivirus can silently block the VPN it is supposed to sit alongside. If the app opens but the handshake never completes, especially right after you installed or updated a security suite, do both of these:
- Allow NordVPN through Windows Firewall. Press Start, search for Windows Defender Firewall, open Allow an app or feature through Windows Defender Firewall, click Change settings, then Allow another app, Browse to the NordVPN program (usually in
C:\Program Files\NordVPN\), add it, and tick both Private and Public. - Add NordVPN to your antivirus exceptions. If you run a separate suite, add NordVPN to its exclusions or exceptions list. The web shield or firewall module in suites like McAfee, Avast or Kaspersky can block the tunnel. If you are weighing whether that suite is worth the hassle, see our antivirus reviews and our take on the best antivirus for Windows (Windows Defender alone rarely causes this conflict).
If an app based rule still fails, create inbound firewall rules for TCP 443 and UDP 1194, the ports NordVPN's OpenVPN protocol uses.
Restart the NordVPN background service
If the app window loads but the Connect button does nothing, the background service has probably stalled. Press Start, type services.msc, open it, find NordVPN Service, right click and choose Restart (or Start if it is stopped), and set its Startup type to Automatic. Launching the NordVPN app once as administrator also lets it re register the service.
Reinstall the NordVPN network adapter
A corrupted virtual adapter, common after a messy uninstall or a Windows update, produces "could not create tunnel" style failures. Press Start, type devmgmt.msc to open Device Manager, expand Network adapters, then right click the NordVPN or NordLynx adapter and choose Uninstall device. In Settings, then Apps, then Installed apps, also remove "NordVPN Network TUN" if it is listed. Restart, then reinstall the latest NordVPN app, which recreates the adapter cleanly. A lighter first attempt is Network adapters, then Scan for hardware changes.
Turn off Fast Startup (the "only works after a restart" clue)
Here is a Windows 11 specific gotcha that generic guides miss. If NordVPN connects fine after you choose Restart, but never after a full shutdown and power on, Fast Startup is leaving the network adapter in a stale half asleep state. Turn it off: open Control Panel, then Hardware and Sound, then Power Options, click Choose what the power buttons do, click Change settings that are currently unavailable, untick Turn on fast startup, and Save changes.
Test IPv6 (carefully)
On some dual stack home and ISP networks, IPv6 routing interferes with the tunnel. As a reversible test, press Start, type ncpa.cpl, open it, right click your active Wi-Fi or Ethernet connection, choose Properties, and untick Internet Protocol Version 6 (TCP/IPv6). It applies immediately, no reboot. Be honest with yourself here: Microsoft does not recommend disabling IPv6 permanently, so treat this as a diagnostic step and re enable it if it makes no difference.
If it broke right after a Windows 11 feature update
After the Windows 11 24H2 update (and the builds that inherited its networking stack), a number of users reported WireGuard based VPNs showing "connected" while passing no traffic. Because NordLynx is WireGuard based, NordVPN can be caught by this. The most widely reported workaround is to enable Virtual Machine Platform: open Control Panel, then Programs, then Turn Windows features on or off, tick Virtual Machine Platform, and restart.
Two honest caveats. First, this is a community reported fix, not an official NordVPN or Microsoft advisory tying NordVPN to 24H2 by name, so try it only if your problem started right after a feature update. Second, if it persists, switching NordVPN to OpenVPN (above) sidesteps the WireGuard issue entirely, and as a last resort some users rolled the feature update back from Settings, then Windows Update, then Update history.
Two quick ones worth ruling out
- Wrong system clock. A clock that is off makes valid server certificates look expired. Open Settings, then Time and language, then Date and time, enable Set time automatically, and click Sync now.
- Network level blocking. If every protocol fails on one network but everything works on a phone hotspot, that network is blocking VPNs. Use NordWhisper or an Obfuscated server, or stay on OpenVPN TCP.
Still stuck?
If you have worked through the list and NordVPN still will not connect, do a clean reinstall: uninstall the app, reinstall the network adapter as described above, restart, and install the latest version from NordVPN directly. Confirm the problem follows you to a phone hotspot to rule out the network, and if it does not, contact NordVPN support with the protocol you tried and the exact error text. For the bigger picture on whether NordVPN is the right tool for you, read our full NordVPN review.