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-10-22T08:20:01+00:00

    I solved it by deactivating the "Automatically use my Windows log-on name and password (and domain, if any)" option.

    It seems to work in contrary, re-activating it Windows asks me for the password when I try to connect to the VPN.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-19T03:29:56+00:00

    Hi AyrA.ch, your registry change that you suggest in your Data Protection API post seems to have fixed my VPN issues.  For anyone else interested in trying this then here's the link and the registry edit that seems to have resolved the problem on my PC.

    https://answers.microsoft.com/en-us/windows/forum/windows_10-security/data-protection-api-dpapi-seemingly-broken/3f37f1dc-2e74-4ee1-8de8-84a1923082a6 

    Potential solution:

    1. Open the registry editor
    2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb
    3. Create a DWORD value named "ProtectionPolicy" and set it to 1
    4. Reboot

    UPDATE:

    I spoke to soon.  Although this appears to have improved my VPN experience it has not fully resolved the problem.  Here's hoping the MS update mentioned in other posts fixes all our woes.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2020-10-17T15:45:17+00:00

    I have the same issue and (in my case) was able to trace it back to the data protection API. A whole lot of other things are also broken, and no error is logged anywhere: https://answers.microsoft.com/en-us/windows/forum/windows\_10-security/data-protection-api-dpapi-seemingly-broken/3f37f1dc-2e74-4ee1-8de8-84a1923082a6

    If anyone is willing to test, try this tool on a broken machine: https://github.com/AyrA/DPAPITest

    It will not fix your problem, it merely checks if the data protection API is responsible for it, or if you have a different issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2020-09-15T19:52:45+00:00

    Just want to add in here that I've been trying to solve this issue for MONTHS and literally nothing is working. 

    None of the fixes or workarounds presented in this thread are working for me. I am able to connect to my l2tp vpn perfectly fine with any mobile device or my OSX clients but not a single one of my windows clients can connect (tested on a custom built pc as well as a SP4 - both fully up to date).

    Every work around presented has resulted in the same error and inability to connect to the remote network. I haven't been able to connect my main work-from-home pc to my work network since June. I've resorted to my super old macbook pro because it doesn't have this malfunction. 

    It's baffling to me that Microsoft can't solve this or address this in a timely manner.

    Was this answer helpful?

    0 comments
  5. 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