KB4522355 fix it for me in one of my W10 1903 machines that had issues. I also found it was fixed in insider build (don't recall the build number), but then a new insider build was released and the issue is even worse. VPN doesn't work at all, even from the settings charm :P. But again this is insider builds.
VPN not working on Windows 10 1903
I am an IT technician at an IT company. One of our clients has asked us to install a fresh version of Windows onto 6 of their PCs.
These PC's are old PC's that they do not use - meaning that they have had a fresh version of Windows installed onto them. This has been upgraded to 1903. I have attempted to setup a VPN connection in order to connect the PC's to the company's domain. When doing so, the VPN connection just hangs on 'Connecting to vpn'
I know 1903 is still very new into the world, but wondering if anyone knows how this issue can be resolved?
Windows for home | Windows 10 | Internet and connectivity
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
118 answers
Sort by: Oldest
-
Anonymous
2019-11-06T19:51:19+00:00 -
Anonymous
2019-11-10T03:53:42+00:00 Hello everyone, recently I updated Windows 10 Pro from version 1809 to 1903and it broke my VPN PPTP and L2TP Windows Built-In. You need to have a right OS Build to make PPTP and L2TP VPN work again. I had Windows 10 version 1903 OS Build 18362.418 but you need to get OS Build 18362.449 that's when Windows Built-In PTTP and L2TP VPN will start working. Get this update 2019-10 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4522355)
-
Anonymous
2019-11-11T20:55:45+00:00 Hey Everyone,
I have been following this thread like everyone else who had their VPN solution broken with the 1903 update. We have applied the KB4522355 and still no luck with our Direct Access implementation. Any word on this?
-
Anonymous
2019-11-12T21:10:29+00:00 Hey Everyone,
I have been following this thread like everyone else who had their VPN solution broken with the 1903 update. We have applied the KB4522355 and still no luck with our Direct Access implementation. Any word on this?
Are you using PPTP or L2TP VPN ?
-
Anonymous
2019-11-13T20:06:00+00:00 We are using Windows Server 2016 Remote Access. I believe the service on the clients that stopped working after the update was RASMAN. This solution is a L2TP VPN. When I troubleshoot I keep getting the error from the direct access troubleshooter that it can't tunnel to the direct access server but no errors are thrown when I run netsh in httpstunnel show int.