Both fresh installs from ISO and upgraded exhibit the issue. All the upgraded were from 1809 or 1709. Funny part is that I got one of the 1709 upgrades to work with the VPN from tray...but only some will connect there. Even worse is that every one has the ridiculous ICC profile flashing/resetting issue on USB activity. Add these two bugs together and 1809 is pretty much annoyingly becoming useless!
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: Newest
-
Anonymous
2019-06-08T08:03:02+00:00 -
Anonymous
2019-06-08T07:46:48+00:00 Interesting. I also have 100+ VPN tunnels with SAVED credentials and they all work perfectly fine from the System Tray across multiple laptops/desktops with version 1903.
Are your 1903 use a fresh install of Windows or they were upgraded from previous Versions 1803/1809?
All mines are upgrades and the credentials were initially saved in 1803 or 1809 prior to upgrade.
-
Anonymous
2019-06-08T07:16:25+00:00 That doesn't make a bit of sense. I have over 100 VPNs, all with saved credentials, and all start perfectly if connected via the Settings panel without asking for a credential once as the login/pass are saved during creation. Not a single one connects from the menu.
-
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
-
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:
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.