Hi, > > Is your computer perhaps behind in Windows updates? My hunch is that > > Digicert's latest root certificate is not availabe in the Windows > > certificate store and this causes the failure. > > > > Samuli > > thanks for the hint! but I don't know why uninstall/reinstall make > things work?
Mind that this OpenVPN release also brings the TAP-Windows6 driver update - first one after some years. That's why there were no issues upgrading the OpenVPN in the past years. The TAP-Windows6 driver remains loaded when there are TAP adapters present. Even if adapters are in the "disconnected" state. This makes upgrading the driver a real challenge. I would suggest disabling all TAP adapters before attempting the upgrade. Disabling the last of the TAP adapters will cause Windows kernel to unload the TAP-Windows6, allowing its upgrade. > our windows 7 update is stay at 2019-8, which is not very far behind. > but we do security-only update to prevent telemetry, I don't know if > that make difference. > I will try again when windows update mess quiet down. December patch > is always good these years. hope it is the same this year. 1. Windows 7 have issues with SHA-256 signatures. In general, it works. But, for optimal experience you should install KB2921916 (not available via Windows Update). Maybe that's the reason for driver signature verification failure recorded in your log. Probably, this error is recorded in the log on all Windows 7 computers without KB2921916. 2. Mind that initial release of OpenVPN 2.4.8 is shipped using separate installers for Windows 7/8/8.1/Server2008R2/Server2012R2 _and_ Windows 10/Server2016/Server2019. Please, make sure you are using the first one on Windows 7. We do plan to unify the installers back to a single one in future releases to avoid confusion. Regards, Simon
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
