The Windows Hardware Lab Kit (HLK) has been updated and made available on the download center in order to support the Windows 10, Version 1511 release of the Windows 10 operating system.

• https://msdn.microsoft.com/en-us/windows/hardware/dn913721.aspx#hlk

Build 10586 of the HLK enables compatibility testing of hardware for the Windows 10, Version 1511 release, the 7/29/2015 Windows 10 release, and Windows Server 2016.

There were no changes made to the HLK infrastructure in this release. The sole focus was to provide fixes for tests that created the need for test errata. Over 200 errata were fixed with this release. Errata that were fixed in the September 2015 release are also included in this release, and all remaining errata now have an expiration date of 2/10/2016.

In order to test successfully for Windows 10 compatibility, you will need the latest version of the Windows Hardware Compatibility Program Playlist. The latest playlist is available for download here:

• http://sysdev.microsoft.com/en-US/Hardware/CompatibilityPlaylists

All partners must transition to this kit release and to the 1.8 version of the Compatibility Program Playlist no later than February 10th, 2016.

In order to certify your hardware for previously released operating system versions, you must continue to use the Windows Hardware Certification Kit (HCK) version 2.1. HCK 2.1 must be used to certify hardware for following operating systems:

• Windows 7
• Windows 8
• Windows 8.1
• Windows Server 2008 R2 (x64)
• Windows Server 2012
• Windows Server 2012 R2

This update makes the following changes:

• Added 3 Private Cloud Simulator (optional, system-level) tests to validate cloud-scale reliability for private cloud solutions supporting different types of storage. This test needs ‘PCSfiles.vhd’ (published as HCK supplemental content) for a successful execution experience.
• Removed Touch/PTP certification, allowing devices to function in Windows 8.1 without the THQA blob.

Microsoft is adding new product disclaimer notices for Intel Skylake-based or next generation chip-based customer systems to the Windows Logo License Agreement for Hardware (“LLA”). These disclaimers are required.

Customer Systems that ARE NOT ON the Skylake Support List

OEMs must provide the following notice for any customer system that is NOT included on the Microsoft Skylake Support list with an Intel Skylake or next generation silicon chips based systems shipping with Windows 7, Windows 8, or Windows 8.1. This includes Windows 10 Pro systems downgraded to Windows 7 Professional, Windows 8 Pro, or Windows 8.1:

This version of Windows running with the processor or chipset used in this system does not come with support from Microsoft. For more information about Microsoft’s support, please see Microsoft’s Support Lifecycle FAQ.

Customer Systems that ARE ON the Skylake Support List

OEMs must provide the following notice for any customer system that is included on the Microsoft Skylake Support list with an Intel Skylake or next generation silicon chips based systems shipping with Windows 7, Windows 8, Windows 8.1. This includes Windows 10 Pro systems downgraded to Windows 7 Professional, Windows 8 Pro, Windows 8.1:

This version of Windows running with the processor or chipsets used in this system has limited support from Microsoft. For more information about Microsoft’s support, please see Microsoft’s Support Lifecycle FAQ.

OEMs must provide notice in a clear and conspicuous manner to end users before they acquire the product. For example, OEMs may provide the notice in advertisements, web sites, packaging, and point of purchase materials. At a minimum, the notice must be in the language of the Windows operating system that is pre-installed on the customer system.

OEMs must provide the notice with customer systems in a commercially-reasonable time of this notice or no later than 90 days.

For more information about Microsoft silicon support, see the Clarifications to the lifecycle support policy for Windows communication.

The Windows Hardware Compatibility Program uses an official playlist to determine which devices meet the requirements for compatibility with Windows 10.

The latest playlist can be downloaded here.

This playlist is optional for the next 90 days, after which it will be required, and the previous playlist will no longer be acceptable.

A published playlist can be used for submissions to the Hardware Developer Portal (sysdev) until 90 days after the next playlist update.

We have updated the playlist by removing the following tests:

