First published on MSDN on Apr 27, 2018
The Windows Hardware Lab Kit (HLK) has been updated to support Windows 10, version 1803 and is available via direct download, here: http://aka.ms/1803HLK . The 1803 version of the HLK enforces revisions to the Windows 10, version 1803 hardware compatibility requirements available from the Hardware Dev Center .
Note: Starting with the last release of HLK version 1709, the HLK will support testing a single version of Windows 10. (The version prior to HLK version 1703 can support testing multiple versions.)
The following support scenarios will be accepted:
When submitting a Windows 10, version 1803 HLK package for validation, you must use Windows 10, version 1803 build 17134 or newer on the test device. Otherwise, the submission will be rejected.
You must continue to use the Windows Hardware Certification Kit (HCK) version 2.1 to certify for following operating systems:
You must continue to use the Windows Logo Kit (WLK) version 1.6 to certify for following operating systems:
Certification for Windows Server 2016, Azure Stack and SDDC must:
Questions about the Azure Stack or SDDC program or how to submit the results for solution validation should be directed to the appropriate Microsoft contact – your technical account manager or partner management contact.
With the change in the policy regarding which versions of Windows 10 the HLK will validate, it is important to note which tests are required with each kit. Playlists must match the HLK version used, not the Windows 10 version under test.
The required playlists pairing are:
*Testing ARM64 Desktop requires two playlists. Please see HLK client setup and testing guidance here for additional information: http://aka.ms/InstallHLK .
All playlists are available at http://aka.ms/HLKPlaylist .
Partners looking to achieve compatibility for systems shipping Windows 10, version 1803 may factory-install drivers for components that achieved compatibility with Windows 10, version 1709 until July 30, 2018.
Errata 33064 filter is available to mask the failures seen when testing a system and the latest errata filter package can be found at http://aka.ms/hlkfilters . This policy is not applicable to partners certifying for Windows Server 2016, as all components within the system must be certified for Windows Server 2016 in order to be considered compatible.
Certification for Windows Server 2016, Azure Stack and SDDC must:
Questions about the Azure Stack or SDDC program or how to submit the results for solution validation should be directed to the appropriate Microsoft contact – technical account manager or partner management contact.
As previously mentioned, submissions for Windows 10, version 1803 must use HLK version 1803. Note that if you are submitting results for Windows 10 version 1803, the results must be packaged for submission using a controller with HLK version 1803 installed. If a controller with any older version of HLK (such as HLK 1709) is used to package and submit results for Windows 10, version 1803, the submission will fail because the data in the package will not be in the correct format.
Submissions affected by this will appear to be stuck in the Validating HCK/HLK Submission Package step. We will monitor for this scenario and reach out to partners with affected submissions. A controller with HLK version 1803 installed can be used to submit results from previous kits (HCK/HLK).
Dev Center has adopted the HLK 1803 Package Manager to generate the DUA Shell for all DUA submission requests, including the submissions that are created from the previously released of HLK Studio. Since the DUA Shell is generated by the HLK 1803 Package Manager, it can only be repackaged by the same version of HLK. When an older version of HLK Studio is used, you will get an error message of “ The package version 3.5.0.0 is not compatible with this version of the kit. Please update your kit version and try again. ”
Please make sure the HLK 1803 Studio is used when repackaging a DUA submission.
The Windows Hardware Lab Kit (HLK) has been updated to support Windows 10, version 1803 and is available via direct download, here: http://aka.ms/1803HLK . The 1803 version of the HLK enforces revisions to the Windows 10, version 1803 hardware compatibility requirements available from the Hardware Dev Center .
Note: Starting with the last release of HLK version 1709, the HLK will support testing a single version of Windows 10. (The version prior to HLK version 1703 can support testing multiple versions.)
The following support scenarios will be accepted:
| HLK version | Supported version | Accepted device/component | Accepted system |
| 1803 | 1803 – Client | 1803 Client Device/Component | 1803 Client Systems |
| 1709 | 1709 – Client | 1709 Client Device/Component | 1709 Client Systems |
| 1703 |
1703 – Client
1607 - Client |
1703 Client Device/Component
1607 Client Device/Component |
1703 Client Systems |
| 1607 |
1607 – Client
1607 – Server, Azure Stack, SDDC 1511 - Client |
1607 Client Device/Component
1607 Server Device/Component 1511 Client Device/Component |
1607 Server Systems |
When submitting a Windows 10, version 1803 HLK package for validation, you must use Windows 10, version 1803 build 17134 or newer on the test device. Otherwise, the submission will be rejected.
You must continue to use the Windows Hardware Certification Kit (HCK) version 2.1 to certify for following operating systems:
- Windows 7
- Windows 8
- Windows 8.1
- Windows Server 2012
- Windows Server 2012 R2
You must continue to use the Windows Logo Kit (WLK) version 1.6 to certify for following operating systems:
- Windows Server 2008 R2 (x64 and ia64)
- Windows Server 2008 (x86, x64 and ia64)
Certification for Windows Server 2016, Azure Stack and SDDC must:
- Meet the Windows Hardware Compatibility Requirements as stated in version 1607 of the documentation
- Use the 1607 version of the Windows Server 2016 operating system
- Use HLK version 1607 build 14393 with matching playlist and supplemental content to generate logs
- Follow the policies stated in the Windows Server Policy .
Questions about the Azure Stack or SDDC program or how to submit the results for solution validation should be directed to the appropriate Microsoft contact – your technical account manager or partner management contact.
Playlists to support the incremental Windows releases
With the change in the policy regarding which versions of Windows 10 the HLK will validate, it is important to note which tests are required with each kit. Playlists must match the HLK version used, not the Windows 10 version under test.
The required playlists pairing are:
| HLK Kit version | Architecture | Playlist |
| 1803 | x86 or x64 | HLK version 1803 CompatPlaylist x86_x64 |
| ARM64 Desktop* |
HLK Version 1803 CompatPlaylist ARM64
HLK Version 1803 CompatPlaylist ARM64_x86 on ARM64 |
|
| 1709 | x86 or x64 | HLK Version 1709 CompatPlaylist x86_x64 |
| 1709 | ARM64 Desktop* |
HLK Version 1709 CompatPlaylist ARM64
HLK Version 1709 CompatPlaylist ARM64_x86 on ARM64 |
| 1703 | X86 or x64 | HLK Version 1703 CompatPlaylist |
| 1607 | X86 or x64 | HLK Version 1607 CompatPlaylist |
*Testing ARM64 Desktop requires two playlists. Please see HLK client setup and testing guidance here for additional information: http://aka.ms/InstallHLK .
All playlists are available at http://aka.ms/HLKPlaylist .
Windows 10, version 1803 may ship with drivers that achieved compatibility with Windows 10, version 1709 until July 30, 2018 !
Partners looking to achieve compatibility for systems shipping Windows 10, version 1803 may factory-install drivers for components that achieved compatibility with Windows 10, version 1709 until July 30, 2018.
Errata 33064 filter is available to mask the failures seen when testing a system and the latest errata filter package can be found at http://aka.ms/hlkfilters . This policy is not applicable to partners certifying for Windows Server 2016, as all components within the system must be certified for Windows Server 2016 in order to be considered compatible.
Certification for Windows Server 2016, Azure Stack and SDDC must:
- Meet the Windows Hardware Compatibility Requirements as stated in version 1607 of the documentation.
- Use the 1607 version of the Windows Server 2016 operating system.
- Use HLK version 1607 build 14393 with matching playlist and supplemental content to generate logs.
- Follow the policies stated in the Windows Server Policy .
Questions about the Azure Stack or SDDC program or how to submit the results for solution validation should be directed to the appropriate Microsoft contact – technical account manager or partner management contact.
Submitting test results for Windows 10, version 1803
As previously mentioned, submissions for Windows 10, version 1803 must use HLK version 1803. Note that if you are submitting results for Windows 10 version 1803, the results must be packaged for submission using a controller with HLK version 1803 installed. If a controller with any older version of HLK (such as HLK 1709) is used to package and submit results for Windows 10, version 1803, the submission will fail because the data in the package will not be in the correct format.
Submissions affected by this will appear to be stuck in the Validating HCK/HLK Submission Package step. We will monitor for this scenario and reach out to partners with affected submissions. A controller with HLK version 1803 installed can be used to submit results from previous kits (HCK/HLK).
Driver Update Acceptable (DUA) Shell will be generated from the HLK 1803 Package Manager
Dev Center has adopted the HLK 1803 Package Manager to generate the DUA Shell for all DUA submission requests, including the submissions that are created from the previously released of HLK Studio. Since the DUA Shell is generated by the HLK 1803 Package Manager, it can only be repackaged by the same version of HLK. When an older version of HLK Studio is used, you will get an error message of “ The package version 3.5.0.0 is not compatible with this version of the kit. Please update your kit version and try again. ”
Please make sure the HLK 1803 Studio is used when repackaging a DUA submission.
Published Mar 12, 2019
Version 1.0
