wincas.blogg.se

Advanced installer registry wow6432node
Advanced installer registry wow6432node












advanced installer registry wow6432node

When we went and removed the COM Extract at Build from all our components that had files self registering the issue went away. If the files have Self Register checked it will cause the issue you are seeing. Expand that component and look at the files. If you open your install shield project and look at the components, some will have the COM Extract at Build property set to yes. Also, as Gert said, testing procedures will be simplified a bit.I have seen this issue at my work. Plus support should a bit easier as we know in which registry the registry keys will be, and that usually OpenVPN is installed to C:\Program Files\OpenVPN. For many this may not be an obvious choice. Significant increase indeed, but the total size (3724 KB) is still quite reasonable imho.Īs for the actual benefits: people no longer have to figure out whether they need (or should have) a 32-bit or 64-bit version. The combined installer is only 1.66x the size of the old 64-bit installer, or 1.93x larger than the 32-bit installer. I'm sure there is a way, I just don't know how complex it would be. Well this is indeed something that can be trivially fixed, now that the file is hosted in openvpn-build. "log_dir"="C:\\Program just a variant of " ​Value of exe_path in registry not updated during reinstall" issue you linked to. are not uninstalled? How did you do this? Looking at openvpn.nsi it looks like the Uninstall section is static (=remove everything, always). Double the size of the download and for no good reason.ĭoes "OpenVPN only" means that the service, openssl, lzo, etc. I Still do not like joint 32/64bit installer.Is it possible to set the "readme" to explicitly open "on top" of all other windows because it quite often opens below other windows.The "readme" file: INSTALL-win 32.txt even on 64bit."log_dir"="C:\\Program config_dir, exe_path and log_dir are not correct. Install Openvpn to a different path (eg: C:\#Tools)."exe_path"="C:\\Program Files\\OpenVPN\\bin\\openvpn.exe"

advanced installer registry wow6432node

"config_dir"="C:\\Program Files\\OpenVPN\\config" To reproduce (All actions are "Run as administrator"):ĭelete registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Openvpn These are the full details of this problem and as it has been outstanding for over three years. !insertmacro WriteRegStringIfUndef HKLM "SOFTWARE\Wow6432Node\$" "" "$INSTDIR"Īnd it works fine with OpenVPN-GUI 5.0.0.ĭon't know about other versions of the OpenVPN-GUI. In my combined installer i use the 圆4.nsh and if statements so it installs the regvalues correct.














Advanced installer registry wow6432node