Tuesday, April 11, 2017

[SOLVED] Cisco VPN Client on Windows 10 (Including the new build April 2018 Update) - This works!

***Updated 05/14/18 **
***Please see my edits below for notes on builds 1803, 1709, and back.**

Here's how to get it working in 2 easy steps:

1. Download and install the Sonicwall 64-bit VPN client from HERE (as of this writing).

2. Install the Cisco VPN client.  Edit:  If you get an error that it cannot run on this operating system then just extract the .exe file using WinRar or a similar program and run the .msi file.  Problem solved.
3. Perform a quick registry edit: (This step is almost always not optional any longer)
  • Open Regedit
  • Browse to the registry key HKLM\SYSTEM\CurrentControlSet\Services\CVirtA
  • Select the display name to modify:
    • x86 - "@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter" to "Cisco Systems VPN Adapter"
    • x64 - "@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows" to "Cisco Systems VPN Adapter for 64-bit Windows"
  • Reboot

The first two steps worked for me without the need for registry edit.  I checked and the settings were already spelled correctly on my machine.  Full disclosure my systems are clean Windows 10 installs without being upgrades.

Without installing the Sonicwall client first you will get Error 433 after trying to connect.  Checking the logs shows that it cannot download the key to complete the secure connection.

What happens is that the Sonicwall client adds the DNE Lightweight filter network client on the machine.  I tried getting it directly from Citrix and installing it that way but was unsuccessful.

Using this method you can now get some more use out of the Cisco VPN client.  If you prefer you can uninstall the Sonicwall client afterward.  I've been told by several people that the DNE software remains even after the Sonicwall client is removed.

Build 1803

WARNING:  You should uninstall the Cisco VPN client prior to running this upgrade so repairing it afterward will make it much easier.  All of the steps above still work on this latest build 1803 (OS Build 17134.1).  No other edits required to keep it running.

Build 1709 Fall Creator's Update

WARNING:  You should uninstall the Cisco VPN client prior to running this upgrade so repairing it afterward will make it much easier.  All of the steps above still work on this latest "Fall Creator's Update" upgrade of Windows 10.

Build 1703 Creator's Update EDIT: Updated 04/11/2017

WARNING:  You should uninstall the Cisco VPN client prior to running this upgrade so repairing it afterward will make it much easier.  All of the steps above still work on this latest "Creator's Build" upgrade of Windows 10.

Now for the not-so-fun-details.  I didn't uninstall prior to the upgrade and proceeded to spend the next 30 minutes clearing out registry entries until I finally found the right one to let me reinstall the product using the .MSI file.  After doing that, and making the registry edit, my VPN client is again working properly.

Version 1607 Build 14393.10 EDIT: Updated 08/03/2016

All of the steps above still work on this latest "Anniversary" build of Windows 10.  As with the 1511 build mentioned below, you will have to run a repair on the program or just do a clean install to get it working because Microsoft yet again determined that they would control which program we use.

You can go HERE to download the latest version of the media downloader and get version 1607.

And not to be left out HERE is a link to all of the new features in 1607 for IT pros.

As I update my Windows 10 machines I'll post updates if there are any issues or errors I run across with this build.  As I always say.... good luck.

BUILD 1511 EDIT: Updated 1/20/2016

I'm getting a lot of feedback about networking being broken after 1511.  I would highly advise you remove the Cisco VPN client and Sonic Global client software prior to installing build 1511.

I have now upgraded three different systems to 1511.  By removing both the Sonicwall and Cisco VPN software first, I had zero issues with it working properly afterward.

However, if the upgrade went through already, here's what you can do to help mitigate these issues.  There's no guarantee this is going to work but I have had two instances where the Cisco VPN software was removed by the 1511 upgrade and I was able to get it working by following the next steps below:

First just reinstall the VPN client using the .MSI file and not the .EXE file.  This will bypass Windows 10 checking the compatibility as I listed at the top.  Next just make the registry edits again and you'll be good to go.  After the registry edits, I have not had to restart but you can if you feel the need just to be sure.