Starting on February 10, 2016, HLK build 10586 is required in order to satisfy compatibility requirements. This kit enables compatibility testing of hardware for the Windows 10 and Windows Server 2016 operating systems.

In order to successfully test for Windows 10 compatibility, you must have the latest version of the Windows Hardware Compatibility Program Playlist.  The latest playlist is located here:

• http://sysdev.microsoft.com/en-US/Hardware/CompatibilityPlaylists

In order to certify your hardware for previously-released operating system versions, you must continue to use version 2.1 of the Windows Hardware Certification Kit (HCK). HCK 2.1 must be used to certify hardware for following operating systems:

• Windows 7
• Windows 8
• Windows 8.1
• Windows Server 2008 R2 (x64)
• Windows Server 2012
• Windows Server 2012 R2

A year ago we rebooted the WinHEC program. We built the new WinHEC program based off of partner feedback which led us to make a number of changes from the large conference we held from 1992 – 2008. The feedback helped us make the decision to locate the events in Shenzhen and Taipei, move from one major conference a year to more targeted conferences throughout the year, build in more hands-on-labs to help engineers become more familiar and develop skills with Windows tools and processes, and bring in more community opportunities through partner booths & presentations showcasing the exciting work in the Windows community. Momentum continues to build as we are seeing attendance grow while receiving positive feedback through our online properties and surveys we gather at each event.

To ensure this momentum continues, we are hoping to get feedback from our hardware community to help us fine tune the WinHEC program this upcoming year to help us meet the goals of our partners. Most likely the survey will take 10 – 15 minutes to complete, but please feel free to take longer to articulate your requests and recommendations.

Link to WinHEC Survey

Thanks again and your feedback is greatly appreciated,

–The WinHEC Team

Starting in April 2016, the Windows Hardware Lab Kit will include changes to the Static Tools Test for Windows Server 2016. This test is required for Certification of NDIS [Network Driver Interface Specification] and StorPort model drivers, as well as for drivers now designated as “Other” – more information below.

Microsoft’s Static Analysis Tools, namely, Code Analysis for Drivers (CA) and Static Driver Verifier (SDV) have been found to be highly effective in improving driver reliability by identifying coding issues that would be otherwise difficult to find.

The resulting Driver Verification Log (DVL) file output by the Static Analysis tools will be captured by the Hardware Lab Kit for inclusion in the device submission package. Issues discovered by CA and SDV that are determined to be “Server: Must Fix” must be corrected in driver code for Windows Server 2016 submission. Any other issues discovered will be recorded in a Static tools log, but there is no requirement to fix those issues.

More information on “Other” device and driver classification

Some devices and drivers have features and functionality for which Windows has no specific design scenario. The Windows Driver Kit uses the same CA Rules as above and the Kernel Mode Driver Framework Rules in SDV to examine these drivers. The Windows Hardware Lab Kit tests the specific features these devices expose to the operating system. The “Other” classification allows for signing of the drivers and distribution on Windows Update, but the device or driver does not receive a Windows Server 2016 Certification or Logo. See the Windows Hardware Compatibility Program Policies and Processes document, in the “Other” products and conditional WHCP section, for more information about “Other” products.

The Windows Hardware Compatibility Program uses an official playlist to determine which devices meet the requirements for compatibility with Windows 10.

The latest playlist can be downloaded here.

This playlist is optional for the next 90 days, after which it will be required, and the previous playlist will no longer be acceptable.

A published playlist can be used for submissions to the Hardware Developer Portal (sysdev) until 90 days after the next playlist update.

We have updated the playlist by adding the following test:

• Static Tools Logo Test

This playlist release covers updates to Code Analysis for Drivers (CA) and Static Driver Verifier (SDV) rules. For more information, see Changes to the Static Tools Test for Windows Server 2016.

The Windows Hardware Compatibility Program uses an official playlist to determine which devices meet the requirements for compatibility with Windows 10.

