Client VPN Error After January Windows Updates

[Darcon]

After patching a couple machines with the January Windows Updates I found that our Meraki Client VPN no longer works. I get error 789 in Windows Event Viewer, and nothing at all in the Meraki Event Log.

This is the error displayed when attempting to connect. It errors out within a second of hitting connect, doesn't even prompt for creds.

We've had AssumeUDPEncapsulationContextOnSendRule set to 2 for some years. I tried removing / rebooting / re-adding this key; same error. I also tried switching our PSK to a key without special characters, same error.

I have confirmed this on 2 different machines. Unpatched machines continue to connect without issue.

Anyone else run into this today?

[Christopher Adlam]

Perfect, so go into AnyConnect Settings and setup AnyConnect, then download and use that client instead. That prevents you from having to deal with Microsoft breaking things with updates, as you use the Cisco AnyConnect client instead.

[Rules_2301]

oh Yeah, thanks.

[Mike6116]

You need to have the windows update 21Hh2 and 2 optional updates that come after it, then you need to reconfigure tue vpn connection and there you go.... it will connect without any issue...

[giacomos]

Hey team,

For those still encountering VPN issues with the Windows client, I would recommend always checking the VPN Adapter settings, as described in this KB . Microsoft has a terrible habit of resetting those checkboxes almost every Patch Tuesday, although if you are leveraging GPOs in your Active Directory environment to push the settings you may be OK.

Just to avoid any shattered dreams, please remember that the use of Anyconnect requires you to have a valid license (as per this KB).

If you don't have a license yet, please get in touch with your partner of choice and your Cisco Meraki sales representative and they'll be happy to assist. 😁

Have a great day!

Giac