Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.
Patch Tuesday: KB3023607 Breaks Cisco AnyConnect, Here's a Fix
Problems with Cisco AnyConnect after Patch Tuesday? You're not alone.
Rod Trent
February 13, 2015
2 Min Read
If unreadable fonts and a broken PowerPoint aren't enough to get your hackles up this week, there's yet another patch that is causing considerable problems. KB3023607, which is the update designed to change the way the Transport Security Layer (TLS) works to eliminate the Poodle vulnerability, is causing headaches for users of the popular Cisco AnyConnect VPN application.
I use the app constantly to connect to the mother ship. This morning, in fact, I was all set to do my expenses (which is a hated, laborious task anyway), but was met with the following error when attempting to connect.
The problem has been verified by Cisco and the company is reported to be working with Microsoft for a permanent fix. But, a temporary fix is also available that includes allowing Windows to configure the compatibility for the application. The following is an expanded and tweaked version of the fix Chris Tierney posted to his blog: Cisco AnyConnect "Failed to initialize connection subsystem"
To fix it, do this:
On the Windows Taskbar, right-click on the Cisco AnyConnect icon and choose Quit.
Open File Explorer and navigate to: C:Program Files (x86)CiscoCisco AnyConnect Secure Mobility Client.
Find vpnui.exe, right-click on it, and then choose the Troubleshoot Compatibility option.
Choose Try Recommended Settings.
Click Test Program (notice that Windows chooses Windows 7 compatibility mode in case you have to set it manually). Choosing to "Test the Program" will launch the Cisco AnyConnect client, giving you the chance test logging in. It should work.
Once it's proven that Cisco AnyConnect works, choose to save the settings. If it doesn't work, the troubleshooter gives you the options of trying again with different settings. The Windows 7 compatibility worked for me and I run Windows 8.1.
Program Compatibility Troubleshooter will give you a final report. Close the troubleshooter and you should be good to go.
Now that it's temporarily fixed, I just have to build up the gumption again to finalize my expenses. The temporary fix is way easier than working through my obvious character flaw.
About the Author
You May Also Like
.png?width=700&auto=webp&quality=80&disable=upscale)