Windows Hardware Certification articles

Windows Hardware Compatibility Program - Guidance for Windows 11, version 24H2 Release

AndyW — Wed, 22 May 2024 19:48:50 GMT

To facilitate the release of Windows 11, version 24H2, and Windows Server 2025, the Windows Hardware Compatibility Program is set to accept submissions. The submission package must fulfill the prerequisites to guarantee compatibility between the operating system and the Hardware Lab Kit (HLK).

New Agreement - Please review and take action on the latest agreement update to avoid service interruption following the effective date of the new agreement.

Windows Hardware Compatibility Requirements – https://aka.ms/whcp

Submission Pre-requisites

OS and HLK minimum acceptable build:
- Windows 11, version 24H2 (Build 26100 or greater)
- Windows Server 2025 (Build 26100 or greater)

Playlist – https://aka.ms/hlkplaylist

The table below illustrates the required playlists for testing each processor architecture:

Target Architecture	Required Playlist(s)
Client (ARM64)¹	HLK Version 24H2 CompatPlaylist x64 ARM64.xml HLK Version 24H2 CompatPlaylist ARM64_x86_on_ARM64.xml HLK Version 24H2 CompatPlaylist ARM64_x64_on_ARM64.xml
Client (X64)	HLK Version 24H2 CompatPlaylist x64 ARM64.xml
Server (X64, ARM64)	HLK Version 24H2 CompatPlaylist x64 ARM64 SERVER.xml

¹For Client system-level x64 and ARM64 submission, the only playlist required is the HLK Version 24H2 CompatPlaylist x64 ARM64.xml

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Deferment of Partner Dev Center SBOM Validation

The WHCP requirement, for partner SBOM submissions alongside driver packages submitted to HDC, will be deferred at HDC. Partners will be given notice as soon as there is a set enforcement date during a future release, along with guidance on how to meet any new requirements.
WHCP continues to support a secure supply chain throughout our signing process. That said, the EO on Cyber Security is a call to action from the U.S. Government, so we continue to encourage that our partners seek to enable a secure supply chain as stated in the NIST guidance.

Device.DevFund.StaticTools Requirement

The Device.DevFund.StaticTools requirement applies to Windows 11 Client x64 and Windows Server x64.
Helpful information about how to use CodeQL and generate DVL files is available here - CodeQL and the Static Tools Logo Test - Windows drivers | Microsoft Learn

ACTION REQUIRED: New Agreement governing access to Hardware Dev Center

AndyW — Mon, 13 May 2024 17:07:36 GMT

We have updated the agreements on Partner Center for the Windows Hardware Program. We made these updates to clarify our terms and ensure that they are transparent, as well as to address usage of new logos.

All participants in the Hardware Program are required to have their authorized personnel review, acknowledge, and accept the agreements. New submissions will be blocked after August 14, 2024 until the agreements are accepted.

Partners who have accepted prior versions of the agreement via other means will still need to accept the agreement on Partner Center. For partners who have already been a part of the program, you will see the previous agreement, the Windows Logo License Agreement from 2021, has been renamed and is now listed in the Agreements section of Partner Center as "Microsoft Marks License Agreement (formerly Windows Logo License Agreement)" with the value in the Agreement column of Version 2021.

As a result, partners who previously accepted the Windows Logo License Agreement will see two entries in the Agreements section:

The new Microsoft Marks License Agreement, with Version 2024.
The previous Windows Logo License Agreement, now renamed to "Microsoft Marks License Agreement (formerly Windows Logo License Agreement)" with the value in the Agreement column of Version 2021.

Going forward, the four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated.

· Code Signing Agreement

· Windows Hardware Compatibility Agreement

· Microsoft Marks License Agreement 2024 (New)

· Windows Analytics Agreement v2.0

If you encounter issues accessing the new agreements, please reach out to our support team. For details on how to contact support, see Get support for Partner Center dashboard issues - Windows drivers | Microsoft Learn.

Windows Hardware Compatibility Program Guidance for Windows 11, version 23H2

AndyW — Wed, 27 Sep 2023 16:12:49 GMT

Microsoft is pleased to announce the release preview of Windows 11, version 23H2 annual feature update, which shares the same servicing branch and code base as Windows 11, version 22H2, and will be delivered via an enablement package (eKB). See Windows 11 Release information for more information on the annual feature update cadence.

In support of the annual feature update, the Windows Hardware Compatibility Program (WHCP) will also release a Hardware Lab Kit (HLK) update to complement the feature updates within the Windows release. There is no plan to update the certification status issued by the HLK: the certification status that was used for the HLK for Windows 11, version 22H2, which is “Certified for Microsoft Windows 11 Client family version 22H2”, will continue to be used for this this HLK release for the Windows 11, version 23H2 update.

While there are no changes to WHCP or certification status, the updated HLK release with Windows 11, version 23H2 will be required when using Windows 11, version 23H2 to certify. Note, certifying for Windows 11, version 23H2 is optional.

Details