If this does not work as an extra effort you will need to reset all networking on Windows 10.  Luckily this is pretty easy to do.

- Open an administrator command prompt
- Run "netcfg -d"
- Reboot and reconfigure your networking as needed.

Here's a sample of the output you will see:

Microsoft Windows [Version 10.0.10586]
(c) 2016 Microsoft Corporation.  All rights reserved.

C:\WINDOWS\system32\netcfg -d
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
SetupDiCallClassInstaller Erorr: 0x6
NetSetup object deleted successfully on MUX
Successfully commited changes to the registry
Successfully commited changes to the registry
We are going to reboot now to complete the clean up. Save all of your work.

Press any key to continue…

I hope this helps out with the additional headaches caused by 1511.  As always if I find any more useful information with future updates to Windows 10 that affect this software, I'll be sure to update the post.

Good luck!





312 comments:

«Oldest   ‹Older   201 – 312 of 312
JavatarSimone91 said...

Thank you very much for such useful info! I had the similar issue after version 1511 update but thank god your solution worked out.

Anonymous said...

If you made the upgrade and did not uninstall both softwares, you should uninstall both of them before you try again. Since the virtual adapter is not created if you just uninstall-install the VPN. So the steps after the upgrade:
1. Unistall SonicWall;
2. Unistall VPN;
3. Reboot;
4. Install SonicWall;
5. Install VPN;
6. Fix the registry;
7. Enjoy!

Anonymous said...

Marvelous! Thank you so much!

Anonymous said...

got an error like "not connected" help me.

BQ said...

Worked for me. Thank you so much

Anonymous said...

I have tried all the recommended solutions here and no joy!!

But root problem was in my NetComm router. Fixed the issue on the router to open UDP?TCP port 500 as mentioned in http://www.netcommwireless.com/sm/common-questions/nb6/vpn-client-issues

Anonymous said...

Netcomm router was the cukprint in my case after trying all the solutions mentioned here.

So My solution was to enable TCP/UDP port 500 in the router
http://www.netcommwireless.com/sm/common-questions/nb6/vpn-client-issues

Rahul Surendran said...

Thanks a ton. I did the same steps one by one and lo! It worked.

noman dudda said...

Thanks a lot!

Unknown said...

Thanks for the write up. I have successfully connected windows 7 and mac OS X to ASA VPN. I"m having hard time to getting windows 10 to connect. I'm guessing the transform sets are not correct. would you be able to hint me which transform sets would work with windows 10.

I have the following configured.

crypto dynamic-map outside_dyn_map 20 set ikev1 transform-set ESP-3DES-SHA ESP-3DES-SHA-TRANS ESP-3DES-MD5-TRANS ESP-AES-128-SHA-TRANS
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside

thank you.

Michael Baker said...

My system came with the 1511 Win 10 build. Installed both Sonic wall and then Cisco VPN using the msi. Made the registry change and voila it worked fine. Am now able to use my new laptop for work. Thank you so much for figuring this out. Many of my customers still have old Cisco VPNs and now I can still log into their VPNs when they need help

Jorge said...

Thanks a lot, it worked on a Windows 10 upgrade installation.

With only the first two steps got an 442 error code, after changing the registry key it worked just fine.

Anonymous said...

Thanks for the wonderful post. I found that installing the Citrix DNE installation and using the MSI installation for the VPN Client, along with the registry edit worked like a champ. However the one drawback that I noticed is that regardless of the provider order in advanced networking, the VPN client adapter would not take precedence. This left DNS lookups falling on the local adapter and not the vpn adapter. So no private addresses could be resolved.

Borrowed from another page the fix is simple:

Open Network and Sharing Center.
Click Change Adapter Settings.
Right click on Local Area Connection and select Properties.
Double click on Internet Protocol Version 4.
Click the Advanced button.
Uncheck Automatic Metric, and enter a number such as 50.

