cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4664
Views
0
Helpful
4
Replies

AnyConnect VPN Error

miked
Level 1
Level 1

I've deployed AnyConnect on Windows 7 clients, and they are throwing this message after few days of usage: "The VPN client driver has encountered an error."

Version: anyconnect-win-2.4.0202-web-deploy-k9

OS: Windows 7 Pro 64-bit

FW: ASA 5505

What seems to fix it:

1. Uninstall Any Connect Client then,

2. Remove C:\Users\User\AppData\Local\Cisco folder

After few days, this error comes back.

Is there permenant fix to this?

2 Accepted Solutions

Accepted Solutions

sjbdallas
Level 1
Level 1

For what it's worth: we found that if our users waited about 5 minutes after booting up their laptop to launch anyconnect, the problem didn't ocurr.  We've speculated that the HP wireless software was conflicting with it and that if we waited for it to finish it's startup sequence, the error didn't happen.

That said, our ultimate fix has been upgrading to 3.1.

View solution in original post

Click on version 3.1.02040 which is available on Windows version.

The latest 3.1.02043 is only for Linux, and at the top of the table it says:

Customers running AnyConnect and deploying HostScan or the Posture  Module on Linux must install this release. It resolves known critical  issues with signed modules. All other customers must deploy 3.1.02040

View solution in original post

4 Replies 4

Jennifer Halim
Cisco Employee
Cisco Employee

Please upgrade to the latest version of AnyConnect.

Jeneffer,

Where can I download the latest version? On your download page, I don’t see any that are Windows compatible.

Click on version 3.1.02040 which is available on Windows version.

The latest 3.1.02043 is only for Linux, and at the top of the table it says:

Customers running AnyConnect and deploying HostScan or the Posture  Module on Linux must install this release. It resolves known critical  issues with signed modules. All other customers must deploy 3.1.02040

sjbdallas
Level 1
Level 1

For what it's worth: we found that if our users waited about 5 minutes after booting up their laptop to launch anyconnect, the problem didn't ocurr.  We've speculated that the HP wireless software was conflicting with it and that if we waited for it to finish it's startup sequence, the error didn't happen.

That said, our ultimate fix has been upgrading to 3.1.