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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2020-08-05T13:41:04+00:00

    This issue not being on MS' radar would be quite a shock. We have a pandemic and VPN is more important than ever... 

    Oh i agree it is important as my boss wants a solution despite it being an MS issue. Its getting frustrating that we have to wait till august or September because it is such a hot item for us. I cant keep telling the boss  "We are waiting for MS but have this work around." 

    I would be happier if it was posted on the FP2004 issues page for tracking. 

    Thank's for the update, at least i can tell him Hopefully August - September time frame. 

    Dean

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-08-05T13:46:46+00:00

    Hi Anton, 

    Thanks for your message. I think you posted this earlier, right? But to be honest, I don't understand how this would solve the issue with the wrong credentials...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-08-05T13:48:57+00:00

    Try my batch file approach. At least it is a solution not perfect but does work.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-08-17T06:13:32+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.

    Can confirm!

    Removing all WAN Miniports and creating the VPN again seems to work ( L2TP PSK )

    Thnx Cary B

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-08-17T06:37:55+00:00

    Hi,

    Thanks for the info, but it seems on some machines that does not work.

    Also, the manual connect button also does not work without prompting you for the password.

    Microsoft really needs to fix this. Even removing the mini-port drivers did work, going through 500 + machines manually is not a good solution.

    Thanks

    Was this answer helpful?

    0 comments