Repeat these steps for the VPN Connection (Local Area Connection 2), except make the metric number LOWER, such as 1. Note that you will have to connect to a VPN server before you can adjust the IP Version 4 settings.

This forces the VPN connection to take priority over the local connection and then DNS lookups are restored correctly.

Anonymous said...

Thank you very much :)

Anonymous said...

Successfully installed and connected to my company's VPN but as soon as I do, internet connection drops out.

Any ideas?

Unknown said...

Thanks, Followed the post step by step and got VPN working on windows 10.

Anonymous said...

Works perfect for me, but I needed the three steps to get it working.
Thanks

Anonymous said...

Thanks! Worked fine for me on installed (not upgraded) Win 10 Pro 64-bit. I did have to do the registry clean-up.

Anonymous said...

Hi,I have win10 pro x64 build1511 and this method doesn't work for me.I got even BSOD after installing citrix software.

Anonymous said...

Thank you for the info. Finally, I was able to login through VPN client under Win 10. But I cannot access anything on the remote server. Tried accessing the files or using remote access and it did not work. Works on my Win 8.1 machine but not under 10. Any help will be appreciated.

Anonymous said...

Hello,

I think I did something foolish: Whenever I connected to any of my customer's VPN I got disconnected within 5 minutes but a month ago I didn't have that problem so I un-installed my Cisco VPN Client 5.0.7 running on Windows 10. After that I tried to re-install it but everytime I run the MSI file I get the Error 28011: Windows 64-bit is not supported.

I have uninstalled the Sonicwall, cleared the TEMP files, performed the Disk Cleanup but I don't know if I should do something with my registry too which currently looks like this:

Cisco Systems VPN Adapter for 64-bit Windows

I hope someone can help me :(

Thanks in advanced.

Regards,

Anonymous said...

After installing VPN client on Win10 bulid 1511, I have a problem with Wireshark. When I run Wireshark, I can see in task manager that process has started, but that is it. No window, no error message.
I tried to reinstall WinPcap, and Wireshark - nothing changes.

I installed Win10Pcap - nothing.

I installed Ncap - stiil same.

I am running out of ideas. Anyone have some sugestions

Anonymous said...

That fix worked for me today in a new update to Windows 10 coming from Windows 8.1..

Only had to do this steps

3. Optional if needed:
Open regedit
Browse to the registry key HKLM\SYSTEM\CurrentControlSet\Services\CVirtA
Select the display name to modify:
x86 - "@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter" to "Cisco Systems VPN Adapter"

Thanks,

pentium9394 said...

Thank you very much. Yes it works very well. I have to install step 1,2 and modify the registry. Must need reboot. If the steps not completed, it will be stuck at "securing connection on the Cisco VPN client". Again thank you for the great help !!!! I am still having a lot of issues with Cisco Anyconnect and cannot migrate over. I wished that Anyconnect is made easier for people to use, the good news is Cisco VPN client still works like a charm !

Deg said...

Worked perfectly (Windows 10 Pro 64-bit) after registry modification.
Rebooting the system was not required.

TimW said...

This works. Had to perform all three steps on Win 10 Enterprise 64-bit.

What I don't know is how you figured this out? Awesome and thank you.

- TimW

Anonymous said...

Hi there! First thank you for posting this article. I used it in April and it worked like a charm. I recently started to get a Error 5: No host name exists, so I determined the best course of action was uninstall SonicWall and CiscoVPN. When I go into the Regedit, I do not see: x86 - "@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter"

Is there something obvious that I am missing?

Anonymous said...

Thank you so much for this post! I performed only steps 1 and 2 with no errors and also used the 64-bit versions for both.

Unknown said...

Symply THANK'S!!! Evrythink work!

Anonymous said...

This Guide is PERFECT! for the latest build 1511. Just do everything as it says in the top. I ran into a wall while trying to install the SOnic VPN part. I did the second install the VPN software and then tried it again and it worked. The Registry part is crucial! once you get that part done reboot and it you should be fine!

Anonymous said...

This worked for me.
Thanks for the solution.

Unknown said...

Thank you so much!!!
The Optional part needed...

Anonymous said...

Thanks for the clear instructions. I had an upgrade from Win7 with VPNclient already installed. Removed it, rebooted, followed your instructions and had to modify the registry. All worked fine thereafter.

Anonymous said...

This worked first time for me today on a new Win 10 rig with current patches. I did need the regedit hack but did not need a reboot or anything else. This just saved me countless hours, many thanks!

piedpiper67 said...

Just a note for those who have upgraded or plan to upgrade to the Anniversary build 1161, during the upgrade it identifies the Cisco VPN software as not compatible with Win 10 and blows out the program. If you uninstall it and then reinstall (using the MSI file) then apply the regedit hack you are good to go. PITA, but it worked.

Anonymous said...

Stephen Feldman, Thanks ;)

