If your VPN stopped working after updating to Windows 10 version 1903, the usual culprits are the built-in L2TP/IPsec or IKEv2 settings, a misconfigured network adapter, or the update resetting your VPN connection properties. Start by checking if your VPN uses L2TP or PPTP, then re-create the connection manually or apply the specific registry fix for L2TP, and finally run the Windows network reset if the problem persists. Below is a step-by-step guide to get your VPN back online, plus background on why this update caused so many issues.
Why Windows 10 v1903 Broke Many VPNs
The May 2019 Update (version 1903) introduced several networking changes, including a new Windows Defender Firewall rule set and a revised Routing and Remote Access service behavior. Many users found that their corporate VPNs (especially those using L2TP/IPsec with a pre-shared key) would connect but then immediately drop, or fail with error 789, 809, or 806. The update also reset the default IPsec settings, causing the VPN client to send incompatible security associations.
Another common issue was that the update changed the way Windows handles DNS and default gateways for VPN connections. If your VPN was set to use the remote gateway, the update sometimes cleared that checkbox, so traffic kept flowing through your local internet connection instead of the tunnel.
Quick Fixes to Try First
Before diving into registry edits, try these simple steps that resolve a large percentage of cases:
- Re-enter your VPN credentials – Go to Settings > Network & Internet > VPN, select your connection, and click Advanced options. Re-type the username, password, and domain (if any). Sometimes the update corrupts the stored credentials.
- Change the VPN protocol – If your provider supports multiple protocols (e.g., OpenVPN, IKEv2, SSTP), switch to a different one in the connection settings. For example, if you were using L2TP, try IKEv2 or SSTP.
- Run the Windows Network Troubleshooter – Settings > Update & Security > Troubleshoot > Additional troubleshooters > Network Adapter. This can reset the network stack automatically.
- Disable IPv6 on the VPN adapter – In Network Connections (ncpa.cpl), right-click your VPN adapter, select Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and click OK.
Fix L2TP/IPsec VPNs After the 1903 Update
If your VPN uses L2TP/IPsec with a pre-shared key (PSK), the 1903 update changed the default IPsec security association lifetimes, causing connections to fail. The most reliable fix is to add a registry key that restores the old behavior.
- Press Win + R, type
regedit, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PolicyAgent. - Right-click on the PolicyAgent key, select New > DWORD (32-bit) Value.
- Name it
AssumeUDPEncapsulationContextOnSendRule. - Double-click it and set the value to
2(this allows the VPN to work behind a NAT). - Click OK and restart your computer.
This registry fix tells Windows to assume UDP encapsulation is being used, which is common when connecting from behind a router or when the VPN server is behind a NAT. Many users report that this single change resolves error 809 and 806.
Fix IKEv2 VPNs After the 1903 Update
IKEv2 connections also suffered from the update, often due to the Cryptography settings being reset. The most common error is 13806 or 13801, indicating that the IKE authentication failed. To fix this:
- Open Command Prompt as Administrator (right-click Start > Windows PowerShell (Admin)).
- Run the following command to reset the IPsec policy agent:
net stop policyagent && net start policyagent - Then, run
ipconfig /flushdnsto clear the DNS cache. - If the issue persists, check if your VPN server certificate is trusted. In the VPN connection properties (Settings > Network & Internet > VPN > your connection > Advanced options), ensure that Use IKEv2 is selected and that the server address matches the certificate’s subject name.
If you still get errors, try changing the VPN type to Automatic in the connection settings. Windows will then negotiate the protocol, which often works around the 1903-specific issues.
Reset the Network Stack and Recreate the VPN
If the above steps fail, a full network reset can clear the corrupted settings that the 1903 update introduced. This will remove all your VPN connections and network adapters, so you will need to recreate them afterward.
- Go to Settings > Network & Internet > Status.
- Click Network reset at the bottom.
- Click Reset now and confirm. Windows will restart.
- After restart, go to Settings > Network & Internet > VPN and add your VPN connection again.
When recreating the connection, pay close attention to the VPN type drop-down. Choose the correct protocol (e.g., L2TP/IPsec with PSK, IKEv2, or SSTP) and enter the server address exactly as provided by your VPN service. If you use a pre-shared key, click Advanced options and enter it in the Pre-shared key field.
Common Errors and Their Specific Fixes
- Error 789 – “The L2TP connection attempt failed because the security layer encountered a processing error.” This is often fixed by the registry edit above or by enabling the Use preshared key for authentication option.
- Error 809 – “The network connection between your computer and the VPN server could not be established.” This usually indicates a firewall or NAT issue. Check that UDP ports 500 and 4500 are open on your router, and apply the registry fix.
- Error 806 – “The connection between your computer and the VPN server was established, but the VPN connection cannot be completed.” This often means the VPN server is not responding to the encapsulation. Try disabling the Windows Firewall temporarily to test, then re-enable it.
- Error 13801 – “IKE authentication credentials are unacceptable.” This is common with IKEv2 and means the server certificate is not trusted. Install the correct root certificate or switch to a different protocol.
Frequently Asked Questions
Why did my VPN stop working after the 1903 update?
Windows 10 version 1903 changed the default IPsec and firewall settings, which broke many VPN clients that relied on older configurations. The update also reset some VPN connection properties, such as the “Use default gateway on remote network” checkbox, causing traffic to bypass the tunnel.
Will the registry fix work for all L2TP VPNs?
The registry fix (AssumeUDPEncapsulationContextOnSendRule) is specifically for L2TP/IPsec connections that fail because of NAT traversal. It works for most home and small office setups, but if your VPN server is not behind a NAT, it may not help. In that case, try disabling the Windows Firewall or using a different protocol.
Can I roll back to an older Windows version to fix the VPN?
Yes, you can roll back to Windows 10 version 1809 within 10 days of updating, but this is not a long-term solution. Microsoft has released several cumulative updates that fix many VPN issues, so it’s better to apply the latest updates and use the fixes above.
Is it safe to edit the registry?
Editing the registry can be risky if you make a mistake, but the specific key mentioned here is safe and widely recommended by network administrators. Always back up the registry before making changes (File > Export in regedit) and only change the values described.
My VPN works on other devices, why not on Windows 10?
If your VPN works on a phone or another PC, the issue is specific to your Windows configuration. The steps above address the most common Windows-related causes, such as protocol settings, firewall rules, and the network stack. If none work, consider using the VPN provider’s own client software instead of the built-in Windows VPN client.
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
- Fix msmpeg2vdec.dll Errors in Windows
- How to Update Sonos App and Speakers
- Unlock iPad Without Apple ID: Is It Possible?
- iOS 18 WhatsApp Notifications Not Working? Fix
- Fix Windows Cannot Locate Suitable Printer Driver
- How to Group Text and Pictures in Word