Windows 10 Creators Update 1703 (and April 2018 1803) VPN Not Working Fix

Update: Confirmed fixes April 2018 update as well.

Are you having issues connecting to VPN services on Windows 10 Creators Update 1703? If so then read on.

Having installed Windows 10 Creators Update everything was working well with no real issues for me other than needing to re-install the Dell Audio application that the Microsoft updated decided I probably didn’t need anymore. Anyway, only a minor inconvenience and it was fixed pretty quickly.

Until…..

One day when I needed to connect to a client over VPN, now this VPN was setup using the Windows VPN client with all settings set to auto and the vpn address set to vpn.myclient.com. It had been working perfectly on Windows 7, Windows 8.1 and up to Windows 10 Anniversary update. At first, I suspected maybe the client’s sysadmin was a little trigger happy and disabled my account, nope client confirms account and VPN access is enabled. Now a little suspicious I tried to connect back to my company using VPN (I almost never do this as there is little need these days with Office 365 and Internet-facing applications) and that’s not working either. So now I’m two for two VPN’s, not working.

Looking at the event logs show VPN not connecting with an Event Log ID: 20227


Figure: Out of nowhere VPN refusing to play ball on Creators Update

Searching the internet returned many suggestions, but in the end, the one that worked was “deleting” and redetecting the Miniport drivers. There are more nuclear options, but I was looking for the least nuclear option and luckily this worked for me!


Figure: Uninstall All WAN Miniport* drivers.


Figure: Right Click Network Adaptors and Scan for hardware changes.

So far so good and all VPN services are back up and running.

Note: I also have a Sophos VPN client but it wasn’t affected before or after Creators Update.

 

12 Comments

  1. Philip Ingram on July 30, 2017 at 11:24 PM

    Brilliant, worked for me. I had to reboot after this procedure as well.



  2. Melissa on August 9, 2017 at 10:25 PM

    worked after a reboot for me as well!



  3. Wayne on September 12, 2017 at 5:02 PM

    Awesome… I thought it was a problem at the work end, but stumbled across this, fixing the problem!! Thank you for sharing



    • Mehmet Ozdemir on September 15, 2017 at 8:54 AM

      No problem Wayne, good to see it helped someone else.



  4. Tim on September 21, 2017 at 9:39 AM

    my man! good work. worked



  5. D on October 18, 2017 at 4:41 PM

    worked perfect for me! many thanks!



  6. HK on November 14, 2017 at 11:40 PM

    worked for me too. Thanks man



  7. KEN YIU on December 1, 2017 at 5:43 AM

    Excellent work!!



  8. heros333 on December 14, 2017 at 12:33 AM

    działa



  9. Cesar on January 7, 2018 at 7:23 AM

    Exactly what I needed! YUDAMAN!



  10. Gerhard Kahler on June 4, 2018 at 11:26 PM

    Had the same issue after upgrade to build 1803. Your solution worked for me as well. Thank you!



  11. Thankful Tech on June 6, 2018 at 12:52 AM

    Please add 1803 to the title as it works for that as well Delete all Miniports scan for hardware changes and Restart.

    Thanks. Cheers