-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
> Hi Samuli, > > Samuli Seppänen wrote: >> New Windows installers with OpenSSL 1.0.1j have been released: >> >> <http://openvpn.net/index.php/download/community-downloads.html> >> >> Two of the issues fixed in OpenSSL may impact OpenVPN. More details here: >> >> <http://thread.gmane.org/gmane.network.openvpn.devel/9133> >> >> Let me know if there are any issues with these installers. >> >> > just downloaded the openvpn-install-2.3.4-i004-x86_64.exe file and installed it; installation seems successful but afterwards the GUI fails to start: > > cannot create HKLM\Software\Openvpn-GUI key > > Running the gui with elevated privileges fixes this issue. Shouldn't the installer have created this registry key? > This is on Windows 7 Pro 64bit. > Hi Jan, Currently the installer does not currently create or update the OpenVPN-GUI registry keys. This is primarily for historic reasons - OpenVPN-GUI has never had it's own installer, so it sets up it's own environment during first startup (as admin). I've written a separate NSI installer script for OpenVPN-GUI[*], which will take care of updating the keys as necessary. The plan is to include the OpenVPN-GUI installer in OpenVPN 2.4 installers only to avoid introducing installers bugs in our stable releases. In my opinion the registry key generation should be removed from OpenVPN-GUI when the installer is fully functional, tested and integrated with OpenVPN. Samuli [*] The NSI script should be in openvpn-gui Git repository -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRGJeYACgkQwp2X7RmNIqM6MgCeJjolkqW8gzufaZ+Qj84GfJGr ypgAoJrcJLDQQQ49p/dVSSjWHLd0cNwD =UTHP -----END PGP SIGNATURE-----
