VPN: Using IPv6 in Windows 10+

By default, Windows doesn't add an IPv6 route to VPN connections. There is a workaround:

On Windows 10, and presumably on every later version where PowerShell is available, you can use the MS PowerShell cmdlet Add-VpnConnectionRoute. This cmdlet won't let you add the default route 0::/0. In most cases, though, you don't actually need a default route through the VPN. As of now (January 2026), the IPv6 space has only the 2000::/3 block allocated as Global Unicast, and adding this prefix is quite enough to route all traffic through the VPN interface. The cmdlet takes care of adding the route when the VPN connects and removing it when it disconnects. Also, unlike netsh, it usually doesn't require administrator rights and is fully integrated with the Windows GUI, which saves you from having to use batch files.

Add-VpnConnectionRoute -ConnectionName "<interface name>" -DestinationPrefix "2000::/3"