This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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?
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.
Hello everyone, recently I updated Windows 10 Pro from version 1809 to 1903and it broke my VPN PPTP and L2TP Windows Built-In. You need to have a right OS Build to make PPTP and L2TP VPN work again. I had Windows 10 version 1903 OS Build 18362.418 but you need to get OS Build 18362.449 that's when Windows Built-In PTTP and L2TP VPN will start working. Get this update 2019-10 Cumulative Update for Windows 10 Version 1903 for x64-based Systems (KB4522355)
Let me know if this helps.
The new KB did not resolve the problem for us either. Although our issue may be different. Here's how we set it up and what happens.
We create the VPN a little differently so that people can sign in to the VPN BEFORE signing in to the computer. The option will show as a new icon on the bottom left of the login screen AFTER pressing Ctl-Alt-Del. Click it and you will see a new sign on box for your VPN credentials. Benefit of this is GPs all execute just like normal along with login scripts.
1: Go to Network & Internet
2: Click on Dial-Up
3: Setup a New Connection
4: Connect to a Workplace
5: Create a New Connection
6: Use my Internet Connection (VPN)
7: Enter the address for your VPN
8: Give it a name
9: Check the box for Allow other people to use this connection. (This is what makes it work prior to logging on to the machine itself)
10: Click Create
11: Click Change Adapter Options (top right of window, stretch it out if you have to)
12: Right click on the adapter for your new Connection. Select Properties
13: Verify VPN address on the General tab
14: Select Security tab
15: Set proper type of VPN, for us this is Layer 2 Tunneling Protocol with IPsec (L2TP/IPsec) (We use the Meraki VPN)
16: Set the proper encryption, for us this is "Require encryption (disconnect if server declines)
17: Set the Radio button for "Allow These Protocols", then set Unencrypted password (PAP) NOTE: This IS encrypted. Very misleading.
18: Click on Advanced Settings
19: Set Radio button for "Use preshared key for authentication" and then enter your preshared key stored in your VPN server/router
20: Ok, close it all up.
For us this works one time. After the first use, if you use an IP for the VPN address it will be corrupted. Additionally, the Pre-Shared key will be gone and "Use certificate for authentication" will be selected. This nonsense has gone on now since 1809. It's a CLUSTER! Fix it Microsoft!!
Does NOT fix it for me.
Hmmm... supposedly, KB4522355 has a fix in it for the issue. Anybody else testing this to see if they actually fixed it?
Hi,
I confirm that KB4522355 resolve this problem.
Thanks
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!