WHCP requirements – No change. Windows 11, version 22H2 requirements, remain the same for Windows 11, version 22H2 and the new 23H2.
Windows Hardware Lab Kit – For Submissions, HLK 22H2 to be used with Windows 11, version 22H2 and HLK 23H2 to be used with Windows 11, version 23H2
Driver signature – No change. Drivers that meet all the applicable Windows 11, version 22H2 requirements will be digitally signed with the same signature attributes.
WHCP qualification – No change. Qualification will be shown as Windows 11, version 22H2
Required OS version – Windows 11, version 22H2 or Windows 11, version 23H2.
WHCP Playlists – Please using the version matching HLK and playlist for the OS version

Windows 11, version 22H2 – HLK 22H2 and Playlist 22H2
Windows 11, version 23H2 – HLK 23H2 and Playlist 23H2
Differences is a total of 9 tests added to the “HLK Version 23H2 CompatPlaylist x64 ARM64.xml” playlist.

Windows HLK playlist – New HLK playlists will be available on the date of Windows 11, version 23H2 release, and can be found here.
Technology areas in HLK that took bug fixes:

Audio APO
Audio - Silicon and Pipeline
Bluetooth
Encoders

ACTION REQUIRED: New Agreements governing access to HDC

AndyW — Fri, 17 Feb 2023 17:28:19 GMT

As a reminder of the comm published on Jan 25, 2023, two new agreements are available on Partner Center for the Windows Hardware Compatibility Program. To avoid service disruption, please prioritize to review and decide the required agreements before they become effective on Feb 28, 2023

We recently added new agreements to Partner Center for the Windows Hardware Program. We made these updates to clarify our terms and ensure that they are transparent, as well as to cover new government mandates. All participants in the Hardware Program are required to have their authorized personnel review, acknowledge, and accept the agreements. New submissions will be blocked after February 28, 2023 until the agreements are accepted.

The four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated.

Windows Server Catalog Changes to Support New Windows Server 2022 Network Additional Qualifications

Sandy_Arthur — Thu, 08 Sep 2022 01:27:32 GMT

Summary

On August 31^st Microsoft went live with an update to the Windows Server Catalog (www.windowservercatalog.com) that will ensure that customers who rely on the Windows Server logo will be able to identify components that will work best with Azure Stack HCI, using an updated set of Additional Qualifiers (AQ’s) that are now being displayed in the Catalog.

More information about the change is available at this blog link, https://aka.ms/RoleBasedNIC

Details

The Windows Server Catalog has some significant changes to the concept and “schema” of the Network Additional Qualifications for Windows Server 2022 (WS2022) network adapters (NICs), visible since the morning of Aug 31.

The change to the Windows Server Catalog was made to increase the “success rate” of Windows Server 2022 and Azure Stack HCI deployments, by ensuring that the NIC(s) used in a deployment are fully qualified for its role.

Now, for Windows Server 2022, the new Additional Qualification (AQ) schema is in place.

NICs can still be “just” Certified, but the majority of the listed network adapters should have at least one AQ. Many will have not just one, but two or even three new AQs for WS2022, as a NIC can have more than one of the new AQs. Example; the Management AQ, one of the Storage AQs, and one of the Compute AQs.

However, a NIC can only have one Storage AQ, either Standard or Premium, and the same for Compute, either Standard or Premium. In both cases, only the highest level AQ Storage or Compute is displayed in the Catalog Product entry page for any specific NIC.

Note: the WS2022 Storage and Compute AQs are “active” on the Server Catalog page left-hand pane in the sense that if either Standard or Premium is selected as a filter [click in the box to the left of the text], the other AQ option is removed from the left-hand pane until the first selection is cleared.

These new AQs are visible in the left-hand menu pane for Windows Server 2022 NICs. As well, the older AQs for SDDC, and the individual Additional Features (AFs) are visible for Windows Server 2019 and earlier submissions. Examples; IPSec support, or VMMQ support.

Here is a description of the Features needed for the Management AQ

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-management.htm.

There are two levels of Storage AQs, with the needed Features described here …

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-storage-standard.htm

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-storage-premium.htm

There are also two levels of Compute AQs, again with descriptive pages

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-compute-standard.htm

https://www.windowsservercatalog.com/content.aspx?ctf=AQinfo-network-adapters-compute-premium.htm

These descriptive pages above can be accessed from the left-hand menu pane main page for NICs, by hovering the mouse over one of these AQs. Click the link in the in the box that then appears to get to the description. Clear the box by clicking the “X” in the upper right-hand corner of the box.

The old Network AQs [e.g., “Data Center Bridging”, or “SDDC Standard”] are still visible in the left-hand menu pane, but only apply to the WS2019 and earlier Windows Server operating system version submissions for any specific NIC. This way, end Customers can still filter using those older AQs and AFs for older OS version submissions. The same will be true for any new submissions made for older OS versions.

Finally, note that for the specific Product entry page, the older AQs for Networking do not appear under the text “Certified for Windows” for the WS2022 section of the entry, only the new AQs.

The older AQs and Additional Features (AFs) will continue to be visible for the WS2019 and earlier sections of the Product entry page.