Anonymous said...

win 10 just auto updated on me and removed the cisco vpn service. wouldn't allow the installer to run at all because "this app can't run on this PC". luckily it was still in programs and features, so i could do a repair install to reestablish the service. fixed the DisplayName reg key again and it worked. not sure what i'd do if i had to install it fresh, MS assistance is no help

Anonymous said...

Stephen Feldman, after posting my PITA story i just noticed you beat me to the punch... i'd add to your post that a repair install from progs and features will work without uninstalling.

Anonymous said...

I have this error message. Any ideas how to fix this. Thanks a million!
Secure VPN Connection terminated locally by the Client.
Reason 401: An unrecognized error occurred while establishing the VPN connection.

Anonymous said...

As of latest update (Windows 10 Version 1607 Build 14393.51) the Cisco VPN client no longer works.

Jeff_y said...

As of latest update (Windows 10 Version 1607 Build 14393.51) the Cisco VPN client no longer works.

Anonymous said...

I stand corrected :-) As long as Cisco VPN is already installed PRIOR to applying anniversary update (Windows 10 Version 1607 Build 14393.51), it will still work with some additional steps:

- run a repair install
- fix registry

Anonymous said...

I stand corrected :-) AS long as Cisco VPN is installed PRIOR to applying Anniversary update (Windows 10 Version 1607 Build 14393.51), it will still work. The install repair process and registry update is also still needed.

Anonymous said...

All steps worked for me after 8/2016 Windows 10 updates (did need the regedit). Many thanks!

Anonymous said...

Many thanks for posting this. Following your instructions worked for me first time. But how ridiculous that this is the best solution - poor from Cisco.

Anonymous said...

Hi All, thanks for d contributions. Pls anyone wit idea of vpn client that works on android phone?

Unknown said...

I need to have both Connect Tunnel (Dell) vpn client and Cisco VPN client (with DNE LightWeight Filter) installed on my Win10. But traffic doesn't flow thru Dell vpn client after DNE update installed. Only if I make DNE filter uninstall on the LAN interface all working ok. But then Cisco VPN client stop its work. Could someone help me resolve it? Thanks.

Unknown said...
This comment has been removed by the author.
Anonymous said...

This worked for me on Win 10 with the 'Anniversary Update'. I needed install the Cisco VPN Client using the .msi file, and the registry fix was also required. No reboot was necessary! Thanks for posting those invaluable instructions!

Unknown said...

Thankyou Worked Great

Anonymous said...

I had it working before the 1607 update. 1607 removed the Cisco code. I reinstalled is and modified the registry. The app gui loads. I can initiate the request, but when the user login comes up and I put in the password the attempt fails. I am getting a 442 error

Anonymous said...

Same issue here, after the 1607 update my VPN didn't work. I decided to uninstall and start from fresh but unfortunately, it's not working. Any suggestions?

Anonymous said...

Thank you SO much!!! On several occasions this page has saved me countless hours of fighting with Windows 10 and Cisco VPN, without which I wouldn't be able to work.

Unknown said...

