But because Wintun advertised itself as a virtual device it had a narrower scope and had to pass fewer HLK tests (~50 in total) than tap-windows6 (68 tests with filters applied).įor the HLK controller you can use a virtualized (Virtualbox, VMware) Windows Server 2016 or 2012r2 instance.įor tap-windows6 testing a support machine is also needed. Wintun was able to pass HLK testing without any physical HLK clients.
His work has now been merged to the upstream tap-windows6 project Sgstair patched tap-windows6 to pass the HLK tests. Apparently that particular piece of MS documentation was written at a time when MS was _planning_ to require WHQL-certified drivers for Windows Server 2016+, then backpedaled and forgot to update the documentation. Our installers have attestation-signed drivers and no Windows Server 2016/2019 users have complained. This claim contradicts the "official" Microsoft documentation but trust me, it is true. An attestation-signed driver is good enough. NOTE: it is not required to pass the HLK tests just to get a driver that loads on Windows Server 2016/2019. Therefore some of the requirements documented in this article are bound to change.ĭifferent Windows versions have different kernel-mode signing options:
Practical testing is often required to understand the requirements fully.
Microsoft has some documentation about HLK testing and WHQL signing, but it is quite incomplete, and there is lots of room for speculation and anecdotes.
0 kommentar(er)