Similar to the main NIC page, on any specific NIC Product entry page, the WS2022 AQs listed also have the same pop-up and “hover box”, w/ the same functionality. This way, no matter where in the Catalog the end Customer is searching for NICs, they will be able to get to the information about these AQs easily and quickly without hunting around in the FAQ pages.

There is a wide selection of Windows Server-certified NICs qualified for the Management, Storage and Compute AQs.

Supporting end Customers

This change is made to increase the “success rate” that Windows Server 2022 and Azure Stack HCI end Customers have when trying to design or build their own deployments. However, the recommended path for an end Customer is to work with a vendor that can provide a fully Integrated System. See this link, https://azurestackhcisolutions.azure.microsoft.com/#/catalog for more information.

WHCP guidance for Windows 10, version 22H2

Naim_Mohammad — Tue, 02 Aug 2022 16:38:00 GMT

The Windows 10, version 22H2 release will not bring updates to the Windows Hardware Compatibility Program (WHCP) and will follow the same guidelines as Windows 10, version 2004. Below are the more details with respect to all WHCP-related activities:

WHCP requirements – No change. Windows 10, version 2004 requirements remain applicable for Windows 10, version 22H2.
Windows Hardware Lab Kit – No change. Since WHCP requirements will persist in Windows 10, version 22H2, the Windows Hardware Lab Kit (Windows HLK) will also remain the same. There will not be a new Windows HLK release for Windows 10, version 22H2 and partners can continue using Windows 10, version 2004 HLK for certification.
Errata – No change. All Windows 10, version 2004 errata will continue to be valid for Windows 10, version 22H2.
Windows HLK playlist – No change. The Windows HLK version 2004 playlist can be used for Windows 10, version 22H2.
Driver signature – No change. Drivers that meet all the applicable Windows 10, version 2004 requirements will be digitally signed with the same signature attributes.
Submission – No change. Windows 10, version 2004, version 20H2, version 21H1, version 21H2 and version 22H2 can be used for WHCP submission.
WHCP qualification – Windows 10, version 2004
Required OS version – Windows 10, version 22H2
HLK version – HLK version 2004

Windows Hardware Compatibility Program for Windows 11, version 22H2

Naim_Mohammad — Fri, 12 Aug 2022 19:49:24 GMT

The updated version of the Requirements, Windows Hardware Lab Kit (HLK), along with updated playlists for testing Windows 11, version 22H2 hardware can be downloaded from below links. Compared to previous releases of the HLK, this version is intended for exclusive testing for Windows 11, version 22H2. Previous version of the HLK remain available at HLK Kits.

**Please note that Partner Center (Hardware Dev Center) will only start accepting submissions from 5/31/2022 onwards. Partners can download requirements and start hardware validation with updated kit now, but submissions can only be done starting 5/31/2022.

Windows 11, version 22H2 WHCP Requirements

WHCP requirements for Windows 11, version 22H2 can be found here - WHCP Specifications and Policies

Windows 11, version 22H2 certification build

Minimum acceptable build for Windows 11, version 22H2 certification is RTM build(i.e. 22621).

Windows 11, version 22H2 WHCP Playlists & Hardware Lab Kit

Windows Hardware Lab Kit can be found here - Windows Hardware Lab Kit

The table below illustrates the playlists needed for testing each architecture: Link - HLKPlaylist

Testing Target Architecture

Applicable Playlist(s)

x64

HLK Version 22H2 CompatPlaylist x64 ARM64.xml

ARM64*

HLK Version 22H2 CompatPlaylist x64 ARM64.xml

HLK Version 22H2 CompatPlaylist ARM64_x86_on_ARM64.xml

HLK Version 22H2 CompatPlaylist ARM64_x64_on_ARM64.xml

Please refer to the HLK Getting Started Guide for details on HLK client setup and playlist use.

Windows 11, version 22H2 – Submissions on Hardware Dev Center

Partner Center will start accepting submissions for Windows 11, version 22H2 starting 5/31/2022. When making WHCP submissions for the Windows 11, version 22H2 certification, use the following target in Partner Center:

Submission Target

Windows 11 Client x64, version 22H2 Full

Windows 11 Client ARM64, version 22H2 Full

Windows 11, version 22H2 based systems may ship with drivers that have achieved compatibility with Windows 11, version 21H2 until Oct 31st, 2022.
Partners looking to achieve compatibility for systems shipping with Windows 11, version 22H2 Release may use drivers for components that achieved compatibility with Windows 11, Version 21H2 until Oct 31st, 2022.

Errata 103871 is available to filter the “System Logo Check” failure seen when testing Windows 11, version 22H2 based systems with Windows 11, Version 21H2 qualified drivers. To apply, download the Latest Errata Filter Package.

Windows Hardware Compatibility Program guidance for Windows 10, version 21H2

Naim_Mohammad — Thu, 16 Sep 2021 20:24:43 GMT

When Windows 10, version 21H2 is released later this year, there will be no updates to the Windows Hardware Compatibility Program (WHCP). The program will utilize the same guidelines as Windows 10, version 2004, which include the following activities:

