Tuesday, April 11, 2017

[SOLVED] Cisco VPN Client on Windows 10 (Including the new build 15063 Creator's Build) - This works!

***Updated 04/11/2017 for build 15063 Creator's Update**
***Please see my edits below for notes on build 1607 and build 1511.**

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). **NOTE: Make sure you are using the latest version of this client.  Older versions may not work properly.

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 15063 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!





295 comments:

1 – 200 of 295   Newer›   Newest»
Viorel Petre said...

Hello, it does not work... I have Win10x64 and I Have the same message, "This app can't run on this PC"...:(

Anonymous said...

Thanks a bunch, you made my day! I did download and run the Citrix DNE but it was failing, this did the trick.

For anyone else doing this, don't forget to clean up the registry entry after installing the Cisco IPsec client at:
Computer\HKLM\SYSTEM\CurrentControlSet\Services\CVirtA\DisplayName
Just remove the garbage before "Cisco Systems VPN Adapter for 64-bit Windows"

Anonymous said...

http://www.citrix.com/go/lp/dne.html DNE update, все есть

Ryan St. John said...

I wish I had seen this earlier! I just rolled back and won't have tume to re-upgrade until the weekend. Hoping it works!

Anonymous said...

You saved another few hours to waste on this one.
Thank you!

Anonymous said...

Great. It works for me

Anonymous said...

any chance you have some instructions for 32bit...I havean older laptop and when I try this method, it give me the following error:

---------------------------
SonicWALL Global VPN Client
---------------------------
Error creating process . Reason: C:\WINDOWS\system32\advpack.dll

Any ideas...I figure I need the SonicWall 32 bit version as well as a different version of the Cisco VPN client?

Will said...

You can download the 32-bit version of the Sonicwall client from the same link I have above. For the Cisco VPN client you would need to try to find this file "vpnclient-win-msi-5.0.07.0410-k9.exe" That is the 32-bit version of the same Cisco VPN client.

Hope this helps.

Anonymous said...

If you can't run the install, instead of running vpnclient_setup.exe in the Cisco VPN installation package, try right-click the .msi and install that way.

Anonymous said...

Thanks a lot...you saved me from the hassle of running a VM just for VPN.

The solution didn't work for me initially.
I had to remove all previous copies of sonicwall, cisco vpn client and pcf files.
Cleared the temporary files and did a disk cleanup followed by a PC reboot.

After that installing as described in the article fixed the issue.

Thanks a lot!

Anonymous said...

You'll have to unpack the exe first, just like if were a zipped file. Then go to the directory were you extracted it and install the client via the .msi file. Hope it helps

John Fernandez said...

I've been trying to get this to work for about the past 3 hours.. I'm continually getting the 443 reason code. I upgraded to Win10 today and I need this going tomorrow :( should have thought of that first! lol..

I've uninstalled both the cisco client and the sonicwall client, cleaned up temp files and removed the left over program files, reboot and then follow the instructions you've posted to a T, however I keep coming back to the same 443 problem. Any suggestions would be greatly appreciated!

Salvador Aguilar said...

If you are using IPSec/UDP, try to use only IPSec it works for me

Anonymous said...

Awesome find. Saved a lot of time fumbling through this. Thank you!

Anonymous said...

Hello,
I have never installed sonicwall client before and things were working fine.
After reading your post, I installed sonicwall but it was asking me the pre-share key which I dont have for my vpn.company.com. Do I need to configure that? How?

And I tried all remaining steps but then its give me Reason 427: unknown error occured at peer.

Kyle P said...

I have a surface pro 3 (the first version) and it was originally on Windows 8.1. I made the mistake of upgrading to Windows 10 without uninstalling Cisco VPN client. When it was done upgrading, nothing worked in regard to the wireless or ethernet connections. I then downgraded back to Windows 8.1 and uninstalled the Cisco VPN client and the re-upgraded back to Windows 10. Everything worked fine. Uninstalled any DNE that was installed before I followed the steps above. I then followed the steps above and did the optional step 3, just in case and when I launched VPN client, it worked like a charm. Thank you so much for this. It took me forever to find this awesome forum. But it worked! Thanks so much again!

Anonymous said...

This was exactly what I needed! This resolved a problem that could have crippled some of the users in my organization. Since these machines were upgraded from Windows 7 and not a clean install, I had to make the changes in the registry. Once that was made, I was able to connect to the VPN without any problems.

Thank you so much for sharing this solution!!

Will said...

You're all welcome. Glad to see how much this is helping everyone get this software working. I know prior to 7/29 it was the largest thing keeping me from being able to deploy Windows 10 since we depend on it so much for connecting to client networks.

Anonymous said...

Worked great here. No need to edit registry.

Anonymous said...

Wow! Works!! Thanks so much, would never in a million years have figured this out

Anonymous said...

I needed to do the registry edit with my Windows 10 Pro 32 bit

Anonymous said...

Appreciate you sharing!!!! This is what IT networking is about. W10 upgrade wiped Cisco IPX client, install sonic, then cisco, no reboot and all works. Back on-call again!

Anonymous said...

Thanks heaps, worked with the regedit straight off on two machines. Much nicer looking than Shew Soft VPN Client (which was my fall back before bothering to research)

Moin Syed said...
This comment has been removed by the author.
GDragon said...

I've got reson 401 "Secure VPN Connection terminated locally by the Client.
Reason 401: An unrecognized error occurred while establishing the VPN connection."

Every time i want to connect,,
Please help me

Adrian Munteanu said...

Hello,
It Works on my win 10. I installed and check the functionality. Thanks!

Adrian Munteanu said...

It Works just perfect for me. Whith first two steps.
Thank you!

cybernet said...

Thank alot it's work.

Anonymous said...

You're' the MAN!

I've been battling this for MONTHS on my Windows 8.1 machine. The only problem I had was when installing the SonicWall Client I got the message -

"Unable to manage networking component. Operating system corruption may be preventing installation error."

to fix I added:

‘HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Network\MaxNumFilters’ (DWORD, set to 14)

Reboot and retry the installation. SonicWall installed, then I followed the rest of your instructions.

Thanks!

jlk1380 said...

perfect too easy :)

Anonymous said...

perfect too easy :)

