What are the WiFi device/driver encryption requirements to pass WHQL tests?

Question

Hi all,

We are developing a WiFi driver for Windows 11 using the (new) wificx library. The driver is for a customer-specific hardware.

Driver implementation is about to be finished, and everything worked quite well so far. We are now starting WHQL certification. It looks like the WHQL testbench WiFi tests require a WPA2-PSK/AES encryption to pass, but our hardware supports WPA3-SAE and OWE encryption, only, for now.

Is it possible to select the type of encryption used by WiFi driver WHQL tests? Is there anyone out there who can share experiences on this?

Thanks, Frank

Answer 1

The WHQL (Windows Hardware Quality Labs) tests for WiFi drivers typically require support for WPA2-PSK/AES encryption. However, if your hardware only supports WPA3-SAE and OWE encryption, it may not meet the current WHQL certification requirements, which could lead to difficulties in passing the tests.

As of now, there is no indication that you can select the type of encryption used by the WHQL tests. The tests are designed to ensure compatibility and security standards that include WPA2-PSK/AES as a baseline. Therefore, you may need to consider implementing support for WPA2-PSK/AES in your driver to meet these certification requirements.

It's advisable to check the latest WHQL testing guidelines or reach out to Microsoft for any updates or possible exceptions regarding the encryption requirements for your specific scenario.

---

References:

• What's new in driver development for Windows 11, version 24H2

Answer 2

Hi @Frank ,

Thanks for reaching out.

When you try to pass the WHQL Wi‑Fi tests, Microsoft expects your driver to support WPA2‑PSK with AES encryption. This is the “standard” Wi‑Fi lock that the tests know how to check. Right now, your hardware only supports WPA3‑SAE and OWE, which are newer and stronger, but the tests don’t know how to use them. Some of the Windows HLK Wi‑Fi roaming and connection tests explicitly configure access points to use WPA2‑PSK/AES as part of their prerequisites:

https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/fd7a55cd-4f03-42d9-b471-39bd14fe5edc

Unfortunately, there isn’t a way to tell the WHQL test suite to use a different encryption type - the test tool always looks for WPA2‑PSK/AES during those connection tests. Another prerequisite page that shows the expected supported suites is here:

https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/798d6fe1-39ea-4800-b782-add4e7aa6b04

Most device makers in this situation do one of two things:

1. Add temporary support for WPA2‑PSK/AES just so the driver can pass the WHQL tests. After certification, they can focus on WPA3 or OWE for real‑world use.
2. Ask Microsoft/HLK support if there’s a newer test plan (or updated HLK guidance) that supports WPA3‑only workflows - especially as Wi‑Fi certification moves forward. Also make sure you follow the official HLK test setup guidance here: https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/wireless-lan--80211--testing-prerequisites

So in short: to pass WHQL, your driver probably needs at least some support for WPA2‑PSK/AES, even if it prefers WPA3 or OWE in normal use. Many device makers follow this approach during WHQL certification, so you’re not alone - it’s a common requirement for new Wi‑Fi hardware.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Answer 3

Thank you, Jack for getting back with these helpful comments.

We were partly successful by using option 1 from above (add temporary support for WPA2). Most of the basic tests passes now.

The driver is for a USB WiFi stick (station mode) that implements the IEEE 802.11ah standard (WiFi HaLow). Thus, we can only connect to APs that support this standard, too. Because of this we see now chance to fulfill all the Windows HLK Wireless LAN (802.11) Testing Prerequisites (link in option 2 above).Are there options to use a modified test setup to pass WHQL certification for a hardware/driver combination that is not compliant to the conventional IEEE 802.11ac standard? How do we get help from the Microsoft/HLK support team regarding this?

Thanks, Frank