This is an old article.


We keep articles like this online for historical purposes. Please note that it may contain outdated information or broken links. For up-to-date information on this topic, visit our Service Guides.


Microsoft Security Patch Causes Cisco AnyConnect Report Errors


Updated February 20, 2015

There have been reports of a "Failed to initialize connection subsystem” error received while using Cisco AnyConnect to establish a virtual private network. The errors began with the February 2015 Microsoft security patch.


Update: February 20, 2015

Microsoft has released a "fixit" to correct the regression in the February 10, 2015 patch. The fixit is accessible by following these instructions.

Once the fixit is installed, Cisco recommends rebooting your PC or log off/log on,  as you need to fully restart the AnyConnect service (not just the User Interface).

The fixit Microsoft has released is not a fix for the OS regression.

Microsoft is planning to release a Windows Update patch on March 10, 2015 for this problem. Microsoft's dates are subject to change.

About the Error

The error affects Windows 8.1 computers running Anyconnect clients v3.x and x4.x, and using any of the following virtual private networks:

  • Off-Campus VPN
  • Departmental VPN
  • Administrative VPN

On-campus services that could be affected:

  • Faculty or staff using two-factor authentication for HUB administrative functions 

Off-campus services that could be affected:

  • iprint anywhere
  • My Virtual Computing Lab
  • UBfs
  • UBUnix

UBIT does NOT recommend you uninstall the Windows update, as it contains important security fixes for Internet Explorer. Please wait for the Windows fix to be issued.

This article will be updated as more information is available.