Anonymous said...

Worked for me too :-)

I upgraded from Win7 pro.
The Cisco program group was missing altogether.
If I tried launching vpngui.exe manually I was getting an error saying that the service wasn't running.

1) uninstalled Cisco VPN Client
2) reboot
3) followed this guide

Just make sure to launch the Cisco VPN Client installer using the .msi file, not the exe. Also, I had to set the "compatibility mode" of the .msi to "previous version of windows" before launching it. Otherwise it will keep telling you "This app can't run on this PC".

Oh, and the registry hack was necessary as well.

Thanks guys!

-Rodrigo-

Anonymous said...

This worked as instructed on a 8.1 to Windows 10 upgraded machine. Tested using a Verizon (Pantech) 4Glte Aircard. Thanks

Pedro Almeida said...

On fresh Win10 (64) installed DNE after patching registry for MaxNumFilters, then Cisco VPN 64-bit, then the registry change for the Interface DisplayName.
All of them give me Error 427.
Any ideas? Also tried to activate logging but the log window only shows:

Cisco Systems VPN Client Version 5.0.07.0440
Copyright (C) 1998-2010 Cisco Systems, Inc. All Rights Reserved.
Client Type(s): Windows, WinNT
Running on: 6.2.9200
Config file directory: C:\Program Files (x86)\Cisco Systems\VPN Client\

Even changing all log levels.
All I get is.

Error 427: Unknown error occurred at peer

At the server side all seems ok:

Aug 14 22:40:02 vpn3000a 5342134 08/14/2015 22:40:01.150 SEV=4 NAC/27 RPT=29449 NAC is disabled for peer - PUB_IP:62.28.X.Y, PRV_IP:10.123.A.B
Aug 14 22:40:02 vpn3000a 5342136 08/14/2015 22:40:01.160 SEV=5 IKE/50 RPT=139696 62.28.X.Y Group [XXX] User [palmeida] Connection terminated for peer palmeida. Reason: Peer Terminate Remote Proxy 10.123.A.B, Local Proxy 0.0.0.0
Aug 14 22:40:02 vpn3000a 5342138 08/14/2015 22:40:01.170 SEV=5 IKE/194 RPT=21675 62.28.X.Y Group [XXX] User [palmeida] Sending IKE Delete With Reason message: No Reason Provided.
Aug 14 22:40:02 vpn3000a 5342141 08/14/2015 22:40:01.170 SEV=4 AUTH/28 RPT=40588 62.28.X.Y User [palmeida] Group [XXX] disconnected: Session Type: IPSec/NAT-T Duration: 0:00:00 Bytes xmt: 0 Bytes rcv: 0 Reason: User Requested


Any ideas?

Anonymous said...

Worked for me just like Rodrigo mentioned above. I tried connecting to the VPN after installing the software but the registry edit was necessary.

I had to use the .msi as I would get an error with the exe installer. I did not have to change to compatibility mode, however.

Pedro Almeida said...

Oddly enough, on my Win8.1->Win10 upgraded PC it worked fine (MSI+registry).
Only on these Win10 fresh installs it's happening, and nothing shows on the logs. Any ideas?!?

Rui Silva said...

Worked for me on Windows 10. Thanks

Rudy said...

Worked perfectly. Thanks

Anonymous said...

Perfect post ... worked great. Thank you.

Naveen Gangil said...

Thanks a lot.. It worked for me as well.

Víctor Castany Aregall said...

Worked for me too :-)

Kev said...

Thank you very much! It worked for me following your recipe the first time....;)

Pedro Almeida said...
This comment has been removed by the author.
Pedro Almeida said...

Just be sure to uninstall any DNE before installing Sonicwall. That was my issue.
I made an installer using Powershell that:
- Changes registry (maxfilters for DNE)
- Installs sonicwall
- Installs Cisco VPN
- Changes registry (correcting interface according to 32/64 bits)
- Uninstalls sonicwall

Would do almost all silently but sonicwall uninstallation, even on quiet mode will prompt about retaining mac-address..

Anonymous said...

If you've already installed any other DNE client uninstall it, and then you can download the DNE remover from Cisco: http://www.citrix.com/go/lp/dne.html (winfix) and use that to remove all instances of DNE then reboot and reinstall the Sonic VPN client as mentioned. Then finally the Cisco VPN client and it should work.

