For me the following old solution from Microsoft worked:
Setting the Value to "2" and rebooting, the VPN connection could be established an authentication worked
Let me Know if it worked.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Good evening.
After upgrading to Windows 10 2004, the L2TP / IPSEC VPN using MS-CHAPv2 with the option "Automatically use my Windows log-on name and password (and domain, if any) no longer connects automatically. Note that the computer in question is in an AD domain and in the previous version it was working without problems (the connection was established with the Windows credentials.
It turns out that now, in this version, it says that the user or password is wrong and shows the dialog window for entering the password. I put the same one I use for windows login and the connection is established. I wanted this to be done automatically and, if not possible, I would like to understand technically why this is happening.
Thank you.
Ricardo
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.
For me the following old solution from Microsoft worked:
Setting the Value to "2" and rebooting, the VPN connection could be established an authentication worked
Let me Know if it worked.
Same issue here, we are using IKEv2 (AlwaysON), It was working fine on Win10 1909, 1903 and 1809.
Hi,
I have the same issue with a computer upgraded from 1909 to 2004.
I tried to delete and recreate the VPN connection but the problem persist.
No, I have no clue but I wanted to add that we are many that have this issue so it might get noticed by Microsoft.
I have also sent in a bug report with the suggested feedback hub app since this is very annoying for all our users.
Just to inform that there are more users having this issue.
We have the same problem with all our computers, around 100, after the Windows 10 2004 update.
Do you already know where the problem is?