The latest playlist can be downloaded here.

This playlist is optional for the next 90 days, after which it will be required, and the previous playlist will no longer be acceptable.

A published playlist can be used for submissions to the Hardware Developer Portal (SysDev) until 90 days after the next playlist update.

We have updated the playlist by removing the following tests:

• Camera Driver Extended Property Handler Base Test Advanced Photo
• Camera Driver Extended Property Handler Base Test Face Detection
• Camera Driver Extended Property Handler Base Test Histogram
• Camera Driver Extended Property Handler Base Test OIS
• Camera Driver Extended Property Handler Base Test VFR
• Camera Driver Extended Property Handler Base Test Video HDR
• Camera Driver Extended Property Handler Base Test Video Stabilization
• Camera Driver Extended Property Handler Base Test Zoom 

The WinHEC team is pleased to invite you to the WinHEC Summer Workshop for hands-on engineering training of tools and services. The workshop will be held in June 2016 at the following times and locations:

WinHEC Summer 2016 Workshop, Taipei: June 28-29, 2016
Hua Nan Bank HNBK International Convention Center
No 123 Songren Road Xinyi District, 2^nd Floor
Taipei City, Taiwan
map

WinHEC Summer 2016, Shenzhen: June 30-July 1, 2016
The Westin Shenzhen Nanshan
9028-2 Shennan Road, Nanshan District, Shenzhen
Guangdong China
map

Next Steps

In order to attend the WinHEC Summer Workshop, please follow the steps below. The registration form will ask questions about basic contact and profile information, and the days and subsequent sessions that you plan to attend.

Registration information

For registration information, please visit our WinHEC registration sites for Shenzhen and Taipei.

For registration questions, please contact us via email.

Please register by June 21, 2016, using one of the links above.

Event Highlights

We look forward to connecting and collaborating with you! Join WinHEC through LINE, WeChat, and Twitter, and please visit our website at http://www.winhec.com. If you have any questions, please contact us at winhec@microsoft.com.

The WinHEC Event team

The new Windows Logo License Agreement for Hardware 2017 and the Windows Logo License Agreement for Software v1.9 are now available for review and signing on the Windows Hardware Developers Dashboard website.

Starting on July 12^th 2016, the Dashboard site will block any attempted submissions for the Windows Hardware Compatibility Program or the Software Logo Program unless the appropriate logo license agreement has been signed.

All Sysdev site services will be offline for approximately 8 hours from 9:30 AM to 5:30 PM PST on 6/21/2016, as we roll out production changes. Please plan accordingly to minimize impact to your releases.

The Windows Hardware Compatibility Program (WHCP) has been the primary channel that we use to communicate to the partner community about our core expectations that Windows places on devices, kernel-affecting software, systems, and solutions. As we transition to a Windows as a Service model, the WHCP must also evolve to accommodate the release cadences. We recognize the importance of feedback from our ecosystem partners and the needs to manage the valuable feedback received. Though LogoFB@microsoft.com has been serving this purpose for the last decade, it’s a challenge to track and categorize each request. Thus, we have decided to make improvements over the existing communication method. Over the next few months, the Microsoft Feedback Management service will replace the LogoFB email alias.

Starting July 15th, 2016, partners who have signed up for the Feedback Management service on the Sysdev Portal can create feedback bugs for the WHCP. The WHCP team will monitor and respond to the feedback bugs quickly. Partners who have a Sysdev portal account but do not yet have Feedback Management access may submit a request for access to Sysdev@microsoft.com. While LogoFB will continue to be operational for the next few months, we encourage partners that need to contact WHCP regularly to transition to the Feedback Management service as soon as possible.

In addition, we would like to take this opportunity to clarify when and whom to contact when a question does arise:

HCK/HLK support: troubleshooting and errata clarification

Open a support case with CSS directly. CSS representatives are on call to provide technical support for the HLK.