Bradley White said...
This comment has been removed by a blog administrator.
Bradley White said...
This comment has been removed by a blog administrator.
Pedro Almeida said...

Isn't there a standalone version of DNE known to work with Cisco VPN W10 (to avoid installing Sonicwall) ?

Will said...

There is a stand alone version. In my testing I was never able to get that stand alone version plus the VPN client to work with Windows 10. There's no harm in trying it I guess.

Pedro Almeida said...

@Will

I know there's a standalone version for DNE (from Citrix). But, as you said, that won't work (fails to retrieve key).

That's why I asked for a standalone version known to work with Cisco VPN (without Sonicwall, so I could make a silent installer).

CarlosRPEvertsz said...

This is the best and final solution http://sourceforge.net/projects/vpncfe/

Anonymous said...

I agree with CarlosRPEvertsz after mess up a lot with clean machine windows 10 I thought I would come back to windows 8.1 where Cisco VPN used to work but VPNC Front End helped me specially because I had pcf file format to import!

Mono Morph said...

Initial how to worked for me after upgrading from 8.1. to 10. It used to work on 8.1 but no longer on 10 after upgrade. Had to patch the registry too.

Big thumbs up! Thx!

Anonymous said...

Thank you so much :-).
Worked perfectly.

Anonymous said...

works! thanks so much.

Anonymous said...

Many thanks !

Tickets said...

It Just Works!!!
Many thanks.

Anonymous said...

Worked a treat I had just done a Win7 to 10 upgrade had to do the regedit works .. Thanks

Anonymous said...

It works perfectly! Thanks much. Doesn't need to do regedit for me. It works after doing step 1 and step 2.

Anonymous said...

It works! only did step 1 and 2.

Anonymous said...

Tried to run this and getting error message that this app can't run on this PC, getting the compatibility. Did some changes on the compatibility and still with the same result.

Any ideas on this please?

Will said...

Extract the VPN client file out into a folder. From there just run the MSI as administrator and you shouldn't get that error any longer. That's how I got it setup on a clean Windows 10 install. Others have posted the same here.

Anonymous said...

Did all on top of this post, it works with step 1,2 and 3 !!!

Anonymous said...

Brilliant, had to do the registry entry to get it to work. But it works!!!! TY TY TY so much for this. Talk about a life saver. You seriously rock!

Anonymous said...

It worked for me after a morning of tries! I would build a statue to this guy

Anonymous said...

Great work Will.... after doing the registry changes,its working fine on win10...
But I don't know why both the adapters (i.e. Cisco Systems VPN Adapter for 64-bit Windows and SonicWALL Virtual NIC) is showing disconnected in device Manager/Network Adapters ..

Also after connecting to vpn client,I am not able to connect to internet on the same machine.

Please share if you have any idea on the above queries..

Thanks
Praveen

Will said...

Typically the VPN adapters don't show connected when they are not. This is normal. As far as being unable to hit the web there's a couple of things at work. First it would seem the VPN connection is not set for split tunnel. This means when you connect you are not allowed to function independently of the VPN connection. If the company controlling the VPN does not allow remote users on the web them this is why.

Chris Owen said...

Had to edit registry. Outstanding!!!

Anonymous said...

Thanks. That did it.

Yash said...

This is stupid. Going back to win7. Everything there just worked.

Arvind B said...

Will.. You are awesome, made my day.. !! Thanks a ton.

Anonymous said...

thanks, it works for me with Windows 10 64b.
What I did is:
1. Install the Sonicwall 64-bit VPN client from HERE (as of this writing).
2. Install the Cisco VPN client.
64-bit Windows 7/Vista/VPN Client (version 5.0.07)
3. Open regedit
Computer\HKLM\SYSTEM\CurrentControlSet\Services\CVirtA\DisplayName
Just remove the garbage before "Cisco Systems VPN Adapter for 64-bit Windows

Anonymous said...

Funka som berre fan.
Great stuff saved the day :-)

Jim Mathews said...

Thanks for your help so far... I have been able to install the program, but am running up against the following error message when I try to connect: "Secure VPN Connection terminated locally by the Client. Reason 442: Failed to enable Virtual Adapter."

Our "IT staff" has no idea about where to go next. Would you posit a guess?

Thanks, Jim

Anonymous said...

Thanks a lot for this post, I didn't find the registry details to edit. Mine is a upgrade of Windows 10 Pro.

What worked for me was an uninstall of the previous client and running the install using compatibility for previous version of windows.

Alcides Pinto said...

THANK YOU!!!! All good. Had to do the registry switcheroo. Working OK.

Антон Белов said...

Thank you VERY MUCH!!! You really saved me from crash. Now connected.

Антон Белов said...

Thank you VERY MUCH!!! You really saved me from crash. Now connected.

Антон Белов said...

Thank you VERY MUCH!!! You really saved me from crash! Now connected after a few hours of useless internet surf.

Anonymous said...

VPN doesn't work after KB3093266 this update.
Does anyone know any workaround?

Anonymous said...

Awesome! I just auto upgraded from 8.1 on a Surface and I had to do most of the steps including fixing registry and installing Cisco using .msi but it works beautifully now!
THANK YOU!

