openvpn-install-2.3.3-I001-x86_64.exe installing old 2.3.2?

[hildeb]

Today I installed openvpn-install-2.3.3-I001-x86_64.exe
Looking at the log, I found the version to be 2.3.2 -- error in the version string or did you forget to actually upgrade the binary in the installer?

[Samuli Seppänen]

Both openvpn-install-2.3.3-I001-x86_64.exe and openvpn-install-2.3.3-I001-i686.exe contain openvpn 2.3.3, just tested both. Also, due to architecture of the openvpn-build buildsystem it would be nearly impossible to build an installer which has 2.3.3 in it's name, but which would contain the openvpn 2.3.2 binary.

Are you 100% sure you did not install 2.3.2 by mistake? If you are sure, please check the md5sum of the installer (e.g. with Git Bash):

$ md5sum.exe openvpn-install-2.3.3-I001-x86_64.exe
a83b6adf1f587a3f78b2328618242d52  openvpn-install-2.3.3-I001-x86_64.exe

Also check the md5sum of openvpn.exe itself:

$ md5sum.exe openvpn.exe
68eb5d2340ebc9d66aef7b0a5406e698 openvpn.exe

If your md5sums for openvpn-2.3.3 do not match those above, then something odd has happened, and we need to look into this in more details.

[Gert Döring]

The old installer did not properly terminate an already-running openvpn. So if your openvpn.exe was active while installing the upgrade, the binary can not be overwritten, and will silently be kept "old".

Yes, this is an installer bug and I'm confident 2.3.4-I001 will get this right :-)

I'm closing this ticket now - Samuli has verified that the builds are good, and we're reasonably certain what caused the effect for you (and nobody else reported it).