Thank you. I used your tutorial the first time I upgraded to win 10. Now on the anniversary update I had again problems.
I solved it only with repair of the application from control panel...
Thank you, Stefan.

Anonymous said...

Worked beautifully for me, thanks for this post.
Remember, the registry edit is the key, I was missing that and had issues. As soon as I did the registry edit, it worked!

Anonymous said...

This is a life saver! This VPN Client is essential for my day to day work. Used this procedure when I first upgraded to Windows 10 x64 and now after the anniversary version upgrade. Yes, I had to modify the registry entry as said. THANK YOU VERY MUCH!

Erik said...

For the people who still have the 442 error (Failed to enable virtual adapter) check if in Device Manager in Windows 10 the SonicWALL Virtual NIC is enabled.

In my case, I hade a clean Windows 10 install, then followed steps 1 and 2 above, didn't need to do step 3 (registry was already correct) but I got the 442 error even after reboot(s).

Then I saw the Cisco VPN Adapter was disabled, so I enabled it, but when connecting the 442 error returned and the adapter was disabled again.
Enabling the SONICWALL VIRTUAL NIC solved the issue.

I hope this helps... Good luck!

Unknown said...

That worked for me. I had edit registry settings as mentioned & it is working now. Thanks a lot for this text.

5SternenSucher said...

Worked for me as well on Windows 10 as described. I then uninstalled SonicWall, rebooted and Cisco VPN is still working!

Marvin said...

Thank you! Mine needed the registry name change to work.

Anonymous said...

Worked perfectly - many thanks

Anonymous said...

Hmmm... links to the Cisco client suddenly not working?

Anonymous said...

Thanks Worked fine ...

Anonymous said...

Another thing to check if it's still not working :

In Device Manager check if you don't have several Cisco system VPN entries. For my case I had 3 entries.

Now it works fine for me.

Thanks for all the docs.

Brent (aka Jack) & Di said...

Hi, I used to have no problem but now I do. I get the “Reason 442: Failed to enable Virtual Adapter” message.


I have Windows 10 Home, Version 1607, OS build 14393.321


I uninstalled Sonic 64_4.9.0.1202_EN and Cisco VPN (version 5.0.07.0440) and did a clean install (same versions, using the *msi for Cisco VPN).


Started Cisco VPN client, attempted log in and received the 442 message.


I then did a regedit from “@oem15.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “@Cisco Systems VPN Adapter for 64-bit Windows”


Rebooted.


Started Cisco VPN client, attempted log in and received the 442 message again.


I ran "netcfg -d"


Rebooted


Started Cisco VPN client, attempted log in and received the 442 message again.


Any suggestions?

Brent (aka Jack) & Di said...

Hi, I used to have no problem but now I do. I get the “Reason 442: Failed to enable Virtual Adapter” message.


I have Windows 10 Home, Version 1607, OS build 14393.321


I uninstalled Sonic 64_4.9.0.1202_EN and Cisco VPN (version 5.0.07.0440) and did a clean install (same versions, using the *msi for Cisco VPN).


Started Cisco VPN client, attempted log in and received the 442 message.


I then did a regedit from “@oem15.inf,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows” to “@Cisco Systems VPN Adapter for 64-bit Windows”


Rebooted.


Started Cisco VPN client, attempted log in and received the 442 message again.


I ran "netcfg -d"


Rebooted


Started Cisco VPN client, attempted log in and received the 442 message again.


Any suggestions?

Anonymous said...

Everything done as you said thank's for the clear tutorial.

but what to after this ? how to change my ip address.

i am using windows 10 ( 1511 ) 32 bit

please explain that too.

hammer said...

I am on Windows 10 Pro (x64). After following your instructions, I get error 442 "Failed to enable virtual adapter" after authentication. Is there a remedy you know of?

Unknown said...

I am on Windows 10 Pro (x64). After following your instructions, I get error 442 "Failed to enable virtual adapter" after authentication. Is there a remedy you know of?