Customers who have a Premier Support Contract and are in need of high-priority handling are encouraged to use their designated Microsoft contacts to open support incidents on their behalf.

For customers without a Premier support contract, professional support options, including telephone numbers and pricing information, are available at Microsoft Support.

Sysdev Portal, including operation issues, submission status, driver signing status

Please contact Sysdev@microsoft.com for assistance

WHCP requirements, feedback, and other requests

1. Feedback Management – Filing a feedback bug via Bug management within Sysdev Portal is the preferred method.
   When submitting feedback via Feedback Management, make sure to populate the Partner keywords field with the following text: “LogoFB”
2. LogoFB email – We will continue to monitor the LogoFB account, but our primary focus will be the Feedback Management service.

Last year, we announced that beginning with the release of Windows 10, all new Windows 10 kernel mode drivers must be submitted to the Windows Hardware Developer Center Dashboard portal (Dev Portal) to be digitally signed by Microsoft. However, due to technical and ecosystem readiness issues, this was not enforced by Windows Code Integrity and remained only a policy statement.

Starting with new installations of Windows 10, version 1607, the previously defined driver signing rules will be enforced by the Operating System, and Windows 10, version 1607 will not load any new kernel mode drivers which are not signed by the Dev Portal. OS signing enforcement is only for new OS installations; systems upgraded from an earlier OS to Windows 10, version 1607 will not be affected by this change.

We’re making these changes to help make Windows more secure. These changes limit the risk of an end-user system being compromised by malicious driver software.

If you are a driver developer, here is what you need to do:

1. Ensure that you submit new drivers to Microsoft via the Windows Hardware Developer Center Dashboard portal.
2. Begin the process of getting an Extended Validation (EV) Code Signing Certificate. All drivers submitted to the portal must be signed by an EV certificate.

FAQs

What are the exact exceptions? Are cross-signed drivers still valid?

Enforcement only happens on fresh installations, with Secure Boot on, and only applies to new kernel mode drivers:

• PCs upgrading from a release of Windows prior to Windows 10 Version 1607 will still permit installation of cross-signed drivers.
• PCs with Secure Boot OFF will still permit installation of cross-signed drivers.
• Drivers signed with cross-signing certificate issued prior to July 29th 2015, when the initial policy went into place, will continue to be allowed.
• To prevent systems from failing to boot properly, boot drivers will not be blocked, but they will be removed by the Program Compatibility Assistant. Future versions of Windows will block boot drivers.

To summarize, on non-upgraded fresh installations of Windows 10, version 1607 with Secure Boot ON, drivers must be signed by Microsoft or with cross-signed certificates issued prior to July 29th, 2015.

What about existing drivers? Do I need to re-sign these drivers to get them to work with Windows 10, version 1607?

No. Existing drivers do not need to be re-signed. To ensure backwards compatibility, drivers which are properly signed by a valid cross-signing certificate issued prior to July 29th, 2015 will continue to pass signing checks on Windows 10, version 1607.

What about older versions of Windows?

The changes described in this post apply only to Windows 10, version 1607. Please note that the Windows Hardware Developer Center Dashboard portal will require all new submissions be signed with an EV Code Signing Certificate no matter what OS you plan to support with your driver package.

How do I sign drivers during development and testing?

Please see the Signing Drivers during Development and Test topic on MSDN for information on how to test sign. In addition, if Secure Boot is set to OFF, then drivers signed with existing cross-signed certificates will continue to be valid.

How do I sign a driver so that it is compatible with Windows Vista, Windows 7, Windows 8, Windows 8.1, and Windows 10?

All you need to do is run the HLK tests for Windows 10 and run the HCK tests for Windows 8.1 and earlier versions as you have in the past. Then, using the Windows 10 HLK, merge the two test logs and submit your driver along with the merged HLK/HCK test results to the Windows Hardware Developer Center Dashboard portal. The portal will sign the driver correctly such that it will work on all platforms that you indicate.

What about Extended Validation Certificate Dev Portal package signing?