Anonymous said...

Thank you , the trick works perfect.. No more incompatibility errors. But after connecting to the VPN client, there is no access to the inside network at all (No packets encaps and decaps).
Please advise!

Matej Ravnikar said...

The trick is working on Windows 10 64bit and dont forget to check regedit !

Khalid Mehmood said...

Worked like a charm on windows 10 enterprise 64 bit.

pethams said...

Worked for me as well! I had to update the registry entry to fix the 'Description'. Nice

Anonymous said...

Hi Will -
My problem is a relatively new Dell Inspiron which was upgraded from Win 8.1 to Win 10.
I have absolutely no wifi showing on my laptop, yet the drivers were installed correctly.
I was hoping that I could use your method to fix the issue, and I have followed your instructions to the letter. However, I still see no wifi connections - although laptop is connected in the background.
What am I doing wrong?

I am told that I will need to roll back/restore to win 8, uninstall the VPN client, upgrade to win 10 and then reinstall the VPN client....what am I to do? That is a LOT of work.

HELP!!!

Anonymous said...

To Jim Mathews
it's important to change the name in registry ....
Thk it works ...

Theo van der Heijden said...

I can just say, it works great for me.
I uninstalled the Cisco VPN first, and rebooted.
Then followed your instructions, including the registry-update, rebooted and everything worked again on W10 64bit.

Thanks for sharing this information!

Scott Blaine said...

This worked great for me (after the registry fix). Thanks a bunch!

Will said...

To Anonymous with the new DELL laptop. You have already given the fix that I have seen and had to perform myself. Downgrade back to 8.1, remove the Cisco VPN client, make sure the registry is clean of all traces of the program, and then upgrade to Windows 10.

Once upgraded follow my steps above and you should be good to go. Since it's a new machine you could perform the system restore to a clean machine, upgrade, and then reinstall.

However if new already includes a lot of applications, the downgrade may be the best way to go.

Personally once it has the free upgrade to 10, I would remove all traces of the OS and do a clean 10 install anyway. You only need to do the upgrade from 8.1 in order to get the free 10 license.

Good luck!

Anonymous said...

hi
I have upgrade windows 7 pro to windows 10 pro 32 bit. when try to install cisco-vpn-client-for-windows-32-bit-v5-0-07-0290 error occurred 27850 unable to manage networking component , operation system corruption may be preventing installation.

Anyone help to resolve the issue.

Cecil Meyer said...

Thank you very much !!

Anonymous said...

Hi, Followed the steps on Windows 10 and was able to install and connect. But there is no traffic.

Marco van der Plas said...

Thanks, it worked! :)

Emilian Wiznerowicz said...

Thanks, worked as a charm :). I had to edit registry at the end (didn't work without it)

Best regards,

Emil

Anonymous said...

I am glad this works for some of you. For me, it only caused my Win10 system to take 15 minutes to log in. Oh, and VPN software cannot be uninstalled anymore. Thanks.

Anonymous said...

Excellent. Had a brand new Windows 10 Home Hp Spectre X360. Installed SonicWall, then the Cisco VPN and imported pcf file - did not work. Did regedit and connected to gateway straight away. Connected to server then using Microsoft RDP. Brilliant

Anonymous said...

Thank you so much for this. I had error 56 because I didn't uninstall VPN client before upgrading so I had to downgrade to 8.1 again, uninstall, upgrade to 10 and then follow your instructions, problem resolved!

Insurance IT said...

THANK YOU! Worked great!

Anonymous said...

Thank you!. It works. I used the 64 bit version of Cisco VPN Client 5.0.07.0440 and followed your instructions..

Anonymous said...

Thank you so much man, you saved my bacon this morning!!

:D

Anonymous said...

Worked for me too. Thanks.

John.

eddie dalton said...

thanks work for me! your Certs paid off

Neilrahc said...

Thanks very much for getting this working. Especially for finding the right DNE, how to remove any preexisting DNE's and for the registry edit. Took some real homework I'm sure to get all that for our benefit.

One final thing I found after removing VPN clients, cleaning the DNE's, rebooting, then installing SonicWall and Cisco VPN clients and cleaning the registry key: it still wasn't working on my Wi-Fi. I tried it on a newer router and it worked just fine. Some older routers/Wi-Fi do not work well with newer computers and Win 10.

Anonymous said...

Doensn't work on a Windows 10 Pro on newest patch level. Even with registry tips the cisco Service wont start. But still thanks

Will said...

Interesting you say it doesn't work on the latest patch level. I just setup two new laptops yesterday with Windows 10 and installed the software on them without issues after both were fully patched and both were Windows 10 Pro.

Is your install an upgrade or clean install? Also prior to upgrades the Cisco VPN client has to be removed fully to prevent any issues with it after the upgrade.

Hopefully you'll get it figured out.

If I find these instructions no longer work on any patch version I will update this article as such.

Thanks for the comment.

Yanuar said...

wow...you saved millions people bro.
I just clean install win 10 to my new laptop, then i follow you instruction, bummm....
it works as usual in my win 7 laptop.

Anonymous said...

installed on Windows 10 Surface Pro 3. Followed the steps above. Got a 442 error, made the registry setting change, and everything worked perfectly. I am now able to connect into my work VPN network(Cisco ASA)

Ashie said...

Dangg!!!! Thanks a million man. You just let me work from home for today!! Thanks again.

Ashie said...

Thanks a ton again!!

Anonymous said...

Changing the display name in registry really did the trick for me. Life saver ;) - thanks a million!!

