Views: counter
Sunday, 16 March 2014

Cisco VPN Client Fix for Windows 8 Machines Released

Please note that the Pro Package version of this fix is now available by clicking the link below:

Cisco VPN Client Fix Pro Package for Windows 8

You may have found that if you use the Cisco VPN Client on your Windows 8/8.1 machines, when you type in your username and password, it fails to connect and eventually will stop trying until you see the "Not connected" message in the client software as below:

Well, we have now designed a fix for this on both Windows 8/8.1 x86 and x64 machines and are making it free to download for our visitors. Please ensure that you select the correct download for your computers operating system, if you try and run the wrong one it will not work.


x64 Download

Get it from CNET!

x86 Download

Get it from CNET!


The process of making this work is very simple, download the fix for the version of Windows 8/8.1 that you have (x86 or x64).

You will be presented with a zip file, unzip the file and you will then get to the MSI installer for this fix.

Install the MSI file on your machine (we have made it into MSI format so that it can be used for deployment in large environments via SCCM, WDS, WSUS, Group Policy etc...). Reboot your machine and then try and connect again, you should now find that your Cisco VPN Client connects successfully.


If you wish to add this to your SCCM environment for the Software Catalog or OSD processes, you can use the following installation script to install this software using the MSI:

 msiexec.exe /i "MSIFILENAME.msi" /q /norestart  


If you have any problems with this software, please do not suffer in silence, leave a comment below and we will try and help you out.


Download PAD File x64

Download PAD File x86
Blog Widget by LinkWithin


  1. Try to get in Safe mode, then type msconfig in the search bar, hit enter.You will see system
    configuration window. Then select "selective startup",tick "locad system
    services" and "load startup items", click apply, then reboot. This way
    works for me many time and not risk.

  2. Sorry about the late reply, are you still having an issue?

  3. Are you still having this problem?

  4. Is it necessary to go back and turn on Windows Management Instrumentation service afterwards? Should both HOtfixes be installed?

  5. 1) the WMI should restart itself after a reboot 2) You should/can only install the hot fix for your architecture (x86 or x64).

  6. use %systemdrive% insted of c. or d: etc and you will get the right letter from windows...

    net stop winmgmt
    cd %systemroot%\system32\wbem
    rd /S /Q repository

    regsvr32 /s %systemroot%\system32\scecli.dll
    regsvr32 /s %systemroot%\system32\userenv.dll

    mofcomp cimwin32.mof
    mofcomp cimwin32.mfl
    mofcomp rsop.mof
    mofcomp rsop.mfl
    for /f %%s in ('dir /b /s *.dll') do regsvr32 /s %%s
    for /f %%s in ('dir /b *.mof') do mofcomp %%s
    for /f %%s in ('dir /b *.mfl') do mofcomp %%s
    echo DONE reboot the machine

  7. Different things work for different people!

  8. well, that worked fantastic for me. thank you very much! :D