The portal currently requires all driver submitters to have a valid EV Code Signing Certificate registered to their account. Windows itself does not have any special requirements for drivers to be signed by EV certificates.

Submissions covered by Windows 10, version 1607

The Windows Hardware Lab Kit (HLK) has been updated to support Windows 10, version 1607 and Windows Server 2016.

The HLK is available for download on the Hardware Dev Center:

• https://aka.ms/hlk_dlc

HLK version 1607 enforces the Windows 10 hardware requirements and polices posted at https://aka.ms/compatreq and is designed for testing the following Windows 10 and Windows Server releases:

• Client version 1607
• Client version 1511
• Client version 1507
• Windows Server 2016

New Features in the HLK

This release of the HLK introduces two new features to the infrastructure:

Exporting failed HLK jobs

Failed jobs can now be exported and re-run on a machines that are not connected to an HLK controller, enabling driver developers to easily diagnose and fix issues that cause the HLK test to fail. This feature supports all tests running on Desktop and Server operating systems except for multi-machine or manual tests.

Improved ability to diagnose failed HLK tests

If an HLK test fails due to a system crash on the client under test, there is now an eye-catching indicator (sad smiley face icon) in the Results tab. The information that is displayed will be the Bugcheck summary from the associated Bug Check along with a link to the HLK help file for debugging information. This feature supports tests running only on Desktop and Server operating systems.

Errata fixes and Expiration date

110 errata were fixed and are set to expire on 10/31/2016. Please open a CSS case for any errata that needs further investigation. All other errata have been reviewed and have been set to expire on 7/1/2017.

Playlists to support the incremental Windows releases

As Windows 10 continues to evolve with new features, there is an increasing need to differentiate the incremental versions of Windows 10 within the HLK. HLK version 1607 incorporates OS metadata to aid in determining which Windows 10 version is presently attached and which tests should target the specific version identified. These incremental identification changes are also reflected in the playlist for the HLK version 1607. There will now be two playlists available to support the incremental Windows 10 releases; one playlist is to be used with the HLK version 1511 and the other for HLK version 1607. In order to successfully test for Windows 10 compatibility and Windows Server 2016 certification, you will need the latest available Windows Hardware Compatibility Program Playlist for the correct OS version under test.

Both playlists are available here:

• http://sysdev.microsoft.com/en-US/Hardware/CompatibilityPlaylists

Compatibility Policy for Windows 10, version 1507/Windows 10, version 1511 drivers Factory-Installing on Windows 10, version 1607 image

Per Windows Hardware Compatibility Policy, all partners must transition to HLK version 1607 and use the HLK version 1607 Compatibility playlist no later than October 31, 2016. After this date, logs from HLK version 1511 and corresponding playlist will no longer be accepted for Compatibility submissions.

You must continue to use the Windows Hardware Certification Kit (HCK) version 2.1 to certify hardware for following operating systems:

• Windows 7
• Windows 8
• Windows 8.1
• Windows Server 2008 R2 (x64)
• Windows Server 2012
• Windows Server 2012 R2

For the first 90 days after the release of Windows 10, version 1607, OEMs looking to achieve Compatibility for systems shipping Windows 10, version 1607 may factory-install drivers for components that achieved Compatibility with Windows 10, version 1511. After 90 days, OEMs looking to achieve Compatibility for systems shipping Windows 10, version 1607 can factory-install only drivers for components that achieved Compatibility with Windows 10, version 1607. This is not applicable to OEMs certifying for Windows Server 2016, as all components within the system must be certified for Windows Server 2016 in order to be considered compatible.

Submitting test results for Windows 10, version 1607

As previously mentioned, submissions for Windows 10, version 1607 must be done using HLK version 1607. One important item to remember is that if you are submitting results for Windows 10 version 1607, the results must be packaged for submission using a controller with HLK version 1607 installed. If a controller with HLK version 1511 is used to package and submit results for Windows 10, version 1607, the submission will fail due to the data in the package not being 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 1607 installed can be used to submit results from previous kits (HCK/HLK).