Unknown said...

i love you

Anonymous said...

You are a godsend. Had to use the msi instead of exe from the cisco vpn software. For those who recommend Shrew vpn, it doesn't always work. I think my company's vpn detects the unauthorized client and forces me to re-sync the secure id. It might work the first time but then kicks me out. Maybe something is missing from Shrew but this fix works like a charm.

Unknown said...

This has been mentioned before, but if you get the error "This app can't run on this PC", it is because you ran the "vpnclient_setup.exe" file, when you need to run the "vpnclient_setup.msi" (at step 2), perhaps the instructions should be updated to make this clear

Anonymous said...

Thanks a lot! I had to reboot after the Sonic install and again after the vpn client. Initially, got a 442 error but after the reboots, it went fine. Also, made the regedit; not sure if it was needed. Cheers.

Bui Viet Duc said...

Thanks. You just save my time

Anonymous said...

This worked perfectly, thanks a ton for taking the time to post this. It's really very much appreciated and you've helped a lot of people out!

Anonymous said...

Beware folks - the latest Windows 10 update (released 11/12/2015) will FORCEFULLY DISABLE the Cisco VPN client you got working earlier! You'll get a message after the update that "This app can't run on this PC. Cisco VPN client doesn't work in this version of Windows."

While I didn't test every scenario, I uninstalled both Cisco VPN client and the Dell SonicWALL client (in that order), then installed them again in reverse order as described above (with the registry key hack).

This seems to work, and the existing vpn profiles are intact.

Anonymous said...

Worked great for me on a clean Windows 10 installation. I did need to make the registry change. I would have never figured this out, so thanks!

Wassim said...

Thanks for posting the solution.

Wassim said...

Thanks for posting the solution.

Charlie Nelson said...

The above steps worked on a previous laptop, but would NOT work on a new ThinkPad L450. Went through the install/uninstall/winfix/reboots/regedit loop about 4 times. At a loss, I installed the Shrew client. Fortunately I had the .pcf profiles used on Cisco. I imported those and Shrew "just worked!"

denis mani said...

WORKS FINE

Mike Lyncheski said...

When the major windows update rolled out last night, it beheaded my VPN Client installation.

The service, some files, and most of the registry entries were removed. It does not show on the windows programs and features app anymore. Microsoft left enough of it behind though to prevent reinstalling the client software (I get an Error 28000: Before installing ..., you must uninstall the previous version).

Anyone else have this same problem? Any workarounds? I tried removing other registry entries and the vpn folders to no avail.

Help! :0

Shannon said...

It did not work the first time I tried, so I followed someone else's recommendation and uninstalled all previous versions, the DNE updater, cleared temp files, deleted registry entries and rebooted. After that, I installed the two programs in the right order and made the registry edit. IT WORKED!!! Thanks so much!

Rajendra Prasad Nvr said...

excellent it works for me. Thanks a lot

Anonymous said...

It worked for me. I did not need to do the regedit setup. Thanks

patricia said...

Thank You so so much! Works just fine for me for my windows 10 on my surface. awesome! Note I had to do the regedit.

Unknown said...

Hi, I also lost my cisco vpn when updating to the latest windows 10. Reinstalling both cisco and the dell sonicwall sotware did not work. After trying a couple of times the install of the cisco software even became corrupted, and I could not install nor deinstall it anymore. As a last resort I tried the Shrew VPN software I read about here. After importing my cisco profile (from: C:\Program Files (x86)\Cisco Systems\VPN Client\Profiles) it just worked. Thanks for your help!

nicojmb said...

it's work like a charm.

Great!!!

Maarten said...

I'm successfully using the ShrewSoft VPN client in Windows 10 x64.
It still works after the migration to the 1511 "November Update" version of Windows 10. However, I'm experiencing a plethora of stability and connectivity issues after the 1511 update that I did not have in the previous version:
- Multiple services like Audio Service, Connection Manager, Event Log Manager not starting and need to be started manually
- Initially (after a cold restart), nothing works in terms of WiFi or LAN. Only after fooling around a lot with trying to restart the mentioned services, resetting ProSet wireless etc. I could get it back to work (until the next restart)
- Intel ProSet connection for my 7260 AC Intel WiFi card shows I'm connected but Windows Connection Manager shows no connections.
- Audio Service (even after having been started) stops automatically after a while
- After restarting,

I have successfully upgraded a couple of other laptops to the 1511 update without ANY issues, so this is definitely somehow connected to my XPS17 setup, in which I use a lot of different VPN clients.

Please also note that when migrating from Win7 to Win10 (first release) earlier, I also had major issues, and had to uninstall all VPN clients (ShrewSoft, Cisco AnyConnect, FortiClient, but also Macrium Reflect and possibly even VMWare Workstation Pro as well since the issues seem to be related to migrating the Virtual Network Adapters of these VPN-providers and the ones associated with VMWare) in Windows 7 BEFORE attempting the 'in place' upgrade to Windows 10. That worked as a charm and yielded an extremely stable Windows 10 environment in every aspect (until the 1511 update came about that is...).
After reinstalling the VPN Clients and VMWare Workstation Pro, all was still well.