Anonymous said...

Two thumbs up. Thanks. Works like a charm with the SonicWall 4.9.9.1016 version.

@people having errors on the Cisco client after authenticating (failed to open adapter) - be sure to make the registry edit. That was the final step in getting mine to work.

Khawar said...

Great Post (Y) It worked for my windows 10 home withe latest upgrades. Thanks a lot

Khawar said...

For the people who are facing "Virtual Adapter" error on connection, disable the Internet Connection Sharing Service and then connect.

Jim said...

Thanks for this, problem solved finally!

Anonymous said...

Thanks. This worked, but I have a little background and knew how to work with the registry. For those of you who don't, in windows 10, click the windows button, then type regedit to get to the registry editor.

Once you are there, in order to browse for the key, you can choose edit, find (or Ctrl-F), but that didn't work for me. I had to drill down to the entry because mine said "@oem18 instead of "@oem8.

There are several choices on the left side - HKLM stands for HKey_Local Machine. You can click on the > sign next to the key to open it up and go to the next name until you get to the CVirtA, then right click on "Display Name" and choose modify.

Thanks again IT Guy.

Anonymous said...

Just a quick thanks, saved my butt from having to spend hours getting this working.

monomorph said...

Same procedure as on every Win10 Upgrade. Today my Win10 Pro was upgraded to 1607. Of course the Cisco VPN client was "incompatible" again... Just follow the steps that are listed in the beginning.

Here's what I had to do this time:

- Global VPN Client was still installed
- Uninstalled the Cisco VPN Client
- Reinstalled Cisco VPN Client
- Applied the registry patch for "Cisco Systems VPN Adapter for 64-bit Windows"

All is fine again. Third time I had to apply the patch:

- 1st time after upgrading from Win7
- 2nd and 3rd time after major Win10 upgrades.

Thanks again! Cheers!

Anonymous said...

Hi everybody, i've installed Cisco VPN Client successfully but now, when i try to connect to a connection entry it happens this error: Reason 414: Failed to establish a TCP connection. Any help would be appreciated. Thanks

Anonymous said...

Does not work for me. New Install, followed guide and did regedit

Anonymous said...

reason 413 user authentication failed, kindly help how to resolve the same

August said...

This worked for me perfectly for connecting me to my work network. But I have one small irritant bug as a result, and I'm wondering if anybody else has encountered it or knows a solution. I can browse to work folders, or even Remote Desktop into my work computer, but if I try to open up my local Microsoft Outlook, it immediately shuts down with an unknown problem. If I disconnect the VPN, Outlook opens fine, so it's something in the way my Outlook is trying to communicate with the Exchange Server at work. This worked fine back when I was on Windows 7 and didn't have to have the CISCO VPN fix to work. So all evidence points to something in the fix that is breaking the Microsoft Outlook communications over the VPN. Anybody have any thoughts?

August said...

This worked for me perfectly for connecting me to my work network. But I have one small irritant bug as a result, and I'm wondering if anybody else has encountered it or knows a solution. I can browse to work folders, or even Remote Desktop into my work computer, but if I try to open up my local Microsoft Outlook, it immediately shuts down with an unknown problem. If I disconnect the VPN, Outlook opens fine, so it's something in the way my Outlook is trying to communicate with the Exchange Server at work. This worked fine back when I was on Windows 7 and didn't have to have the CISCO VPN fix to work. So all evidence points to something in the fix that is breaking the Microsoft Outlook communications over the VPN. Anybody have any thoughts?

Admin77 said...

Having the same issues, weirdly fixes work on some 8.1 machines and some don't. Ahwell. Anyconnect is nicer to use.

Anonymous said...

Thanks. It still work.

Anonymous said...

Shame on Cisco for not updating the software for Windows 10. It's buggy at best, and, yes the above fixes do work - sometimes. I expect better from a company like Cisco. I have decided to scrap this software altogether as it is not consistent in operation. I'm now looking for another solution.

Anonymous said...

