20H2 Build 19042.572 is the October Update that just came out. Looks like they're going to patch 20H1 (version 2004), and I would think 20H2, in the next cumulative updates.
Upgrade to Windows 10 2004 (VPN L2TP fail autoconnect)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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.
107 answers
Sort by: Oldest
-
Anonymous
2020-10-26T15:55:03+00:00 -
Anonymous
2020-10-26T16:13:32+00:00 I've replied to them and asked them about 2004 and 20H2. We are going to roll out 20H2 in the next month so we need it to be fixed there. But I guess if it is fixed in 2004 it will also be fixed in 20H2 as both versions share the same foundation. Will keep you posted.
If anyone knows where to get the CU preview please let me know.
BR
Michael
-
Anonymous
2020-10-26T16:52:30+00:00 Very good. Thx a lot!!!
-
Anonymous
2020-10-26T17:08:36+00:00 According to the Windows Insider blog, this should be fixed in the October 22nd patch for 20H2: https://blogs.windows.com/windows-insider/2020/10/22/announcing-windows-10-insider-preview-build-19042-608-20h2/
It's likely this is only showing up for those in the Release Preview ring, but if past experience is anything to go by, this should wind up in the November Windows Update release for both 20H1 and 20H2. There's also a chance it shows up in the out of band patch release either this Tuesday or next Tuesday for 20H1 before the regularly scheduled release.
-
Anonymous
2020-10-28T13:10:03+00:00 We have about 1000 employees using VPN, some solved the problem, updating to 20H2, but others not.
We using two authentication radius servers, NPS and FreeRadius, if I use the user that the server authentication is NPS, works fine, but If I use the user that server authentication is FreeRadius, doesnt work.