WHCP requirements – No change. Windows 10, version 2004 requirements remain applicable for Windows 10, version 21H2.
Windows Hardware Lab Kit (Windows HLK) – No change. Since WHCP requirements persist in Windows 10, version 21H2, the Windows HLK also remains the same. There will not be a new Windows HLK release for Windows 10, version 21H2. Both Windows 10, versions 2004 and 21H2 can be used for the Windows 10, version 2004 qualification.
Errata – No change. All Windows 10, version 2004 waivers will continue to be valid for Windows 10, versions 20H2, 21H1, and 21H2.
Windows HLK playlist – No change. The Windows HLK for Windows 10, version 2004 playlist can be used for Windows 10, versions 2004, 20H2, 21H1, and 21H2.
Driver signature – No change. Drivers that meet all the applicable Windows 10, version 2004 requirements will be digitally signed with the same signature attributes.
Submission – No change. Windows 10, versions 2004, 20H2, 21H1 21H2 can be used for WHCP submission.

WHCP qualification – Windows 10, version 2004
Required OS version – Windows 10, version 2004, version 20H2, version 21H1, and version 21H2
HLK version – Windows HLK for Windows 10, version 2004

For more information on the Windows Hardware Compatibility Program, visit https://aka.ms/WHCP.

Windows Server 2022 Mass Storage SDDC AQ Process - Test and Submission Guidance

Sandy_Arthur — Tue, 31 Aug 2021 21:42:07 GMT

Storage component [storage bus adapters, hard drives, solid state drives, NVMe adapters] vendors must work with their OEM and other partners to determine if the SDDC Premium AQ for Storage for Windows Server 2022 is a need for the partner with regards to the Storage vendor’s product(s).

For the SDDC Premium AQ for Storage for Windows Server 2022, Storage Firmware testing is no longer required for either the storage controller or storage media [hard drive, solid state drive, NVMe device].

All other testing previously mandated for the SDDC Premium AQ for Storage for previous Windows Server versions must still be executed and passed.

For Windows Server 2022, the mass storage devices are unable to be tested for Windows Server 2022 Certification tests as well as the S2D Stress tests for the SDDC (Software Defined Data Center) AQ (Additional Qualification) in a single valid HLK project. The work around is to have two separate HLK projects for each device. One project will contain all the necessary Certification tests, and one will contain all the necessary S2D tests for the SDDC AQ. These projects will then be submitted together, with the S2D Test HLKX results file placed in the supplemental folder (NOT merged) and submitted on Hardware Dev Center for Certification. Once the submission is reviewed and has passing results, it will be displayed in the Windows Server Catalog with the proper Additional Qualifications (AQ).

Please follow these steps:

Create two HLK projects:

“Master Logo” HLK project:

A project will be used for your standard Windows Server certification tests. This is where all the usual HLK feature tests will be run (like PNP, Flush, Server Core, Firmware Update, trim, etc.). You MUST manually add/select the AzureStack/SDDC features in this project, even though these Tests will not be run in this specific project.

All the logo tests (except S2D) must have passing results.

DO NOT RUN the S2D tests in this project. The S2D tests will be shown as “Not Run” (due to selecting the AzureStack feature) in the resulting HLKX package. This is the goal.

“S2D tests” HLK project:

A new project will be created to run the required S2D BVT and stress tests.

Create a new project.
Update the computer pool to contain the nodes of the cluster, and a single standalone server that is not part of the cluster. The nodes of the cluster must contain the disks you are looking to logo as part of the Storage pool (not boot disks). The Gatherer logs will identify the disks that are present in the storage pool to confirm that the S2D tests were run against the proper disk models.
Select ONE disk in ONE node of the cluster as the device under test (DUT).
On the device,

HBAs, such as SAS controllers, can add the Feature "Device.Storage.Controller.AzureStack"
Disks, such as HDD, SSD and NVMe, can add the Feature "Device.Storage.Hd.AzureStack