Thank you! Had to do the registry fix but worked fine after that. Very helpful.

Unknown said...

hi
i have successfully installed VPN client 5.0.07.0440 in Windows 10 am getting connectivity "error 412:remote peer is no longer response " how to solve this issue

Anonymous said...

Hi!

For Build 15063 Creator's Update: do you have the list of registry entries to remove to complete Cisco VPN client uninstall? I have not uninstalled BEFORE win10 upgrade, so now re-install not working...

Thanks a lot!

P.

Will said...

I do not have an exact list of the registry entries. What I did do when having the same issues with the Creator's update was to run regedit and then delete all entries that contained "Cisco" in the name.

Once that was completed I was able to reinstall using the .msi with no issues and it still works.

Good luck!

Pradeep Behl said...

I do not see the HKLM\SYSTEM\CurrentControlSet\Services\CVirtA key through RegEdit. I have not yet installed the Cisco VPN client - does this key appear only after the install? Thanks

Will said...

Yes. The registry key is specific to the Cisco VPN client after installation. It is not a default registry key.

Unknown said...

With this guide, installation in Creators Update was a breeze.

Thanks a lot for sharing!

crudos said...

FYI, for those who have had Cisco VPN Client disabled by Windows 10 Creators Update or Anniversary Update, you can repair without having to manually delete registry entries and uninstall and reinstall:

This works if you had a previously working Windows 10 Cisco VPN Install (using the steps in the original blogger post), but a Windows update had broken it:

1. Find and right-click the vpnclient_setup.msi installer and and choose Repair.
- At some point the repair process may ask you to again browse to and select this vpnclient_setup.msi file, and then ask you to confirm Administrative Permissions to do the repair.

2. Open regedit (e.g. from typing "regedit" in the Windows Search bar)

3. Browse to the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\CVirtA

4. In the right pane, right-click on the DisplayName entry and choose Modify:

Change the string value here to "Cisco Systems VPN Adapter for 64-bit Windows" and then click OK/Save to close.

5. After this you should be able to use Cisco VPN again as you normally did.

Anonymous said...

Ill be trying this. Thanks! syg.

Anonymous said...

Windows 10 Creator Update

didn't uninstall prior to upgrade kept getting 27850 error - this is how I got it working

1. uninstall vpnclient_setup.msi (right click on file, uninstall)
2. dneupdate64.msi download and install (I have 64bit windows)
ftp://files.citrix.com/dneupdate64.msi
ftp://files.citrix.com/dneupdate.msi
3. reinstall vpnclient_setup.msi (no more errors)
4. HKLM\SYSTEM\CurrentControlSet\Services\CVirtA\DisplayName

Anonymous said...

for those, who get 442

this line:

x64 - "@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows" to "Cisco Systems VPN Adapter for 64-bit Windows"

should looks like

for x64
"@oem8.ifn,%CVirtA_Desc%;Cisco Systems VPN Adapter for 64-bit Windows"
change to
"Cisco Systems VPN Adapter for 64-bit Windows"

Anonymous said...

Thank you so much! This works with Windows 10 x64.
Indeed, you can uninstall SonicWALL afterwards and it will continue working.
Also if you'd like Cisco VPN Client to save preferences you have to run it as Administrator, change preferences and quit. Then you can run it normally again.

Backup link to the latest Cisco VPN Client: http://oldwww.asc.edu/download/CiscoVPN/Windows/

Anonymous said...

Have you some new suggestion for current update - June/July 2017?

misar said...

Your advice worked fine with the original Win 10, 1511 and 1607 but I have a problem with 1703. Everything as before until connection to the gateway. It then returns this error:
Reason 442: Failed to enable Virtual Adapter.
I tried various solutions found by Google w/o success. Any suggestions?

Thanks

Anonymous said...

Worked like a dream, thanks

Anonymous said...

Shrew Soft (Shrewsoft) VPN Build 2.2.2-release ist not running on my Windows 10 Build 1709. Can someone confirm?