My next approach to resolve the issue with the 1511 update will be to revert to Windows 10 (first edition), repeat the same actions that I took when I originally moved from Win7 to Win10 (VPN clients etc. see above) and then hope that the result will be better than currently.

Keep you informed...

Maarten said...

I'm successfully using the ShrewSoft VPN client in Windows 10 x64.
It still works after the migration to the 1511 "November Update" version of Windows 10. However, I'm experiencing a plethora of stability and connectivity issues after the 1511 update that I did not have in the previous version:
- Multiple services like Audio Service, Connection Manager, Event Log Manager not starting and need to be started manually
- Initially (after a cold restart), nothing works in terms of WiFi or LAN. Only after fooling around a lot with trying to restart the mentioned services, resetting ProSet wireless etc. I could get it back to work (until the next restart)
- Intel ProSet connection for my 7260 AC Intel WiFi card shows I'm connected but Windows Connection Manager shows no connections.
- Audio Service (even after having been started) stops automatically after a while
- After restarting, the problems are back.

I have successfully upgraded a couple of other laptops to the 1511 update without ANY issues, so this is definitely somehow connected to my XPS17 setup, in which I use a lot of different VPN clients.

Please also note that when migrating from Win7 to Win10 (first release) earlier, I also had major issues, and had to uninstall all VPN clients (ShrewSoft, Cisco AnyConnect, FortiClient, but also Macrium Reflect and possibly even VMWare Workstation Pro as well since the issues seem to be related to migrating the Virtual Network Adapters of these VPN-providers and the ones associated with VMWare) in Windows 7 BEFORE attempting the 'in place' upgrade to Windows 10. That worked as a charm and yielded an extremely stable Windows 10 environment in every aspect (until the 1511 update came about that is...).
After reinstalling the VPN Clients and VMWare Workstation Pro, all was still well.

My next approach to resolve the issue with the 1511 update will be to revert to Windows 10 (first edition), repeat the same actions that I took when I originally moved from Win7 to Win10 (VPN clients etc. see above) and then hope that the result will be better than currently.

Keep you informed...

Anonymous said...

In Windows 10 Pro is not longer available... :(

Bob Kummer said...

The recipe worked great for me today on Win 10.1151. Note that before applying the regedit step, I had the dreaded 442 error. After regedit and a reboot, all worked fine. I have not seen any stability problems so far.

Anonymous said...

You save my life!!!

Anonymous said...

I get Reason 412: The remote peer in no longer responding on each of my existing VPN connections

Anonymous said...

Any thoughts on why I get the reason 412 error? I have the 1511 update installed. Did the admin cmd prompt cmd and rebooted but issues. Uninstalled cisco rebooted. reinstalled dne then cisco error 412. uninstalled cisco and dne rebooted and did winfix to remove dne further and rebooted again. reinstalled dne then cisco and tried a new connection entry but failed again with reason 412. Any help would be appreciated. Thanks

Anonymous said...

I finally got this working and now don't receive the reason 412 error.

I uninstalled reinstalled a few times using cisco .440 version and dneupdate64.msi. Failed after several attempts of removing cleaning rebooting etc....

Then tried this GVCSetup64_4.9.0.1202_EN.exe and cisco version .440. This combo worked but may have got it worked with dumb luck...unsure but finally works

Thanks for the fixes suggested

Anonymous said...

worked like a charm!

Bob G said...

I have a Dell running windows 10. I have done everything I have seen and I am still getting an error reason 442. I have installed Sonic, Cisco VPN, and changed the registry. What did I miss

Savas Demir said...

Thanks dude. it works like a charm. I still don't understand as to why i need to install Dell SonicWall in order the cisco vpn to work. but it works :)

Anonymous said...

Спасибо, очень помогло!

Anonymous said...

Thanks guys! works for me! :)

Anonymous said...

I followed the steps EXCEPT for the regedit and was getting error 412 trying to connect. I then did the regedit and the VPN connection worked, without restarting the VPN client.

Anonymous said...

I had a very hard time after my upgrade from 8.1 to 10 did everything possible but just followed the instructions here and after netcfg -d installed it with success.
TYTYTY!!

Nick Chapman said...

