sodcalculator

10 Tech How-To

Fix Windows VPN Only Connecting After Restart

Guide 10-51610 · Updated · Step by step

If your Windows VPN only connects after a full restart, the problem is usually a stuck service, a stale network configuration, or a conflict with the WAN Miniport drivers. This guide walks you through the most effective fixes, from simple service restarts to deeper driver and registry adjustments, so you can get a reliable connection without rebooting every time.

What You’ll Need

  • Administrator access to your Windows PC (to run commands and change settings)
  • Your VPN connection name (as shown in Settings > Network & Internet > VPN)
  • Your VPN server address and credentials (for re-creating the connection if needed)

Step-by-Step

  1. Restart the VPN-related services. Press Win + R, type services.msc, and press Enter. Find Remote Access Connection Manager and Remote Access Auto Connection Manager. Right-click each and select Restart. If they are not running, start them. Then try your VPN connection.
  2. Disable and re-enable the VPN adapter. Open Control Panel > Network and Sharing Center > Change adapter settings. Right-click your VPN adapter (often named “WAN Miniport (IKEv2)” or similar) and select Disable. Wait a few seconds, then right-click again and select Enable. Try connecting.
  3. Run the network troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters and run Network Adapter troubleshooter. Follow the prompts; it may detect and fix misconfigured settings.
  4. Reset the network stack. Open Command Prompt as administrator (right-click Start > Terminal (Admin) or Command Prompt (Admin)). Run the following commands one by one, pressing Enter after each:
    ipconfig /release
    ipconfig /renew
    ipconfig /flushdns
    netsh winsock reset
    netsh int ip reset
    Restart your PC (this is the one time a restart is required) and then test the VPN. If it works, the issue was a corrupted network state.
  5. Reinstall the WAN Miniport drivers. Open Device Manager (right-click Start > Device Manager). Expand Network adapters. Look for devices with “WAN Miniport” in the name. Right-click each one and select Uninstall device. Check the box “Delete the driver software for this device” if available, then click Uninstall. After uninstalling all WAN Miniport devices, restart your PC. Windows will reinstall them automatically.
  6. Check the VPN protocol and server settings. Go to Settings > Network & Internet > VPN, click your VPN connection, and select Advanced options. Ensure the VPN provider (e.g., Windows built-in) and the protocol (e.g., IKEv2, SSTP, L2TP) match what your VPN service requires. If unsure, try switching to Automatic protocol. Also verify the server address is correct.
  7. Disable IPv6 on the VPN adapter. In Change adapter settings, right-click your VPN adapter and select Properties. Uncheck Internet Protocol Version 6 (TCP/IPv6) and click OK. This resolves some routing conflicts.
  8. Modify the registry to disable smart multi-homed name resolution (if using DirectAccess or Always On VPN). This is an advanced step. Press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters. If a DWORD named DisableSmartNameResolution exists, set its value to 1. If not, right-click in the right pane, select New > DWORD (32-bit) Value, name it DisableSmartNameResolution, and set its value to 1. Close the registry editor and restart your PC.

Common Mistakes

  • Skipping the service restart. The Remote Access Connection Manager often gets stuck after sleep or network changes. Restarting it is the fastest fix and should always be the first step.
  • Not running commands as administrator. The netsh and ipconfig commands will fail or do nothing without admin rights. Always open the terminal with “Run as administrator”.
  • Uninstalling the wrong driver. Be careful to only uninstall WAN Miniport devices, not your physical Wi-Fi or Ethernet adapter. Uninstalling the wrong one can cut off your internet.
  • Changing the protocol without checking with your VPN provider. Some VPN services only support specific protocols. Switching blindly can break the connection entirely.
  • Forgetting to restart after driver reinstall. The WAN Miniport drivers are reinstalled automatically, but Windows needs a restart to load them properly.

Tips

  • Create a system restore point before making registry changes. This gives you an easy rollback if something goes wrong.
  • If you use a third-party VPN client, check for updates. Outdated clients often cause connection issues that appear to be Windows-related.
  • Use the built-in Windows VPN client if possible. It is more stable and integrates better with the network stack.
  • Keep your network drivers up to date. Use Windows Update or your PC manufacturer’s support site.
  • If you use a laptop, disable the VPN adapter before switching from Wi-Fi to Ethernet (or vice versa) to avoid conflicts.

Troubleshooting

  • If the VPN still fails after a restart: The issue is likely with your VPN server or credentials. Contact your VPN provider or try a different server.
  • If you get error 809 or 720: These often indicate a protocol mismatch or a blocked port. Try switching to SSTP or OpenVPN (if your provider supports it).
  • If the VPN connects but you have no internet: Check the VPN adapter’s DNS settings. In the adapter properties, select Internet Protocol Version 4 (TCP/IPv4) and click Properties. Ensure “Obtain DNS server address automatically” is selected, or set the DNS to your VPN provider’s recommended addresses.
  • If the registry edit does not help: Delete the DWORD you created and restart. The edit is only relevant for certain network configurations.
  • If you cannot uninstall the WAN Miniport drivers: Try running Device Manager as administrator. If that fails, boot into Safe Mode and uninstall from there.

Frequently Asked Questions

Why does my VPN only work after a restart?

Usually because a Windows service (like Remote Access Connection Manager) gets stuck, or the network stack has a stale route. A restart clears these, but the underlying issue remains.

Will resetting the network stack delete my saved Wi-Fi passwords?

No. The commands netsh winsock reset and netsh int ip reset only reset network protocols and settings. Your saved Wi-Fi profiles and passwords remain intact.

Is the registry edit safe?

Yes, if you follow the steps carefully. Creating a restore point first is recommended. The edit only affects how Windows resolves certain network names and is reversible.

Can I avoid restarting by just disabling and enabling the adapter?

Sometimes. Disabling and re-enabling the VPN adapter can clear the stuck state, but it does not fix the root cause. The service restart (step 1) is more reliable.

Why does my third-party VPN client have this issue but the built-in one doesn’t?

Third-party clients often use their own drivers and services that may conflict with Windows network components. Updating the client or reinstalling it often resolves the conflict.

How often should I run these fixes?

If you need to run them daily, the problem is deeper. Consider updating your network drivers, checking for Windows updates, or contacting your VPN provider for a configuration guide.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →