WHLK testing for Windows 10 2004

[xv-avram-m]

Running the tests for the 2004 version of Windows 10, running into a bunch of failures, with several blue screens, on both the Client and the Support machine.

• 1c_ioctlcoverage
• 1c_Mini6PerfSend
• 1c_Mini6Send
• 1c_OidsDeviceIoControl
• 1c_WMICoverage
• 2c_Mini6Performance
• 2c_OidsNdisRequest
• 2c_Priority
• AddressChange
• PacketFilters
• ShortPackets

Has anyone managed to get a successful pass on the 2004 build yet with Product Type LAN? Or anyone have an idea how to get these passing. A lot of the failures seem to revolve around failing to query OIDs.

[mattock]

I have not heard of anyone pulling that of. I stopped trying to get HLK tests to pass when I learned that an attestation signature is good enough to get tap-windows6 to load on Windows Server 2016/2019. The official Microsoft document which claims otherwise is wrong. Too bad we learned this after putting a huge investment of time and money into HLK.

Just in case you have not found our HLK testing documentation yet:

• https://community.openvpn.net/openvpn/wiki/HLKTesting

Please add your findings to the document.

[xv-avram-m]

I'm going to remove the failing tests and attempt HLK certification as an "other driver" - should be enough, if it works. We do need HLK, sadly.

Will update the wiki with any useful info.

[mattock]

Ok, thanks!