After the upgrade to Windows 10 Build 1709 Shrew Soft VPN says 'network unavailable' when connecting to a vpn.

Reinstallation gives the error: "Error 0x8007007e: Couldn't install the network component."

Greetings
Mr. Black

Rose said...

I have used this process successfully on a different computer a few months back and it worked great. Went to use the same process again on a new computer and I'm having trouble. Did something change? That very first link... click here to Download Sonic wall... requires me to login or create an account as if downloading it requires licensure. Any suggestions?

Unknown said...

We just got the 1709 update rolled out to us at work. I'm trying to follow along with this guide again but I too can't download the Sonicwall client. It appears you need a Sonicwall account to grab it.

Does anyone have a link to it on dropbox or something they can share?

Will said...

I have updated the link for the Sonicwall VPN client to download the file from Dropbox without the need for going to DELL and creating a mysonicwall.com account. Cheers

Signo said...

Has anyone had the Error 1722 when trying to install the vpn client. I have done this procedure many times but this time I cant get the client to install. The issue is happening on two of my machines.

Thanks for any help.

Isabel Bent said...

Your Post is very useful, I am truly to this blog which is specially design about the vpn It helped me with ocean of awareness so I really appreciate your blog.
vpn

Anonymous said...

Just an FYI - Cisco VPN Client was EOL over 3 years ago and has a known (and unpatched) privilege escalation vulnerability.
Just upgrade to AnyConnect and don't use EOL software.

https://www.cisco.com/c/en/us/obsolete/security/cisco-vpn-client.html
https://nvd.nist.gov/vuln/detail/CVE-2015-7600

Alcides Pinto said...

Hello and thanks for this very usefull post!

I have used it prior to Creators Update and it worked like a charm. But just like you I updated without unistalling the VPN and now it is a mess :(
You said "Now for the not-so-fun-details. I didn't uninstall prior to the upgrade and proceeded to spend the next 30 minutes clearing out registry entries until I finally found the right one to let me reinstall the product using the .MSI file. After doing that, and making the registry edit, my VPN client is again working properly." - can you specify wich entries should I delete, please?
Thank you very much!

Cheers!

Will said...

- To address the comment about the software being EOL...I am very aware of that as well but in the real world we cannot always stop using things just because the vendor says they are EOL. Businesses do not always move at the speed of tech. I wish I did not have to use this software any longer but that is not my reality at this time so I try to provide a way for other such as myself to keep things running as long as possible when we have no other choice.

- To address Alcides...I did a registry search for everything "Cisco VPN" and remove it. I had to go back again and run the search a second time to get some items left over by searching Cisco. Since I also run the AnyConnect client, I removed it first to ensure that I would not disrupt how that program works. Once I had the VPN client working, I reinstalled AnyConnect without issue.

Alcides Pinto said...

Thank you!
It is working flawlessly again!

Much much appreciated!

Regards!

Realtebo said...

i cannot install Dell sonic Wall 64_4.9.4 on my windows 10 pro x64.

I hot an error code 2753 while installing.

i tried running the sonic wall cleanup, and restarted, but the error while installing dell sonic wall is still here

Anonymous said...

I just had this issue after upgrading to Windows 1709 (Fall Creators Update). Unfortunately, I was not able to uninstall the software before the update. However, I attempted the following:

Repair the Cisco VPN client installation via the Control Panel
Changed the Adapter entry in regedit. (Cisco Systems VPN Adapter for 64-bit Windows, per the article)

And it works. There was no need to touch the DNE installation.

Unknown said...

For Windows 10 update 1803 - it triggers removal of the VPN client and "Error 56" service messages.
As said before, your best bet is to
1. Unistall SonicWall;
2. Unistall VPN;
3. Reboot;
4. Install SonicWall;
5. Install VPN;
6. Fix the registry (for the "442 error");
7. Reboot to enjoy!

«Oldest ‹Older   201 – 312 of 312   Newer› Newest»