OEM down level system testing for Windows 10

OEMs looking to achieve compatibility for systems shipping Windows 10, version 1511 must continue to use HLK version 1511 to achieve compatibility for Windows 10, version 1511 until the OS version 1607 is required to be factory installed on systems.

In a previous post, Microsoft announced that all driver and system submission packages submitted to the Windows Hardware Developer Center Dashboard Portal must be signed with an Extended Validation (EV) certificate. As part of this announcement, the Windows Hardware Developer Center Dashboard portal was to introduce a per-submission check to validate that every driver and system submission was signed with an EV certificate, and any submission that was not signed with an EV certificate would be declined.

Recent partner feedback has made it clear that the enforcement of this requirement would place an undue burden on current ecosystem business practices. Therefore, the Dashboard portal will not require that every driver and system submission be signed with an individual EV certificate. There will be no per-submission check for an EV certificate signature.

Microsoft is serious about end-user security and takes necessary steps to protect our customers from malicious driver code. The EV certificate requirement was introduced to help ensure the identity and ownership of every submission to the Dashboard portal and to enforce a higher level of accountability and security to protect our customers from potentially-malicious driver code.

Dashboard portal accounts will continue to require partners to authenticate proper identity upon creation of their account by using an EV certificate. Microsoft strongly believes in the value of signing each driver and system submission with an EV certificate and encourages partners to continue signing their driver and system portal submissions using their EV certificate.

As a result of Microsoft having received registered trademark status for the Windows logo, the trademark symbol (™) at the bottom right of the Windows logo on the Genuine Microsoft Label (GML) will be changing to a registered trademark symbol (®). Any GML variants containing the trademark symbol (™) may be used to exhaustion. This change is effective immediately.

In addition, Microsoft has introduced a specific GML for use on Academic products, shown in the image below. Please note that as defined in the LLA, this Logo is part of the GML acquired from a GML Supplier. It may not be used in print or online.

The Windows 10 Logo (shown below) and Windows 10 Pro Logo (for systems with Windows 10) previously had an end-of-use date of October 1, 2016. However, Microsoft is now allowing use of these logos until July 31, 2017.

Finally, Microsoft is discontinuing the dark blue logo option for Windows 8-compatible and Windows 10-compatible logos. Existing labels may be used to exhaustion. No new orders for the dark blue option of the logos should be made.

Version 1607 of the Windows HLK enables you to distribute drivers to specific Windows 10 versions through Windows Update.

When you distribute to a specific version of Windows 10, the Hardware Dev Portal submission must contain HLK results for that version. If distributing to all Windows 10 versions, you must include results for each version as part of the submission. Including HLK results for previous versions ensures that drivers built for the current version also function properly when installed on previous versions of Windows 10.

After successfully submitting a package that contains HLK results for versions 1607 and 1511, you’ll see two options in the Driver Distribution Center:

• Windows 10 (version 1607 and 1511)
• Windows 10 Anniversary Update (version 1607)

The following table shows different distribution scenarios in relation to the 90-day transition timeline after the release of Windows 10, version 1607:

*Windows 10, version 1507 and Windows 10, version 1511 cannot be individually targeted

The image below shows the distribution options when a submission includes test results for both Windows 10 versions. Windows 10 targets versions 1511 and 1507, while Anniversary Update targets version 1607 and above:

Commonly-asked questions are listed below:

If I want to obtain Windows 10, version 1507 compatibility, can I test my driver with version 1607 of the HLK?

• Yes, version 1607 of the HLK can be used to generate test logs that validate Windows 10, versions 1511 & 1507 scenarios.

A previous blog post mentions that version 1607 of the HLK will be required for making submissions after October 31, 2016. After this date, will I still be able to make submissions for Windows 10, version 1511?

