OpenVPN client version bug in 2.3.4

Updated by Jon McClary on Sep 17, 2014

 In some cases, connection issues have been observed with OpenVPN client for Windows, version 2.3.4. The issue does not always reproduce, and we have not identified the specific criteria which causes the failure.


 The specific symptom is a VPN disconnect, which will not clear until the client machine is rebooted, due to a ‘hung’ or ‘stuck’ OpenVPN Daemon process in Windows.



 Attempting to end the task in Task Manager or to kill the process via command line fails. The only effective method in which to end the process is via a reboot of the client machine.

 Our recommendation at this time is to use OpenVPN 2.3.2. It has not been observed to suffer the connection issue described for 2.3.4, and is immune to the Heartbleed vulnerability. There is no need to uninstall 2.3.4 first, as during the install process any other version previously installed will be removed.

To verify your current version via Windows:

1.   Browse to C:\Program Files\OpenVPN\bin

2.   Right click on openvpn.exe

3.   Click ‘Properties’

        1.   See version information:


     To verify version via CLI:

     1.  Open Cmd
     2.  Enter the following:

                   'C:\Program Files\openvpn\bin\openvpn.exe' –version


To change your version to 2.3.2:

  Note: This does not require a reboot unless you're running version 2.3.4 and the OpenVPN Dameon process is already in a hung state.

  1. Run the installer, which you can download here: OpenVPN 2.3.2

  2. When prompted whether you want to allow the program to make changes to your computer, select 'yes'

  3. The OpenVPN Setup Wizard will open. Click 'Next'


  4. Agree to the EULA


  5. Leave defaults checked, and click 'Next'


  6. Click Install, changing the destination folder first if you wish to

         1. This will automatically remove any previously installed versions and install 2.3.2


 7. Click 'Next' when finished



  8. Click 'Finish'