VPN not working on Windows 10 1903

Roll back Windows 10 to 1803 or 1809....PPTP and L2TP Build VPN Clientsdon't work with 1903 update.   Not sure what to do when Microsoft will forcefully push 1903 update. Best regards

Yup, 1903 is a joke. ICC profiles don't work right, VPN doesn't work except randomly, and many more enterprise functions that are half-cooked. Might be fine for consumers who don't use their computers for anything useful, but not ready for any kind of deployment in a business/enterprise/actual usage enivronment!

This is a joke that this is STILL a problem. I understand that some people are comfortable with a workaround but for business/enterprise, workarounds are not acceptable. I need the interface to work as intended. Are we still at a place where we can't use the VPN connection icon from the tray?

I don't want a solution to use a different method, I don't want to use some homebrew application, I don't want to have to direct the user to dig into menus just to connect to their VPN. I need a viable, repeatable SOLUTION to this problem. How are enterprise admins/IT staff doing this in large organizations?

One way to workaround this VPN issue in Windows 10 - 1903 (and it is a workaround NOT A FIX) is to use the VPN Connect option in the Windows Network Settings window to get the login screen to pop up.  And, NO setting the VPN to "Remember your Sign-in Info" is NOT a good solution.  This just causes another issue, because when the user's AD password expires, the user is not informed that the password is expiring/expired and the VPN connection still does not present the login screen.  VPN just throws a connection error and the End User is what do I do now.....  What they do is, call IT...  Like we need more work.  By the way, the default setting of "Remember my Sign-in Info" for the VPN connection is BAD SECURITY!!!!  We want the user to know their AD login ID and password and use it every time they access the network remotely!

We don't want End Users mucking around in the Network Settings, nor do we desire to teach them how to clear their VPN sign-in info when their AD password expires.

THIS IS A MICROSOFT BUG THAT NEEDS TO BE FIXED PURE AND SIMPLE!!!!!

Other VPN suggestions:

-Make NOT REMEMBERING the sign in info the default.  If an admin wants to change it, then it's a conscious decision to trade convenience for security. 

-Inform the End User when their password is expiring IN ADVANCE if possible across the VPN connection.

-If the password is expired, then automatically clear the sign-in info, TELL the End User, and then present a login screen.

I had this same issue with the "hanging" connection, and tried some of the suggestions. In my case, the issue is not with the connection, but there is a break in launching the "credentials window" from the hidden icons VPN shortcut.

I discovered I could connect through the Network Setting for my VPN; however, if I tried to connect to my VPN through the lower right corner (hidden icons ^), I received the "Connecting to.... VPN" but the credential window wouldn't open and it just hanged.