• Yes. Version 1607 of the HLK supports validating Windows 10, version 1511, as well as Windows 10, version 1607.

The Windows Hardware Compatibility Program uses an official playlist to determine which tests must be successfully completed for devices and systems to be compatible with Windows 10 and Windows Server 2016. The latest playlist can be downloaded at https://sysdev.microsoft.com/en-US/Hardware/compatibilityplaylists.

This playlist is optional for the next 90 days, after which it will be required by the Hardware Developer Portal, and previous playlists will no longer be accepted. Published playlists can be used for submissions for 90 days after the next playlist update.

Note: This playlist must be used with version 1607 of the Windows HLK.

Jobs removed from the playlist:

• Camera Driver Test –  Video Capture (Record) – Record 30 seconds of 480p Video from Capture pin to H264 file (Video Only)
• Camera Driver Test – Video Capture (Record) – Record 30 seconds of 720p Video from Capture pin to H264 file (Video Only)

New Additional Qualifications for Windows Server 2016

With this playlist, two new Additional Qualifications (AQs) can be earned and are described below. For these AQs, the Windows Server Catalog will display the appropriate designations on devices or systems that pass the associated tests.

1. Firmware Update Capable
   Disk Drives that can update firmware while running without requiring a power cycle.
   SAS, SATA, and NVMe Storage devices may be optionally tested for Firmware Update Capability. If this AQ is sought for SAS devices, you must manually add the If Implemented Device.Storage.Hd.FirmwareUpdate feature to run the corresponding test.
2. Nano Server Capable
   Devices and systems that are verified to run Nano Server, the new very-small footprint installation option for Windows Server 2016.
   Network adapters, Storage adapters, USB components and “Other” (a.k.a. Unclassified) products can be optionally tested running Nano Server. To receive the Nano Server AQ, you must manually add the If Implemented DevFund.Server.Nano feature, which will avoid having unneeded tests scheduled.

This playlist enables these new tests:

• Storage Firmware Update
• Nano Proxy Test – Perform Basic Operation
• Nano Proxy Test – Run ApiScan
• Nano Proxy Test – Validate Inf
• Nano Proxy Test – Verify Remote Server Is Nano
• Nano Proxy Test – Verify Same Device

Note: For Windows Server 2016 certification, Quick Path offerings, Software Defined Data Center (SDDC) Standard or Premium certifications, or Azure Stack certification testing, Microsoft recommends that this playlist be used along with the latest October Update (10D) update (https://support.microsoft.com/en-us/kb/3197954) to Windows Server 2016.

Additional references:

The policies and processes for certification testing, product submission and business requirements can be found at http://go.microsoft.com/fwlink/p/?LinkID=615222.

The HLK requirements can be found at https://msdn.microsoft.com/en-us/windows/hardware/commercialize/design/compatibility/index.

In November 2016, the phased transition from SysDev (sysdev.microsoft.com) to the new Windows Hardware Dev Center began. The initial phase included the transition of HCK/HLK device submissions and has now been completed. The next phase of the transition will include Attestation signing and is detailed below. For further details on the overall transition to the new Windows Hardware Dev Center, please refer to the following Channel 9 article.

Attestation Signing Submissions

Attestation signing will be transitioning to the new Windows Hardware Dev Center in mid-January. Once transitioned, new attestation signing will be required to use the new Windows Hardware Dev Center, and existing attestation submissions will be migrated from the Hardware Dev Center (SysDev) over time.

Key points: 

• New attestation submissions will be blocked on Hardware Dev Center (SysDev) once the transition has occurred
• Existing attestation submissions will be migrated over time, beginning in February
  • Existing submissions will remain fully functional in the Hardware Dev Center (SysDev) until they are migrated
• The packaging format of attested submissions will remain the same as they were in the Hardware Dev Center (SysDev)

Certification Verification Reports

In mid-January, certification verification reports will be made available in the new Windows Hardware Dev Center. Once available, users will be able to download the reports from for any new or migrated submission.