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 No comments

118 answers

Sort by: Newest
  1. Anonymous
    2019-10-14T20:53:39+00:00

    I don't know what that code does but id be leary about running a powershell command with admin rights AND when the author says "*Note: During the command execution you'll receive some errors, which can be safely ignored."  Be cautious....very cautious.  

    That particular Powershell command is a very common one that re-registers Windows apps. It's safe.

    -Forjo

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-10-14T14:32:31+00:00

    I don't know what that code does but id be leary about running a powershell command with admin rights AND when the author says "*Note: During the command execution you'll receive some errors, which can be safely ignored."  Be cautious....very cautious.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-10-14T13:28:20+00:00

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-10-09T23:58:20+00:00

    Check out my post on page 4 of this thread.  The workaround I describe should work for your issue until Microsoft provides a permanent fix.

    edit----

    Actually I'll just paste the original post here since most don't seem to be seeing it any longer.

    As stated in earlier posts, this issue IS caused by Windows' failure to display the credentials dialog prompt when using the system tray to initiate a VPN connection. If initiated via System Settings or using the Rasdial command all VPNs connect successfully. It would seem by saving your credentials via Rasdial or System Settings that the credentials prompt would no longer be required. Unfortunately this is not the case. In order to use the System Tray to initiate a VPN connection successfully you will need to make sure the "Remember my credentials" box is checked for each VPN adapter setup in the Network Connections control panel. Once the credentials are saved using the System Settings connection method, connecting via the System Tray will be possible for future connections. This is definitely not a fix but a workaround. Hopefully Microsoft will resolve this issue soon.

    In summary:

    System Settings -> VPN -> VPN connection -> Advanced Options -> Edit

         add Username and Password to the connection profile -> check box for "Remember my sign-in info" -> SAVE

    Next do the following

    Control Panel -> Network and Sharing Center -> Change adapter settings

         right click desired VPN adapter -> Properties -> Options tab -> check box for "Remember my             credentials" -> OK

    I hope this helps clear up the confusion as to how to workaround this frustrating issue. 

    These are workarounds that introduce more complexity and potential security issues (saving user credentials).  Also with saved when say the users password for the network changes, they don't know to edit their VPN password - issue is back.  Thanks for posting these, but what we really need is for MS to fix this obvious UI bug.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-10-09T21:41:36+00:00

    Take a chill pill buddy!!

    I agree that this is NOT a solution. I was very clear in stating that this is just a WORKAROUND and that MS needs to fix the problem. However, if someone needs to get this working in the meantime this IS the workaround to Microsoft's problem.

    Was this answer helpful?

    0 comments No comments