Upgrade to Windows 10 2004 (VPN L2TP fail autoconnect)

Anonymous
2020-06-02T14:15:49+00:00

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

Windows for home | Windows 10 | Internet and connectivity

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.

0 comments

107 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-09-04T14:17:04+00:00

    I tested latest updates and insider preview builds:

    • Win 10 2004 (cumulative updates 2020-08, build 19041.450) - issue occurres. VPN ask for password when try to connect via GUI. Connecting via CMD (rasdial vpnname) works without asking for password.
    • Win 10 2004 (lSeptember 3, 2020—KB4571744 Preview, build 19041.488) - issue occurres. VPN ask for password when try to connect via GUI. Connecting via CMD (rasdial vpnname) works without asking for password.
    • Win 10 2004 (September 8, 2020—KB4571756 (OS Build 19041.508) - issue occurres. VPN ask for password when try to connect via GUI. Connecting via CMD (rasdial vpnname) works without asking for password.
    • Win 10 20H2 (insider preview, build 19042.450) - issue occurres. VPN ask for password when try to connect via GUI. Connecting via CMD (rasdial vpnname) works without asking for password.

    - Win 10 2004 (insider preview, build 20201.1000) - issue doesn't occur. VPN connect without asking for password. Connection works both for GUI and CMD.

    Unfortunately but at this moment it looks like we don't get fix for that earlier than 20xxx build (Win 10 21H1?).

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-07-20T16:49:33+00:00

    I had this problem. Tracked down that if I go to Device Manager and remove all the WAN Miniport protocol versions, Scan for Hardware Changes and let Windows re-install all the Mini port drivers, It seems to be working now. Hope this helps. Had to recreate the VPN connection. Using L2TP to Meraki.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2020-06-25T11:26:17+00:00

    Yo!

    Found some easy workaround that works!

    Create a .bat or .ps1 file with

    rasdial "Your VPN Connection name"

    and it works with automatic user logon settings as before!

    So the BUG is after 2004 update on default Connection window when pushhing "Connect" only, but not overall with settings.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-10-30T21:36:06+00:00

    This problem appears to be fixed as part of Windows 10 KB4580364 Preview.  The changelog for that KB includes this:

    ·         Addresses an issue with virtual private network (VPN) connections that use Secured Password (EAP-MSCHAP v2) for authentication and have enabled the “Automatically use my Windows logon user name and password” property. When you connect to this type of VPN, an authentication dialog box incorrectly prompts for your credentials.

    https://support.microsoft.com/en-us/help/4580364/windows-10-update-kb4580364

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-06-04T04:18:04+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments