Just for test try disjoin from domain and rejoin and see if problem persist?
Check event viewer and see if there is any log files like network or DNS failure?
Report this issue through Feedback Hub app.
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.
Just for test try disjoin from domain and rejoin and see if problem persist?
Check event viewer and see if there is any log files like network or DNS failure?
Report this issue through Feedback Hub app.
I have the same issue and it appears that it applies to all VPN types. I have two Microsoft VPN's setup for work. One is PPTP and the other is SSTP. Since upgrading I am now getting prompted on both types, this has never happened before. When connecting to the VPN on logon it all works as it always did, seamlessly. Once windows is up and running and you attempt to connect while at the desktop you will always get prompted for your password.
I can't find any DNS errors and this is happening on more computers. I didn't disjoint and join the domain because it's not just being applied to one machine.
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.
The strange thing is that in the dialog window it says that the user or password is wrong. If it was a security requirement, I would not display this message. I think!