worked here. w7 64 upgrade. followed normal steps, including uninstall cisco software first (didn't have to reset network) and it worked perfectly...even remembered my stored vpn information!

thanks!

Anonymous said...

Worked like a charm for me with only 1st and 2nd steps.

Mono Morph said...

Stepped into the Win10 1511 upgrade trap here too. Here's what I had to do:

- Chose "repair" from programs/features for the Cisco VPN Client.
- Had to re-apply the registry tweak for "HKLM\SYSTEM\CurrentControlSet\Services\CVirtA"
- Reboot

VPN is working again. Yikes!

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

Thank You...
( HP Stream Laptop ) ( Win 10 ( BUILD 1511 ) 64bit ) vpnclient-winx64-msi-5.0.07.0290

Followed all of the steps apart from the reg edit received error 442 did the reg edit then it is working like a charm.

Andrew said...

Operation "repair" for the Cisco VPN Client helped me to restore connection after upgrated Win10 to build 1511 without running - "netcfg -d"

Anonymous said...

I really appreciate you posting this fix. I was at a loss, and then I found your blog. I had to do steps one and two and also the optional registry edit, and then my Cisco VPN Client works again on my Windows 10 machine. Thank you so much!

Randy

Naresh Reddy said...

Cisco VPN client doesn't work on this version..

(Solved) For every windows build update regedit files are modified. Cisco VPN Client is automatically removed from your system then it will give message like Cisco VPN client doesn't work on this version. Simply you can follow below steps.

- Right click on vpnclient_setup(Type: Windows Installer)
- Select option Repair
- 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"

Carlos Tavares said...

Hi
Keep getting the reason 442 error message.
Upon opening regedit I cannot locate " HKLM\SYSTEM\CurrentControlSet\Services\CVirt"...
which is strange.
Can anyone help?
Thanks
Carlos

Bhavin Ginoya said...

Hi,
I have a problem that i am able to connect to VPN but i am not able to take the remote desktop of the server.
I tried from other PC and it is working find.
OS Windows 8.1
Cisco Vpn Client v 5.0.07.0290
Thanks
Bhavin

Anonymous said...

Thanks very much for this article and all the comments.

Worked for me
Fresh Windows 10 pro (1511) install
Sonicwall Global VPN Client v.4.9.4.0306 for 64-bit Windows
Cisco VPN Client MSI 5.0.0.7.0440 64 bit
Registry edit step resolved error 442

Anonymous said...

Carlos Tavares:

I know nothing about Windows, but I had the same problem and looked around what was there in the new build and found what was needed at this path (I think that's what you call it):

HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlset/Services/CVirtA/

My machine updated overnight and wiped out VPN. I started over by uninstalling both Cisco VPN and Sonic Wall, reinstalling Sonic Wall, then VPN, then following the original instructions with the new path I found and everything is working. I did not need the new edit at the bottom of the instructions.

Carlos Tavares said...

Hi
Thanks.
I did already uninstall both Cisco VPN and Sonic Wall and reinstalled them after reboot; still not working...
Regards
Carlos

myst3k said...

Windows update also just broke my Cisco VPN installation. I uninstalled only Cisco VPN, then re-installed it. Updated the registry item as the post shows, and my VPN is now working again.

Pedro Rocha said...

Hi, this happened to me also, and myst3k tip worked for me. I have version 5.0.07.0440, and in a 64 bit environment. Don't forget to rename adapter on regedit. Nice and easy!

Anonymous said...

Thanks Bro !

Steve Nelson said...

Thanks! I was in a bit of a fix and needed to use my Windows 10 machine for work. This did the trick (took a couple tries - make sure you try to uninstall VPN clients, even if you don't think you have it installed).

Dave said...

Many thanks for this and the 1511 update. Saved the day once again

Scott Bond said...

Thanks for the 1511 update... I believe this is the order of my fix:
1. installed Sonicwall
2. ran "netcfg -d"
3. rebooted
4. used my existing Cisco shortcut (Windows stated that it removed the Cisco client software, but not the shortcut) to reinstall by pointing to the .msi file (newly downloaded) when prompted
5. new installed Cisco client from #4 did not function, so I uninstalled it from control panel (finally showed up in control panel). Uninstall also removed the shortcuts this time.
6. reinstalled Cisco client from the same .msi file
7. ran client - got VPN Adapter error - changed registry setting as described
8. VICTORY

Bhavin Ginoya said...

Hey guys,
Can anybody please send me the Cisco VPN version 5.0.07.0440 please, i lost my setup.
my email id is bravsss@gmail.com
Thank you

Markus Eisele said...

Thanks for the tutorial. Made everything work perfectly fine until the 1511 update.
I did re-install the VPN client and also reset the network stack.
Actually, the VPN client connects to the VPN but all requests (e.g. browser accessing an intranet page) lead to a connection reset error.
Windows network trouble-shooter complains about:
"One or more network protocols are missing on this computer
Windows Sockets registry entries required for network connectivity are missing."

Re-Installing adapter driver or following the various tips on the web didn't lead me to a solution. Any idea, what could be the problem?

Thanks,
M

Nitya said...

None of the techniques worked on v1511 11082.1000

ShrewSoft VON worked like a charm instead (no workarounds required)

Maarten said...

Same experience here, the ShrewSoft client installs and works without any of the tweaks, and has served me since perfectly since the initial install on Win10, and also nicely imports any of the profiles from the Cisco V5.0 version that I previously used under Win7.

Perhaps I am missing something, but are there any advantages to using the SonicWall solution vs. the ShrewSoft client ? Otherwise, I can safely recommend using ShrewSoft to restore VPN-functionality for Cisco V5.0 based connections.

raj said...

Thank you very much for this workaround, it really saved me a lot of time...

Dave Hemke said...

Thanks. Resolved a serious headache.

Dave Hemke said...
This comment has been removed by the author.
nomyaw said...

I'm trying to install shrewsoft vpn client 2.2.2 on win10 x64 and get a "this app can't run on your pc" error. Any ideas?

nomyaw said...

I'm trying to install shrewsoft vpn client 2.2.2 on win10 x64 and get a "this app can't run on your pc" error. Any ideas?

Dave Hemke said...

Have you tried the msi trick listed above for the cisco install?

Maarten said...

@nomyaw: I'm running ShrewSoft 2.2.2 on my Windows 10 x64 Pro without issues.
Didn't run into any problems either during installation.
Could this help explaining this ? http://www.techkhoji.com/windows-10-this-app-cant-run-on-your-pc-problem-fix/
My setup-version is called 'vpn-client-2.2.2-release.exe' and is 3.19 Mb in size (3.346.256 bytes / 3.346.432 on disk) and has installed without issues on my Win10 x64 Pro in october 2015.

Shane said...

I've been after a working solution since upgrading my Surface Pro 3 to Windows 10. This works! I finally have VPN access and no longer have to carry my work laptop around!

Muhammad Khan said...

Worked on Windows 10 64bit, steps 1 - 3. Thanks.

Anonymous said...

AMAZING! Thank you so much for this. Steps 1-3 solved my issue after upgrading from Windows 7 to Windows 10.

Anonymous said...

Cisco VPN had stopped working after the latest windows update and I had the error 56. I ran the winipcfg command and rectified name in regedit, now works like a charm. :)

Thank you.

Omar said...

Thank you very much Pro :)), I just followed the 3 simple steps in your post on my windows 10

