Symptom: You receive the following error when trying to establish a connection with the Cisco AnyConnect client on Windows 8 x64.
Solution:
Option 1: PowerShell Method
- Go to the Windows 8 Start screen, search for PowerShell, Run as an Administrator
- Execute the following powershell command
- Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\vpnva -Name DisplayName -Value ‘Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64‘
- Set-ItemProperty -Path HKLM:\SYSTEM\CurrentControlSet\Services\vpnva -Name DisplayName -Value ‘Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64‘
- Exit and reopen the Cisco AnyConnect Program
Option 2: Registry Editor GUI Method
- Go to the Windows 8 Start screen, search for regedit, right click Run as administrator
- Navigate to the following registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpnva
- Double cick on the DisplayName value and replace the value with Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64
- Exit and reopen the Cisco AnyConnect VPN client
Thanks for posting this! Still stuck with the cryptic "The client agent has encountered an error." but it worked great in 7860. The client hangs until terminated with Task Manager. Back to the Windows 7 laptop until I can resolve.
Nice job though!
Hey Allen,
As another side note, I have also seen antivirus products affect the way the client works in Windows 7 up. In particiular, we saw the scanning engine of Microsoft's System Center Endpoint Protection prompt a lot of issues with the Cisco VPN clients. Adding an exclusion to the program files folder did the trick for us.
Hope this helps!
Jack
The issue could be that the VPNagent is referencing an old VA driver to VaConn. The workaround is to uninstall the client, remove all files and references and then reinstall the driver.
If you look up in Anyconnect DART, if you see that it can't find the vpnva64.sys, that's the problem. You'll want to ensure your ASA has the updated AnyConnect too. The latest version that fixes this is 3.1.06079.
If you have a CCO, you can find this known bug under CSCup30116.
Appreciate the notes CiscoGuy! 🙂
Jack