Answered by:

Question

Cisco VPN clinet is re-installed after upgrading to Windows 8 release preview from Windows 7. When I tried to connect to my University network using Cisco VPN, the error message appears saying VPN Client failed to enable virtual adapter. I have never had
this error in Windows 7. Can you please look into this and suggest some solution? I would really like to work from home using Cisco VPN Client on Windows 8 release preview.

You guys have done a great job in re-imagining windows to a very new level. I am loving every bit of it. Thanks for your efforts.

Friday, June 22, 2012 4:41 PM

Answers

Thank you so much for the link of thread. The solution of editing registry provided by Mr. Raman worked very well. Now, I am able to connect using Cisco VPN Client. For others benefit, I am pasting Mr. Raman's solution below.

*************************************************************

Hi Everyone,

Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –

· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto "%;" i.e.
o For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”
o For x64, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to "Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again

All replies

As the issue is related to Cisco VPN client, it is also recommended that you contact Cisco Support for help and see if there will be a new version which will fix the issue or if they have other constructive suggestions:

Thank you so much for the link of thread. The solution of editing registry provided by Mr. Raman worked very well. Now, I am able to connect using Cisco VPN Client. For others benefit, I am pasting Mr. Raman's solution below.

*************************************************************

Hi Everyone,

Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –

· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto "%;" i.e.
o For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”
o For x64, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to "Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again

Thank you so much for the link of thread. The solution of editing registry provided by Mr. Raman worked very well. Now, I am able to connect using Cisco VPN Client. For others benefit, I am pasting Mr. Raman's solution below.

*************************************************************

Hi Everyone,

Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –

· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto "%;" i.e.
o For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”
o For x64, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to "Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again

Thank you so much for the link of thread. The solution of editing registry provided by Mr. Raman worked very well. Now, I am able to connect using Cisco VPN Client. For others benefit, I am pasting Mr. Raman's solution below.

*************************************************************

Hi Everyone,

Just to update, the legacy Cisco VPN client (5.0.07.0440 for x64, 5.0.07.0410 for x86) is working for some people. You need to apply a small workaround as explained below –

· Open Registry editor by typingregedit in Run prompt
· Browse to the Registry Key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\CVirtA
· Select the DisplayName to modify, and remove the leading characters from the value data upto "%;" i.e.
o For x86, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to "Cisco Systems VPN Adapter”
o For x64, change the value data from something like "@oem8.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to "Cisco Systems VPN Adapter for 64-bit Windows”
· Try connecting again

I have sucessfully installed and I am using Cisco VPN client on 32bit version Windows 8. But not on 64bit version (5.0.07.0440-k9-X64 and 5.0.07.290-X64). Client is conected, routes seems to be o.k. But I can not reach remote network. I cannot reach
dns or any other IP address.

I am not using any other 3party AV or firewall for this purpose.

I have 32bit client installed on Virtual box XP machine inside my W8 64bit machine, I can work, but I am very disatisfied with such solution (W8= hypervisor for XP :o).

I have sucessfully installed and I am using Cisco VPN client on 32bit version Windows 8. But not on 64bit version (5.0.07.0440-k9-X64 and 5.0.07.290-X64). Client is conected, routes seems to be o.k. But I can not reach remote network. I cannot reach
dns or any other IP address.

I am not using any other 3party AV or firewall for this purpose.

I have 32bit client installed on Virtual box XP machine inside my W8 64bit machine, I can work, but I am very disatisfied with such solution (W8= hypervisor for XP :o).

The registry editing workaround described earlier (email from Raman quoted) made Cisco VPN client 5.0.07.0440 worked for me under Windows 8 Pro from early November 2012 until December 9, 2012. The client was notably slow to connect, but would connect,
and worked. Beginning yesterday, it would still connect, but I could not reach any IP addresses, not even my home router. I don't know whether something changed in Windows 8 or in my institutions's VPN configuration. I installed ShrewSoft 2.1.7, imported the
Cisco client files, and it works fast and apparently flawlessly.

hi, this is working when i am using LAN or WIFI connectivity but it is nt working when i am connecting using a dongle(modem) Vpn conection is establishing but after that packets are not sending and receiving on virtual adapter

Thought I had this fixed. But after working for a while, now the VPN will not receive packets.

On a remote network, a Win7 PC conects fine and can ping all of the main network

a Win8 machines appears to connect fine and gets an IP address, but statistics show only out going traffic. If the remote Win8 machine is pinged from the main network. Packets show as being received on the WIn8 but the ping fails.

Hi all, I just went through this and wanted to drop in a note. If you do not have the CVirtA folder under your registry (and I did not either), it could have been deleted during the upgrade. There are two ways to get it back, import that folder
from a computer that has that folder still on it. or Re-install the Cisco VPN. I did the latter.

I uninstalled the Cisco VPN Software, re-installed, it came up with all my connections and the same error. This time I went into regedit and the CVirtA folder was there. Corrected the display name as detailed above, and it started working.

I saw a lot of people stating that they didn't have the correct registry path for this. I can only assume it is due to different versions of Cisco VPN or perhaps that some users are upgrades from Win7 and others are clean installs. Regardless, I didn't have
the listed registry path either, but I still found the key in another location and performed the workaround.

For me, the key was located here:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpnva

Otherwise, the fix was the same. I just removed the extra garbace in front of the text "Cisco Systems VPN Adapter for 64-bit Windows" and I no longer got driver error messages when attempting to connect.

The correct key inside 'services' is NOT CVirtA but something like 'vpnva'. I had to do that twice: First in Developer Preview and then in Release Preview.

Hi,

I found the my string was different to those mentioned and found the actual issue is the garbeled text infront of the string in the HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\vpnva

e.g. @oem4.inf,%vpnva_Desc%;Cisco AnyConnect VPN Virtual Miniport Adapter for Windows x64 becomes Cisco AnyConnect
VPN Virtual Miniport Adapter for Windows x64 by removing the first part. I can presume the string changes for different versions etc. So I would suggest a. backing up your whole string prior and b. keeping your string but removing the first part only.

I did this and straight away it worked.

While the answer from Raman was not complete, it certainly was well on the right track to resolving the issue.

Here is the almost official Cisco supported solution for this issue. Cisco came out with a new device to compete with the SonicWall TZ200 series called an ISA550. With Cisco's help we have implemented this device in front
of UC540s. Windows 8 users can now use the latest version of Cisco AnyConnect VPN client and connect to the internal network. We haves used IP Communicator on a Windows 8 Tablet connected to cell phone hot spot VPN into the ISA550 and it works
great.

Contact me if there is any interest in the solution. It is fairly complex and only two Cisco techs know how to do it. One tech told me it was impossible to do, so be persistent. The ISA550 is not CCA compliant so this adds to the challenge

Microsoft is conducting an online survey to understand your opinion of the Technet Web site. If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.