Apply the latest public playlist. (http://aka.ms/HLKPlaylist) “HLK Version 21H2 CompatPlaylist x64 ARM64 server.xml”
Select the necessary S2D tests (BVT, Stress Tests). The others are optional, but we recommend the Prepare and Setup tests.
Run the tests (fill in the necessary parameters)
All tests must be passing (there will be a bunch that are listed as “Not Run”
Save this project

Project packaging:

You must add a Supplemental Folder and create a README file that states “Please contact the Storage Spaces Direct HLK alias (S2DHLK@microsoft.com) for manual review of the S2D Test results.”

You will now have 2 HLK projects: Master Logo HLK project, and S2D tests HLK project. You will open the Master Logo HLK project and add a supplemental folder that contains the S2D tests HLK project, and the README file. Do not merge the packages as this will result in a package that will be rejected. Sign and save the project for submission.

Submission process:

Go to the Hardware Dev Center and submit the Master Logo HLK project (with the supplemental folders). Provide the Submission ID to the Microsoft team (S2DHLK@microsoft.com) to help move the manual review process along.

The submission will be opened and reviewed to contain all passing results. There will be a few “Not Run” tests, and they must only be the S2D tests that are “Not Run.” The supplemental folder will be opened and the S2D tests HLK project will be opened and reviewed. This project must contain passing results for the S2D BVT and Stress tests. The results will also be opened and the Gatherer logs for STORAGE_BLOCK.XML will be reviewed to confirm that the disks being submitted for logo were part of the S2D cluster node. Every disk that is part of the Master Logo HLK project must be included in the cluster node. If all the disks are not present, then the submission will be failed. If the disks are all present, and have passing results, then the submission will be passed.

Once the submission is reviewed and passed, it will pass on to the Windows Server Catalog and be visible publicly.

For further information and instructions, see these links

Private Cloud Simulator FAQ | Microsoft Docs

Run cluster tests for Storage Spaces Direct (S2D) in the Windows HLK | Microsoft Docs

This second link includes sections on; Prerequisites, Setup, Running the Tests, Troubleshooting, Packaging the results, and Terms

Windows 11 & Server 2022 HLK kit guidance for creating new submission packages for Windows 11, v21H2

Naim_Mohammad — Wed, 21 Jul 2021 17:13:11 GMT

When creating a new project in the Windows 11 & Windows Server 2022 HLK, users will be presented with the option to create a Windows Driver Project ([Is Windows Driver Project] checkbox highlighted in yellow in below image). This option is currently intended for engineering and development purposes, not for creating official submissions. To create a project for proper Windows 11 & Windows Server 2022 certification, please DO NOT check this box. The resulting package generated from a Windows Driver Project will be blocked at the validation stage.

For additional questions/assistance, please reach out to Microsoft support team by creating a support ticket here - Windows developer support

Enforcement of InfVerif Validation Checks

Naim_Mohammad — Tue, 20 Jul 2021 16:03:06 GMT

InfVerif tool validation checks (Error 1217 and 1330-1333) are enforced with the release of Windows 11, version 21H2 after two years relaxation. These validations will be performed on every Driver submissions for the Windows Hardware Compatibility Program (WHCP) made to the Partner Center(Hardware Dev Center). These validation check points were initially introduced in Windows 10, version 1903 (InfVerif validation) but enforcement was relaxed to give partners sometime to prepare for the change. This enforcement will help us ensure the reliability of driver packages and reduce the install failures. Please find additional details on errors below

These checks will be run against all driver submissions and for all OS levels. Driver submissions which exhibit the following errors, will be rejected on Partner Center.

Error 1217:

InfVerif failed for Driver. Partial Log:Error 1217 in xxxxxxxx.inf, line x : Invalid driver version (1.4.1), expecting w.x.y.z, where each segment is between 0-65536.

Error 1330:

InfVerif failed for Driver. Partial Log:Error 1330 in xxxxxxx.inf, line xxxxx: Cannot copy multiple different sources files ('<filename>' and ' <filename> ') to destination file 'C:\Windows\system32\<filename>'.

Error 1331, 1332, and 1333:

These errors are all the same problem but relating to registy values, registry values within services, and services respectively. Methods to resolve these errors are similar to the methods used to resolve Error 1330.

For more information on the errors and what Windows driver developers can do to address them, please review the information at these links:

https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-driverver-directive

https://docs.microsoft.com/en-us/windows-hardware/drivers/devtest/inf-verif-error-1330

Updated Instructions for "Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile"

Sandy_Arthur — Thu, 15 Jul 2021 20:43:50 GMT

Based on feedback, here are new instructions on how to do the "Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile"

Update your HDC Partner Center Profile Information

We are reaching out to those assigned the Admin role for your company's HDC account. Microsoft is currently performing updates to the Hardware Dev Center (HDC). As part of this effort, it is vital that you as Partner Center account Admins update/complete your company’s HDC Profile by July 16, 2021 to keep your account active.

Please ensure that the following information is up to date:

Business name
Address
Contact phone (use your work phone number)
Email (use your work email address)

Even if there are no changes to this information, the HDC Admin role must validate the profile settings in HDC to maintain your program access. Remember that HDC access is needed to submit drivers, devices, and systems for signing or certification.

How to Update your HDC Profile

Verify that you have the permissions to make the change

Click on the dashboard (https://partner.microsoft.com/en-us/dashboard/home)

Click on the “Gear” Icon in the upper right-hand corner of the screen. Then click on “Account Settings”

Click on Settings -> Account settings-> User management to determine if you have the Admin role. Please enter your e-mail address in the Search bar (step #3) to see if you have the ‘Admin’ role assigned to you.

The Admin role gives you the permission to update your profile

Update your profile

Once you have determined that you have the permissions to change the legal profile, follow these steps to update the information

Click on the “Gear” Icon in the upper right-hand corner of the screen. Then click on “Account Settings”.

Click “Organization Profile”, and then click on “Legal”.

On the “Legal info” page, click on the “Developer” tab

Under “Contact info”, ensure that all fields are completed with accurate contact information for the person in your organization that is responsible for your Partner Center registration.

FAQ

Q. I don’t see the ‘Developer’ tab under legal info. What should I do?

If you don’t see the Developer tab under legal info, it means that you have not been given any user role in the Hardware program. This screenshot is an example of a partner who does not see the ‘Partner’ tab.

If you wish to have access to the program, please work with the ‘Admin’ user within your organization to grant you access. If you do not know who the ‘Admin’ user of your organization is, please file a support ticket (details at the bottom of the article).

Q. I see the ‘Developer’ tab under legal info but it tells me that I am not authorized. What should I do?

If you see the Developer tab under legal info but you are not authorized, it means that you do have not the role ‘Admin’ in the Hardware program. The following is an example of a partner who sees a ‘Not Authorized’ error under the Developer tab.

Q. How do I file a support ticket?

You can reach out to Partner Center support to solve your issue. Please visit https://developer.microsoft.com/en-us/windows/support and click on ‘Contact us’

Once done, please file a ticket under this category

In the ticket details, please provide your details in the following screen and the details of the issue you are facing.

Now accepting Windows 11, version 21H2 submissions

Naim_Mohammad — Fri, 13 Aug 2021 17:17:52 GMT

Windows 11, version 21H2 hardware driver submissions for Windows Hardware Compatibility Program (WHCP) are now being accepted at the Partner Center for Windows Hardware. The updated version of the Windows Hardware Lab Kit (HLK), along with updated playlists for testing Windows 11, version 21H2 hardware may be downloaded from Hardware Lab Kit. As with previous releases of the HLK, this version is intended for exclusive testing for Windows 11, version 21H2. Previous version of the HLK remain available at HLK Kits.

Windows 11, version 21H2 WHCP Playlists

The table below illustrates the playlists needed for testing each architecture: Link - HLKPlaylist

Testing Target Architecture

Applicable Playlist(s)

x64

HLK Version 21H2 CompatPlaylist x64 ARM64.xml

ARM64*

HLK Version 21H2 CompatPlaylist x64 ARM64.xml

HLK Version 21H2 CompatPlaylist ARM64_x86_on_ARM64.xml

HLK Version 21H2 CompatPlaylist ARM64_x64_on_ARM64.xml

*Testing for ARM64 requires validation in a separate mode for each playlist. Please refer to the HLK ARM64 Getting Started Guide for details on ARM64 HLK client setup and playlist use.

Windows 11, version 21H2 – Submissions on Hardware Dev Center

When making WHCP submissions for the Windows 11, version 21H2 certification, use the following target in Partner Center:

Submission Target

Windows Hardware Compatibility Program – Client, version 21H2

Windows 11, version 21H2 based systems may ship with drivers that have achieved compatibility with Windows 10, version 2004 until October 22, 2021.
Partners looking to achieve compatibility for systems shipping with Windows 11, version 21H2 Release may factory-install drivers for components that achieved compatibility with Windows 10, version 2004 until October 22, 2021.
Errata 81316 is available to filter the “System Logo Check” failure seen when testing Windows 11, version 21H2 based systems with Windows 10, Version 2004 qualified drivers. To apply, download the latest errata filter package.

Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile

Sandy_Arthur — Wed, 23 Jun 2021 18:38:23 GMT

We are currently performing updates to the Hardware Dev Center (HDC). As part of this effort, it is vital that you update/complete your HDC Profile to keep your account active. To keep your HDC account active, you must update/complete your HDC profile by July 16, 2021. Please ensure that the following information is up to date:

Business name
Address
Contact phone
Email

Even if there are no changes to this information, you must validate the profile settings in HDC to maintain your program access. Remember that HDC access is needed to submit drivers, devices and systems for signing or certification.

To update your HDC Partner Profile:

Log in to the Microsoft Partner Center Dashboard using the AAD Global Admin account (or account with Global Admin AAD Role assigned).

Link to Dashboard (https://partner.microsoft.com/en-us/dashboard/home)

Click on the “Gear” Icon in the upper right-hand corner of the screen.

Then click on “Account Settings”.

Click “Organization Profile”, and then click on “Legal”.

On the “Legal info” page you will see two tabs, Partner and Developer.

Click the “Partner” tab and ensure that the information under “Legal business profile” is complete, and correct. If any fields are blank, or any information needs to be updated.

Click “Developer”.

Under “Contact info”, ensure that all fields are completed with accurate contact information for the person in your organization that is responsible for your Partner Center registration.

If you are unable to update your profile information, please open a ticket with Partner Center support.

Click on the “Support” button. Under “Problem summary” enter “Can’t update partner profile”. Under “Problem type” select “General > Accounts, Onboarding, Access > Company details (legal business profile)”

Thank you for your help in maintaining the Hardware Dev Center! We appreciate your prompt attention to this matter.

Changes to driver signing for Windows 7, Windows Server 2008 R2, and Windows Server 2008

Naim_Mohammad — Thu, 17 Jun 2021 18:51:29 GMT

Effective June 17, 2021, Microsoft partners should utilize the process below to sign drivers for Windows 7, Windows Server 2008, and Windows Server 2008 R2 through the Partner Center for Windows Hardware.

Remove existing signatures from driver binaries.
Generate new catalog files using INF2CAT.
Sign the security catalog files using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Add the driver to your HCK file.
Sign the HCK file using the IHV/OEM certificate registered with the Partner Center for Windows Hardware.
Submit the driver package to the Partner Center for Windows Hardware for signing.
Download the signed driver bundle from the Partner Center for Windows Hardware.

As noted in our post on Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008, Microsoft will discontinue the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2; however, signed drivers will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in an Extended Security Update (ESU) program. Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023.

Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008

Naim_Mohammad — Thu, 17 Jun 2021 18:52:57 GMT

On June 17, 2021, Microsoft will discontinue the publication of drivers to Windows Update for Windows 7 SP1, Windows Server 2008, and Windows Server 2008 R2. If your organization utilizes the Extended Security Updates (ESU) program, you will continue to have the ability to deploy drivers to your managed devices using Windows Server Update Services (WSUS_ and other supported methods.

As previously communicated, the SHA-1 Trusted Root Certificate Authority expired for Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 on May 9, 2021 and is no longer used by Microsoft. Due to the discontinuation and expiration of SHA-1 certificates, partners utilizing the Microsoft Trusted Root Program could publish incompatible SHA-2 signed drivers to unpatched Windows client and Windows Server devices. This, in turn, had the potential to cause degraded functionality or to cause devices to longer boot. This occurs because unpatched systems will have code integrity failures when presented with a SHA-2 signed driver.

To minimize the potential impact of these incompatibilities, Microsoft will discontinue publishing of SHA-2 signed drivers to Windows Update that target Windows 7 SP1, Windows Server 2008, Windows Server 2008 R2 devices on June 17, 2021. While these Windows versions reached the end of support on January 14, 2020, we are making this change to diminish disruptions for users who still remain on these versions of Windows. This includes:

Any driver package submitted for multi-targeting for currently supported versions of Windows and Windows Server
Any driver package targeting versions of Windows or Windows Server that have reached the end of support.

When this change occurs, a notification will be sent to the submitter and they will need to resubmit the shipping label for publishing after they have removed the unsupported versions.

Note: SHA-1 certificates are expired and are already no longer a publishing option for Windows Update.

Continuation of driver signing

Windows 7, Windows Server 2008, and Windows Server 2008 R2 driver submissions for the Windows Hardware Compatibility Program (WHCP) will continue to be available through January 2023. These submissions will continue to be made available to ensure optimal driver reliability for Volume Licensing customers who have elected to participate in the Extended Security Update (ESU) program.

Private Cloud Simulator package for Windows Server 2022

Sandy_Arthur — Tue, 08 Jun 2021 02:22:58 GMT

The Private Cloud Simulator package contains the PCSFiles.VHD to be used for Private Cloud Simulator testing of Network Adapter products for Windows Server 2022 Certification, for Software Defined Data Center (SDDC) Additional Qualification (AQ) testing of selected network adapters, and Azure Stack HCI 21H2 validation testing.

See this link for the PCS Files VHD download, https://download.microsoft.com/download/6/6/f/66ffb8b7-b61b-4a18-9c45-8b80a9ee8b41/PcsFiles.vhd

The package is to be used with the Windows Server 2022 operating system, the Evaluation version of which can be downloaded here https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022-preview

The package is to be used with the Windows Server Hardware Lab Kit (HLK), available https://docs.microsoft.com/en-us/windows-hardware/test/hlk/

Additional package information;

File name and format: Windows HLK WS 2022 Update Package-210527.zip

The package contains dotNet 3.5 for Windows, "microsoft-windows-netfx3-ondemand-package~31bf3856ad364e35~amd64~~.cab" if you do not have access to the Windows Server 2022 install ISO image (which already contains this file)

The package must be applied to an installed and working HLK environment for Windows Server 2022 testing.

The Windows Server 2022 HLK Playlist includes support for the Private Cloud Simulator Tests, also available here https://docs.microsoft.com/en-us/windows-hardware/test/hlk/

Further information and instructions are available at https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/private-cloud-simulator-server-2022

It is recommended to install the latest Windows Server 2022 Update as those become available. The Windows Server Manager tool, or other tools, can be used for this purpose.

Hardware Dev Center Submission Portal is now accepting Windows Server 2022 Submissions

Sandy_Arthur — Wed, 02 Jun 2021 03:08:29 GMT

The product submissions must be tested using the Hardware Lab Kit (HLK) for Windows Server 2022 hardware and software testing. The kit is available at the Partner Center for Windows Hardware, https://docs.microsoft.com/en-us/windows-hardware/test/hlk/.

For information on how to make a submission, see https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard

Vendors may download the Windows Server 2022 Eval version of the operating system for testing purposes here, https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022-preview

Vendors may also download the Virtual Hardware Lab Kit (VHLK) here, https://docs.microsoft.com/en-us/windows-hardware/test/hlk/ . The VHLK is a complete pre-configured HLK test server on a Virtual Hard Disk (VHD). The VHLK VHD can be deployed and booted as a Virtual Machine (VM) with no installation or configuration of the HLK required.

The playlist for testing Windows Server 2022 hardware and software may also be downloaded at that location. For Windows Server 2022, the release playlist has been consolidated for both X64 and ARM64 architecture. The Playlist may be updated in the future, so it is best to check for new versions regularly.

Preview versions of the OS and HLK cannot be used for certification testing of products for Windows Server 2022.

Previous versions of the HLK to be used for testing previous Windows Server versions will continue to be available in accord with the Microsoft Product Lifecycle guidance.

Windows Hardware Compatibility Program testing for Windows Server 2022

Sandy_Arthur — Thu, 27 May 2021 23:33:09 GMT

The Hardware Lab Kit (HLK) for Windows Server 2022 hardware and software testing for Windows Hardware Compatibility Program (WHCP) is now available at the Partner Center for Windows Hardware, https://docs.microsoft.com/en-us/windows-hardware/test/hlk/.

The updated version of the Windows Hardware Lab Kit (HLK), along with updated playlist for testing Windows Server 2022 hardware, may be downloaded at that location. The Playlist may be updated in the future, so it is best to check for new versions regularly.

Vendors may download the Windows Server 2022 Eval version of the operating system for testing purposes here, https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022-preview

Vendors may also download the Virtual Hardware Lab Kit (VHLK) here, https://docs.microsoft.com/en-us/windows-hardware/test/hlk/.

The VHLK is a complete pre-configured HLK test server on a Virtual Hard Disk (VHD). The VHLK VHD can be deployed and booted as a Virtual Machine (VM) with no installation or configuration required.

As with previous releases of the HLK or VHLK, this version is intended for testing for Windows Server 2022. Earlier, or preview, versions of the OS and HLK cannot be used for testing Windows Server 2022. Previous versions of the HLK to be used for testing previous Windows Server versions remain available from the Hardware Dev Center.

Windows Server 2022 WHCP Playlist

For Windows Server 2022, the release playlist has been consolidated for both X64 and ARM64 architecture.

Windows 10, version 21H1 release (WHCP)

Naim_Mohammad — Mon, 01 Aug 2022 19:20:12 GMT

The Windows 10, version 21H1 release will not bring updates to the Windows Hardware Compatibility Program and will follow the same guidelines as 20H2. Below are more details with respect to all WHCP-related activities.

Windows Hardware Compatibility Program (WHCP) activities:

WHCP requirements – No change. Windows 10, version 2004 requirements remain applicable for Windows 10, version 21H1 release.
Hardware Lab kit – No change. Since WHCP requirements will persist in Windows 10, version 21H1, the HLK will also remain the same. There will not be a new HLK release in Windows 10, version 21H1. As both Windows 10, version 2004 and 21H1 OS can be used for Windows 10, version 2004 qualification, they will be recognized as meeting the Windows 10, version 2004 qualification.
Errata – No change. All Windows 10, version 2004 errata will continue to be valid for Windows 10, version 20H2 and version 21H1 release.
HLK playlist – No change. HLK version 2004 playlist can be used for Windows 10, version 2004, version 20H2 and version 21H1 release.
Driver signature – No change. Drivers that meet all the applicable Windows 10, version 2004 requirements will be digitally signed with the same signature attributes.
Submission – Windows 10, version 2004, version 21H2 and version 22H2 OS can be used for WHCP submission.
WHCP qualification – No change, Windows 10, version 2004, version 20H2 and version 21H1 OS can be used for WHCP submission.
Required OS version – Windows 10, version 2004.
HLK version – HLK version 2004

Windows Hardware Certification articles

Windows Hardware Compatibility Program - Guidance for Windows 11, version 24H2 Release

ACTION REQUIRED: New Agreement governing access to Hardware Dev Center

Windows Hardware Compatibility Program Guidance for Windows 11, version 23H2

Details

ACTION REQUIRED: New Agreements governing access to HDC

Windows Server Catalog Changes to Support New Windows Server 2022 Network Additional Qualifications

Summary

Details

Supporting end Customers

WHCP guidance for Windows 10, version 22H2

Windows Hardware Compatibility Program for Windows 11, version 22H2

Windows Hardware Compatibility Program guidance for Windows 10, version 21H2

Windows Server 2022 Mass Storage SDDC AQ Process - Test and Submission Guidance

“Master Logo” HLK project:

“S2D tests” HLK project:

Project packaging:

Submission process:

Windows 11 & Server 2022 HLK kit guidance for creating new submission packages for Windows 11, v21H2

Enforcement of InfVerif Validation Checks

Updated Instructions for "Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile"

Now accepting Windows 11, version 21H2 submissions

Mandatory Check, Update and Validate of Hardware Dev Center (HDC) Profile

To update your HDC Partner Profile:

Changes to driver signing for Windows 7, Windows Server 2008 R2, and Windows Server 2008

Changes to driver publication for Windows 7 SP1, Windows Server 2008 R2, and Windows Server 2008

Continuation of driver signing

We’re here to help

Private Cloud Simulator package for Windows Server 2022

Hardware Dev Center Submission Portal is now accepting Windows Server 2022 Submissions

Windows Hardware Compatibility Program testing for Windows Server 2022

Windows 10, version 21H1 release (WHCP)