WHQL Testing
{{Short description|Certification for device drivers on Windows}}
{{update|date=April 2016}}
The Windows Hardware Certification program (formerly Windows Hardware Quality Labs Testing, WHQL Testing, or Windows Logo Testing) is Microsoft's testing process which involves running a series of tests on third-party device drivers, and then submitting the log files from these tests to Microsoft for review. The procedure may also include Microsoft running their own tests on a wide range of equipment, such as different hardware and different Microsoft Windows editions.
Overview
File:CertifiedForVistaLogo.gif
File:FoundNewHardwareWizard.png]]
The WHQL project was started since Windows 95. {{Cite web |title=Q158957: DirectX: Description of the DirectX Setup (Dxsetup.exe) Tool |url=https://jeffpar.github.io/kbarchive/kb/158/Q158957/ |access-date=2025-05-14 |website=KnowledgeBase Archive |language=en-US}} Windows 2000 added support for WHQL signature checking. {{Cite web |title=Q281770: How to Perform Clean-Boot Troubleshooting for Windows 2000 |url=https://jeffpar.github.io/kbarchive/kb/281/Q281770/ |access-date=2025-05-14 |website=KnowledgeBase Archive |language=en-US}}
Products that pass the WHQL tests get to use a "Certified for Windows" logo aka "Designed for Windows" logo, 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. (In the past, Microsoft also awarded a similar logo as part of a different Software Certification program to apps that passed software compatibility tests.)
For device drivers passing the WHQL tests, Microsoft creates a digitally signed certification file that, when included in the driver installation package, prevents Windows from displaying a warning message that the driver has not been certified by Microsoft.
Since June 2007, Microsoft has added an Audio Fidelity Test (Audio Precision SYS-2722-A-M) requirement for System Submissions.{{Cite web
|url = http://www.microsoft.com/whdc/whql/audiofidelity.mspx
|title = Windows Vista Logo Program - Audio Fidelity Testing Policy Update
|work = Windows Hardware Developer Central website
|publisher = Microsoft Corporation
|date = 18 June 2008
|accessdate = 7 February 2011
|archive-url = https://web.archive.org/web/20091212103252/http://www.microsoft.com/whdc/whql/audiofidelity.mspx
|archive-date = 12 December 2009
|url-status = dead
|df = dmy-all
}}
A company can choose to sign their own drivers rather than go through the WHQL testing process. These drivers would not qualify for the "Certified for Windows" logos, but they would install on Windows without a warning.{{cite web
|url = http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx
|title = Digital Signatures for Kernel Modules on Systems Running Windows Vista
|date = July 27, 2007
|accessdate = 2008-07-30
|publisher = Microsoft Corporation
|work = Windows Hardware Developer Central website
|archive-url = https://web.archive.org/web/20080725062506/http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx
|archive-date = July 25, 2008
|url-status = dead
|df = mdy-all
|url = http://www.tech-archive.net/Archive/Development/microsoft.public.development.device.drivers/2009-04/msg00098.html
|title = Re: Digital sign a driver for XP and Vista
|work = tech-archive.net
|date = April 8, 2009
|accessdate = 7 February 2011
|first = Tim
|last = Roberts
}} However, in some cases, such as drivers created after the termination of WHQL testing for a version of the operating system, the Windows operating system may refuse to start the driver and will require enabling the operating system's test mode by a command prompt to otherwise run it.
Device drivers that have passed the WHQL tests are also made available for download using Windows Update or the Microsoft Update Catalog. Not all of the drivers in Windows Update are up to date. On Windows XP, when Windows detects a new device for which it does not have built-in drivers, it shows a Found New Hardware Wizard dialog box. Microsoft has since dismantled this dialog box, but one way to avoid it on Windows XP was to pre-install a WHQL-certified driver before connecting the device.
Since 7 January 2014, Microsoft no longer requires a WHQL testing fee,{{cite web
|url = http://download.microsoft.com/download/4/D/D/4DD894CD-62C8-488F-944D-4E5F8BA40114/hardware-certification-policies-processes-hck2-1.docx
|format=DOC
|title = Hardware Certification Policies and Processes
|publisher = Microsoft Corporation
|date = 7 January 2014
|accessdate = 24 June 2015
}} which used to be US$250 per operating system family.{{cite web
|url = http://winqual.microsoft.com/download/DTM%20Global%20WHQL%20POLICY.doc
|format = DOC
|title = DTM Global WHQL Policies Draft
|publisher = Microsoft Corporation
|date = 21 August 2006
|accessdate = 7 February 2011
|page = 28
|first = Lyndon
|last = Bethel
}} This fee covered both x86 and x64 driver SKUs, if submitted simultaneously, and was non-refundable. The fee did not include other expenses, such as the Windows license necessary for running WHQL tests, and the VeriSign certificate necessary for submitting test results.{{cite web
|url = http://msdn.microsoft.com/en-us/windows/hardware/gg463010.aspx
|title = Windows Logo Kit 1.6 Step by Step Guide
|publisher = Microsoft Corporation
|date = 13 September 2011
|accessdate = 22 November 2011
}}
See also
- Windows Hardware Lab Kit (WHLK)
- Windows Hardware Certification Kit (WHCK)
References
{{Reflist}}
External links
- [https://developer.microsoft.com/windows/hardware Windows Hardware Developer Center] (WHDC)