On Thu, Apr 02, 2020 at 21:16:48 +0300, Samuli Seppänen wrote: > The installer I extracted had a sha1sum of > > 9c3fa39b6dc1ca9a02bf940c0509cf58a13fdf7d > > That matches the sha1sum of openvpn-install-2.4.8-i602-Win10.exe's which > I just a few minutes ago downloaded from the official download page and > our alternative download server:
Yes, this matches the other copies of the installer we have (though unfortunately on the machine where this failed, the installer .exe file was not saved, so I guess there is some remote possibility that it was not the same file, somehow). > > <https://swupdate.openvpn.org/community/releases/openvpn-install-2.4.8-I602-Win10.exe> > <https://build.openvpn.net/downloads/releases/openvpn-install-2.4.8-I601-Win10.exe> > > At this point I have no clue where a Windows 7 version of the driver > could have appeared from, unless: > > - The installer you're using is somehow accidentally not the correct one > - Windows has the Windows 7 driver hidden somewhere (Driver Store) Would this second option be consistent with the fact that the failed setupapi log says the driver package was "already imported? Is "oemvista.inf_amd64_6d4bec28a2ef0cdf" a name that is hard-coded inside the TAP-Windows installer, or is that generated dynamically at installer-execution time? Anway, I will see if I can determine anything by checking the timestamps for the various c:\windows\ files mentioned in the log, etc. Nathan ---------------------------------------------------------------------------- Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
