VPN not working on Windows 10 1903

FYI:

Ryan Dixon and DocHoliday666 provide the answer but I wanted to add as well.

SUMMARY

VPN will not provide username and password prompt when clicking WiFi system tray icon and selecting VPN Profile to Connect (RasMan and update 1903)

Explain in more detail (optional)

ISSUE:

If you click on the Wifi icon on the system tray then select a VPN Profile name you want to connect to, you can click Connect but no username and password login prompt box will show up. Rather a spinning circle will run for minutes until it times out. After two hours with Microsoft support and escalated to Senior Systems Engineer I was provided with this bugs work around for Windows 10 Home. I feel silly as I wish I could have done the steps below soon after update 1903.

WORK AROUND

Open Network and Internet Settings -> under Network and Internet click on VPN -> select VPN Profile click Connect ->the Windows Security window will show up to Sign In enter your credentials.

AFFECTED VPN PROTOCOLS

L2TP over IPsec

PPTP

IKE

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.

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.

not an appropriate solution.  IT needs to move forward, not backwards.

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