Windows Hardware Quality Labs (WHQL)

Windows Hardware Quality Labs or WHQL is Microsoft‘s testing process which involves in running a set of tests on third-party hardware or software application, and submitting the log files from these tests to Microsoft for review.

Products that pass the WHQL tests get to use a”Certified for Windows” logotype, which certifies that the Hardware or software has had some share of testing by Microsoft to ensure compatibility. The actual logo used depends on the version of Microsoft Windows.

Certified for Vista Logo

At the end of this testing process, Microsoft signs the driver release with their own certificate to indicate that the driver has passed testing.

Independent Hardware Vendors (IHVs) that participate in this program can submit driver packages to be test-signed. The signature on a test-signed catalog file is generated by a test root certificate that is issued by WHQL under the Microsoft Test Root Authority. Along with the test-signed catalog file, WHQL also provides participants with the test root certificate.

WHQL Signing Advantages:

  1. Devices that pass the WHQL process are eligible to use the Windows logo for marketing use..
  2. Windows driver installations won’t display a warning indicating that the device driver has not passed logo certification.
  3. Driver catalog is signed by WHQL (Microsoft) rather than a third party.
  4. During WHQL testing, drivers are installed and uninstalled many times and in different orders for stress testing which helps to resolve most BSOD cases are caused by installation and power management problems.


Setup for WHQL process divided into two part,HCK(Hardware Certification Kit) and HLK(Hardware Lab Kit).Before users can install a driver from a WHQL test-signed driver package, the test computer must be configured

  1. To run these tests you will need at least two computers: a test server and a test client.
  2. The User Account Control (UAC) must be disabled to install the WHQL test certificate correctly.
  3. The WHQL test root certificate (Testroot.cer) must be installed in the test computer
  4. The TESTSIGNING Boot Configuration Option must be set on the test computer.
  5. For HCK, windows server can be Win2012/Win2012R2 and test system version must be win7(32/64) or win server 2008 and above
  6. For HLK, windows server can be Win2012/Win2012R2 and test system version must be win10 or server 2k16.

Use cases:

  1. For driver testing ,Compatibility of driver with any other driver using WHQL.
  2. Driver operate in GUI and server core version.
  3. Driver inf verification.
  4. Driver Memory Test





Related Posts

The Evolution of Testing in the Digital Era

The Evolution of Testing in the Digital Era

Customers quickly reject buggy software, and as a result, software testing has acquired great importance in the modern day. In this article, we trace the evolution of testing, and see if we can learn any lessons from the past. Read it here.

The Evolution of a Strategic Product Development Relationship

The Evolution of a Strategic Product Development Relationship

Building a strategic product development relationship is difficult, but rewarding. In this article, Parag Kulkarni lays out the logical steps to select a product development partner that’s perfect for you.


9 Quick & Easy Tips for a Robust QA Strategy

To explore our end-to-end QA offerings, visit our website or get in touch for a free consultation.


Why Should Software Testing Matter to Retail Enterprises?

A superlative & consistent customer experience is the mainstay of a retail enterprise. What role does software testing play to ensure customer loyalty for a retail product company? Read on to know more.


Smart Testing in the Age of Machine Learning

While test automation has helped product companies keep up with the required delivery speed, incorporating AI/ML capabilities in test automation will be a futuristic approach to take. Check out this blog to delve into the details.


After the 2020 Curveball – What’s in Store for QA?

QA & testing is in a state of rapid evolution since 2020. Keep reading to know and be prepared for what the future of software testing may hold.


Leave a comment / Query / Feedback

Your email address will not be published. Required fields are marked *