works like a charm !!

Regards
Omar

Prapula Madala said...

Thank you very much Pro :)), I just followed the 3 simple steps in your post on my windows 10

works like a charm !!

Restarted initially without the Registry entry, which did not work

Did the registry entry and Voila... it works!!!

Thanks a lot Dude!!!

Steve Pringle said...

This was very helpful. Now I no longer have to mandatory dual boot between 7 and 10 just to run VPN.

Anonymous said...

Worked for me (Win 10 - upgrade from Win 8.1).

Thanks!!!

Ryan Myers said...

Thank you so much for this! I had to use the registry edit, but otherwise it worked on the first try. I had put off my Windows 10 update for months until I found this forum and took a chance on it. So glad I did!

Wasin Tinsawat said...

Hey guy if i already upgrade 1511 , Can i just reinstall VPN software and change regedit it will be work or not ? or i should to rollback and remove before upgrade , please advised

Will said...

My experience so far has been to reinstall (using the .msi) and then change the registry. Once done the software will work again even on 1511. The best way to reduce issues into remove prior to the update. From there reinstall and change the registry entries. The PCF files are not removed when you uninstall.

Wasin Tinsawat said...

after i re install i face new issue for me error 427 : Unknow error occurred at peer : [

Ralph Russell said...

This was a great help and works fine. However, one of these steps breaks Wireshark. After performing these two installs, Wireshark only logs inbound packets. Outgoing packets are no longer logged. This is true even after uninstalling the SonicWall VPN client. Any ideas on how to solve this.

ivdezine said...

Hi there, just wanted to let you know that this post was INCREDIBLY helpful! I've been struggling with getting on my office VPN the last week since updating to Windows 10 and following your steps solved my problem. Thank you for writing this up for everyone!!

Anonymous said...

Use the new Cisco VPN software:
anyconnect-win-3.1.10010 (once installed it updates to version 4.2)

I try the aforementioned solutions, but with the anyconnect program it works like a charm and no more configurations need to be done

Nick Chapman said...

Others may have figured it out, but I think Windows 10 users who upgraded from Windows 8.1 seem to get the 442 error which requires the 3rd step (registry fix). I upgraded to 10 from 7 and didn't have that issue. I have limited test cases, so this may not be as cut and dry as it seems to me. All machines I've used have been 64-bit, I believe.

Great guide and thank for sharing!

Anonymous said...

Thanks anonymous, you're the MAN!!!

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

That worked for me. I had to remove the 'garbage' from the registry. But it is working now. Thanks a lot

Anonymous said...

MANY MANY THANKS for this post. It worked like a champ on a Surface Pro 4 Win 10!

Anonymous said...

Thank you for sharing this information, problem solved!

Chrispy said...

Thank you for the solution.
I have Win 10 x64 and you're right. 1511 takes out the VPN.
I just reinstalled the VPN, fixed the registry, and everything works fine again.
I did not have to uninstall the Global VPN.

Thanks for your diligence for us little folk.
CISO should have done the update to their VPN a long time ago.

Bob Kummer said...

I used this recipe on several machines - thank you!

Today I attempted it using a fresh download of the SonicWall VPN (GVCSetup64_4.9.9.1016_EN.exe). No good - the 433 error persisted. After several retries, I uninstalled everything and repeated with the older GVCSetup64_4.9.4.0306_EN.exe. Success!

Hope this helps...

Drew said...

This worked for me after upgrading to 1511. I couldn't run the Cisco installer from the .exe though only the .msi worked. I also had to do the reg hack. I tried without the reg hack and the VPN software threw and error about not being able to configure the virtual adapter. After making the change in the registry and reboot it worked like a charm

Anonymous said...

@Markus Eisele -- I'm having the very same issue. Any chance you know a fix for this? I know it's been 2 months since you've posted...

«Oldest ‹Older   1 – 200 of 295   Newer› Newest»