Il 14/07/2018 20:22, Simon Rozman ha scritto: > Hi! > > Does anybody have some specific Windows 2016 Server release and build > numbers from which on they require HLK certified driver? Or, do all Windows > 2016 Server versions require HLK certified drivers from initial release on? > > I am adding a detection logic to pack multiple TAP drivers in a single MSI > and install only one conditionally - and would not like to reinvent the > wheel. > > Best regards, > Simon > >
Hi, Greetings from my vacation! In general Windows Server 2016 versions require HLK certified drivers. Our old tap-windows6 driver works only because it fits Microsoft's exceptions. It would love to have automatic OS detection in the MSI. For official releases we'd have two separate drivers (for now): - For Windows Server 2016 - Comes with MS signature based on HLK test results - For Windows 7/8/10, Windows Server 2008r2 and 2012r2 - Comes with dual signatures - Cross-signed for everything except recent Windows 10 - Attestation signed for recent Windows 10 Getting a single driver that works across the board would prohibitively expensive time- and money-vise. This is because we'd have to pass WLK, HCR and HLK tests on pretty much every supported Windows version known to man in every bitness. So we need either auto-detection (=best) or separate installers. I will do the latter for starters so that my vacation is not ruined. But soon after we should switch to the MSI-based installer with OS- auto-detection. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel