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-09-17T16:29:08+00:00

    I'm not sure my problem is the same, but I think it's related.  We create our VPN connnections by going to the Network Center \ DialUp menu and create it there.  We create the connection so "Any User" can use the connection.  This allows the connection to be made prior to the user logging in to the machine which allows their login scripts to run, etc.  n icon gets placed on the bottom right hand corner of the screen, pressing it brings up a VPN login rather than the normal Windows login.  What I'm finding happening is if we put an IP address in for the VPN rather than a qualified name then thatIP address gets corrupted the first time someone tried to make a connection.  If you use a qualified name it just hangs forever on Connecting.  This of course causes the connection to fail.  We find that manually connecting through the VPN menu in the Network Center works nicely as long you have not tried to use that connection prior to login.  Once it is corrupted it stays that way.  Anyone seen a fix for this?  This happen to anyone else? I guess I should note that we've only seen this happening with 1903, however when we updated to 1903 doesn't seem to have anything to do with the issue, it's there regardless of when the update was run.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-09-17T11:27:18+00:00

    This is not a solution - i can't rollback 1000 systems and update again...

    An interesting case.

    It helped me out of four (all of them had a problem). Windows Home in Polish.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-09-16T12:24:30+00:00

    Yes, we know this but for most end users, they are used to finding their VPN where the wifi connections live.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-09-16T12:23:27+00:00

    Agreed, this is ridiculous, I read that here on Friday and thought, wait, Microsoft can't actually fix it with the update? I'm supposed to roll back to 1809 and then use the "new" 1903 that isn't all $%$#@%$ up?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-09-16T09:19:29+00:00

    An update from a week ago solved the problem.

    You need to roll back Windows to the previous version and update again.

    Hi SlawekSidor, 

    This is not a solution - i can't rollback 1000 systems and update again...

    Was this answer helpful?

    0 comments