VPN not working on Windows 10 1903

Anonymous
2019-05-31T15:38:48+00:00

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.

0 comments

118 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-11-15T04:53:18+00:00

    Well, nevermind. It still isn't fixed. Still hangs on Connecting... from the task tray, but connects fine from the Settings VPN menu. Five different test boxes and two VMs still show no change from before the KB was installed. 

    Whatever they "fixed" in KB4522355, it wasn't in the task tray GUI. Come'on Microsoft...test your fixes before you deploy. I'd love to write **** software, never fix a critical bug, and still get paid!

    odd. the KB resolved it for 3 of the machines I tried it on.   Maybe try installing it again?  What VPN type are you using ?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-14T23:56:32+00:00

    The update to v1909 resolves the issue

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-13T20:51:53+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.

    Hmm I see we are using Cisco Appliance for L2TP VPN and it works fine after applying (KB4522355) update...I hope you will get it to work

    Was this answer helpful?

    0 comments
  4. 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.

    Was this answer helpful?

    0 comments
  5. 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 ?

    Was this answer helpful?

    0 comments