Although the video is for build 10162, I can confirm that this is a problem in 10240 as well. This is quite bad, it's probably a bug.
Yes I reported this bug before RTM phase but guess they did not have time to fix it, remember there where several issues with networking in the insider 10240 build, crashing explorer etc... But thanks for the workaround, at least now I can use my VPN! Edit: settings for disabling default gateway are: IpPrioritizeRemote=0 Ipv6PrioritizeRemote=0
Any news about this problem ? we received a lot of updates since july 29, but this annoying problem is still here...
You can also use powershell to modify the connection: To disable the default gateway: Set-VpnConnection -Name "NameGoesHere" -SplitTunneling $True To reenable: Set-VpnConnection -Name "NameGoesHere" -SplitTunneling $False