I got 99 problems, and my VPN is one…
I have been delaying using Windows 8 as long as I can. I think a lot of people have…
Upon initial reviews and playing with it at stores, I was not hugely impressed with what I saw (ex. I enjoy typing to search, but I will always want some form of a Start Button). But part of working in the IT field requires adapting new technology, so I bought a new Windows 8 laptop this weekend knowing it would be a good learning experience. I plan on writing more about these experiences, so feel free to subscribe to our blog by filling out the information in the top right corner and follow me if you want to see more. But, for now, let’s talk about the first major hurdle I encountered.
The Cisco VPN Client Error Reason 442:
I fiddled with settings for a little while, thinking I must have configured it wrong. This didn’t fix anything, in fact I wound up destroying my WiFi adapter driver profile which required removing the adapter from Device Manager and reinstalling it. Which was a bit annoying…
I also reinstalled the VPN client thinking it needed a setting I missed, or compatibility mode. Nothing worked for about two hours of playing with it (most of which is also learning to navigate around Windows 8). So without further ado, let me save you from all of this headache.
To the Google!
This problem is caused during the installation of the Cisco VPN client. When you try to connect with Cisco VPN client, it attempts to enable the virtual adapter on your computer using the adapter’s name. This name is stored in the registry under an incorrect registry key after install. The Cisco VPN client fails to enable the adapter resulting in Error 442 because this Key contains an incorrect DisplayName value. So to fix this, we head into treacherous waters…
Ready for Regedit
Important: Editing the registry is a potentially dangerous task. Do not attempt unless you are confident in your ability to edit the registry properly. To avoid problems, I recommend creating a backup first. Save some place easily accessible and name it something you will remember later.
You can manually resolve this issue by using regedit.exe to edit the registry and remove all the garbage in front of the correct DisplayName value. The key in question is located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CVirta.
For x86, change the value data from “@oem#.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter” to “Cisco Systems VPN Adapter”
For x64, change the value data from “@oem#.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “Cisco Systems VPN Adapter for 64-bit Windows”
You should not need to do a reboot, but you may need to disable the network adapter for the VPN client to work properly.
Open Control Panel – Open Network Settings – Check Adapter State
The adapter will be enabled when it is in use by the client. If it is enabled now it might cause conflicts again, so turn it off. Good luck, and get back to work!