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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-06-04T13:00:46+00:00

    This issue has been resolved. I had created a thread on TechNet and the user Travis Huang was able to provide a solution.

    Simply by connecting to the VPN via the settings menu instead of using the tasktray!

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2019-06-15T14:21:51+00:00

    I upgraded this week and had the same problem and found an easy to implement workaround, I have put the details on my blog:

    https://www.tachytelic.net/2019/06/vpn-connections-not-working-windows-10-1903-update/

    Basically it involves using the old rasphone executable to connect to your VPN connections instead of the new Windows 10 tray interface. It's not a fix but it is very easy to implement and actually the old interface is a bit more informative than the new one.

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments
  3. Anonymous
    2019-06-08T06:56:24+00:00

    The issue appears to be the login dialog box which gets prompted for credentialing the user to enter a username and password for the VPN CONNECTION.

    Based on my testing, I figured out that if the username and password is saved in the VPN SETTINGS, then the VPN object from the System Tray works just fine.  The problem only happens when the VPN initiates the login and the Login Dialog Box fails to open for prompting the username and password. 

    I am not a programmer but it is safe to say the problem seems to stem from the Login Dialog Box not getting the proper permissions and/or parameters  necessary to pop up securely in order to  authenticate the user. 

    I reported the issue to CISCO MERAKI as well since their online instruction now is partially broken!  Based on their documents, if one double clicks the Network VPN Adapter Object that gets created with the setup of the VPN, it will launches the Network Object in the System Tray which is in turn is used to start the VPN CONNECTION and then fails to open the login dialog box.

    This should be an easy fix if Microsoft actually reads it's own forums for reported issues.

    Mike Khatibi

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2019-06-05T13:50:09+00:00

    This isn't a solution. It's a workaround. User's shouldn't be expected to do this. 

    This has been a long outstanding problem:

    https://social.technet.microsoft.com/Forums/en-US/821b5675-743b-4d52-87a4-3f5491c122f3/vpn-connection-from-system-tray-does-not-work-but-works-from-network-settings?forum=win10itpronetworking

    I found my way on to this post while searching to see if 1903 fixes this issue but alas it hasn't. Unbelievable that this is still not resolved.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  5. Anonymous
    2019-06-08T18:56:50+00:00

    I'm a developer as well as an IT director, so I'm half-tempted to attached a debugger to the tray on one of these boxes that don't work around here. But, I'm pretty sure that the reason it doesn't throw any event errors is that the tray is nothing more than a dumb call to the actual API and they missed/forgot to update/added a dependency that the tray calls. Since the call never actually makes it through, the API doesn't actually do anything and hence, no logging of any sort. 

    I just BSOD'd a box poking the driver structure and after reboot...now the connections work from the tray on that box??! Hmm. 

    Yeah, I love how each an every release they jump through hoops to make stupid little GUI things "better", check like crazy to be sure gaming features work, and add useless visual features, but never take the time to validate features like VPNs, domain functions, and other business features.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments