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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-11-18T15:28:48+00:00

    New trial, new NO solution.

    I have installed 20H2, uninstalled WAN miniport drivers, deleted entry connection, restart, drivers automatically installed, defined new entry connection... same BAD result, trying connection to VPN from the client stais locked in "connecting to....."

    Looked for new updates... only the Net framework one. Tried to install the November cumulative update, "already installed in this system".

    Framework and antivirus stopped, same, no connection.

    So, again VPN integrated server doesn't accept PPTP connections. Restored 1909 version, it works again.

    Any other idea of help?

    Regards

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2020-11-15T15:37:36+00:00

    No way :(  , I updated my windows 10 to 2004, then latest SSU, then tried KB4586781 that seems to be November cumulative update, this last one said it was already installed, uninstalled WAN Miniport drivers, deleted incoming connection, restarted system, redefined the incoming connection using PPTP...

    Same result

    VPN from the client locks at "connecting to...." message

    Again, stepping back to 1909 and keeping the client at 2004, VPN works again.

    Any other idea of help? Should I try 20H2 if there is any way to do it?

    Thanks

    regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-11-15T08:53:14+00:00

    Thanks for your answer.

    After Updating to 2004, I tried to look for additional updates, but the only one that came was for NET.

    Looking at the client, it seems that there is an additional one: KB4586781, I will do an additional try today and try to download the independent update for that one and look if it can be installed and if it solves the problem.

    Regards

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-11-15T08:11:45+00:00

    After the November updates, the problem no longer exists.  I haven't moved to 20H2 yet.  It was some kb installed in the November updates.

    Was this answer helpful?

    0 comments