Hardware Dev Center articles

<?xml version="1.0" encoding="UTF-8"?> <rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0"> <channel> <title>Hardware Dev Center articles</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/bg-p/HardwareDevCenter</link> <description>Hardware Dev Center articles</description> <pubDate>Sat, 23 Nov 2024 17:08:33 GMT</pubDate> <dc:creator>HardwareDevCenter</dc:creator> <dc:date>2024-11-23T17:08:33Z</dc:date> <item> <title>2025 Driver Release Calendar and Block Out Dates</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/2025-driver-release-calendar-and-block-out-dates/ba-p/4292425</link> <description>Exciting news – our 2025 Driver Release Calendar is here! &nbsp; The Driver Shiproom Release Calendar provides a clear view of our release windows for delivering drivers through Windows Update. For a detailed overview of the process, please check visit our <A class="lia-external-url" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/driver-release-cadence" target="_blank">complete overview</A>. &nbsp; <img /></description> <pubDate>Tue, 12 Nov 2024 18:26:19 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/2025-driver-release-calendar-and-block-out-dates/ba-p/4292425</guid> <dc:creator>Asotocama1</dc:creator> <dc:date>2024-11-12T18:26:19Z</dc:date> </item> <item> <title>ACTION REQUIRED: HDC API users may need to update code for accessing submission blobs by Aug 28th</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-hdc-api-users-may-need-to-update-code-for/ba-p/4193041</link> <description>On August 28th, 2024, Hardware Dev Center APIs will change the type of blob urls that are returned in various API calls from service sas urls to user delegated sas urls. Partners using HDC <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fdashboard-api&amp;data=05%7C02%7CCymon.Kilmer%40microsoft.com%7Cb90734d794174bee11f508dca5bc39e4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638567475048153390%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=aLrj7ooG6WI%2B0HImUoNtJbs2%2FKYYDV387uleORVbJYw%3D&amp;reserved=0" target="_blank" rel="noopener">Hardware dashboard API</A> to automate driver submission process may be affected. The specific area affected is the upload and downloads through the <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fget-product-data%23download-object&amp;data=05%7C02%7CCymon.Kilmer%40microsoft.com%7Cb90734d794174bee11f508dca5bc39e4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638567475048167945%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=odeC5HJAvv%2Brd7fcEnWv03GJ1qP8APO8bN%2FJaauDw0Q%3D&amp;reserved=0" target="_blank" rel="noopener">download links</A> in the submission response. All other aspects of the submission process that can be accessed through the API are not affected. Partners are recommended to update to latest version of the libraries they use to upload and download from Azure Blobs during the driver submission process. &nbsp; Partners using C# are encouraged to move to&nbsp;<A href="https://learn.microsoft.com/en-us/dotnet/api/overview/azure/storage.blobs-readme?view=azure-dotnet" target="_self">Azure.Storage.Blobs</A>&nbsp;or <A href="https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.specialized?view=azure-dotnet" target="_self">Azure.Storage.Blobs.Specialized</A> library to ensure that driver submissions are not interrupted. Any partner already managing blob interactions through these libraries is not affected by this change. The following is an example of the <A href="https://learn.microsoft.com/en-us/dotnet/api/azure.storage.blobs.specialized.blockblobclient?view=azure-dotnet" target="_self">BlockBlobClient</A>: &nbsp; <img /> &nbsp; If you experience any issues, please open a support ticket with HDC support. For details about how to contact the support team, visit <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FGetHardwareSupport&amp;data=05%7C02%7CCymon.Kilmer%40microsoft.com%7Cb90734d794174bee11f508dca5bc39e4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638567475048194674%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=E5bMY6ubz77iryEbyKECvaufTrcdQ4EHhe4FtOXFjFs%3D&amp;reserved=0" target="_blank" rel="noopener">https://aka.ms/GetHardwareSupport</A> .</description> <pubDate>Fri, 26 Jul 2024 13:38:16 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-hdc-api-users-may-need-to-update-code-for/ba-p/4193041</guid> <dc:creator>Cymoki</dc:creator> <dc:date>2024-07-26T13:38:16Z</dc:date> </item> <item> <title>ACTION REQUIRED: New Agreement governing access to Hardware Dev Center</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-new-agreement-governing-access-to-hardware-dev/ba-p/4138809</link> <description>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. &nbsp; 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. &nbsp; 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&nbsp;Agreements&nbsp;section of Partner Center as "Microsoft Marks License Agreement (formerly Windows Logo License Agreement)" with the value in the Agreement column of&nbsp;Version 2021. As a result, partners who previously accepted the Windows Logo License Agreement will see two entries in the&nbsp;Agreements&nbsp;section: <OL start="1" type="1"> <LI class="x_x_x_MsoNormal">The new Microsoft Marks License Agreement, with&nbsp;Version 2024.</LI> <LI class="x_x_x_MsoNormal">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&nbsp;Version 2021.</LI> </OL> Going forward, the four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated. ·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A title="Original URL: https://learn.microsoft.com/en-us/legal/windows/hardware/code-signing-agreement-2208. Click or tap if you trust this link." href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Flegal%2Fwindows%2Fhardware%2Fcode-signing-agreement-2208&amp;data=05%7C02%7CNatacha.Roger%40microsoft.com%7C759a08cca25c47e4f1df08dc6f5ba473%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638507686676879915%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=nes405nW3B29gzg77W8Z5dvd4pCE9xU2h92fMnLBNpE%3D&amp;reserved=0" target="_blank" rel="noopener" data-auth="Verified" data-linkindex="2">Code Signing Agreement&nbsp;</A> ·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A title="Original URL: https://learn.microsoft.com/en-us/legal/windows/hardware/windows-hardware-compatibility-program-2208. Click or tap if you trust this link." href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Flegal%2Fwindows%2Fhardware%2Fwindows-hardware-compatibility-program-2208&amp;data=05%7C02%7CNatacha.Roger%40microsoft.com%7C759a08cca25c47e4f1df08dc6f5ba473%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638507686676884410%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=Tqw6xTCYq9V6T1fCRHWkHByI2nHJ5RrPjYMa%2FpV9gzo%3D&amp;reserved=0" target="_blank" rel="noopener" data-auth="Verified" data-linkindex="3">Windows Hardware Compatibility Agreement</A> ·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A title="Original URL: https://learn.microsoft.com/en-us/legal/windows/hardware/microsoft-marks-license-agreement-2024. Click or tap if you trust this link." href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Flegal%2Fwindows%2Fhardware%2Fmicrosoft-marks-license-agreement-2024&amp;data=05%7C02%7CNatacha.Roger%40microsoft.com%7C759a08cca25c47e4f1df08dc6f5ba473%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638507686676888972%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=AlPHj2skaWavuw35RB5PQMOGepiAuNHywKsJ36kfM%2B8%3D&amp;reserved=0" target="_blank" rel="noopener" data-auth="Verified" data-linkindex="4">Microsoft Marks License Agreement 2024 (New)</A> ·&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<A title="Original URL: https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fquery.prod.cms.rt.microsoft.com%2Fcms%2Fapi%2Fam%2Fbinary%2FRE1T4mt&amp;wdOrigin=BROWSELINK. Click or tap if you trust this link." href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fview.officeapps.live.com%2Fop%2Fview.aspx%3Fsrc%3Dhttps%253A%252F%252Fquery.prod.cms.rt.microsoft.com%252Fcms%252Fapi%252Fam%252Fbinary%252FRE1T4mt%26wdOrigin%3DBROWSELINK&amp;data=05%7C02%7CNatacha.Roger%40microsoft.com%7C759a08cca25c47e4f1df08dc6f5ba473%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638507686676893964%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=nkXfni8%2FFJrvPXreuNIIx2Fs3VNmwiaJGE21G6GWcdo%3D&amp;reserved=0" target="_blank" rel="noopener" data-auth="Verified" data-linkindex="5">Windows Analytics Agreement v2.0</A> &nbsp; Please note:&nbsp;Authorized personnel&nbsp;must&nbsp;review and accept the updated agreement on Partner Center. To access the new agreement, sign in to Microsoft Partner Center and select "Agreements" under "Account Settings". &nbsp; If you encounter issues accessing the new agreements, please reach out to our support team. For details on how to contact support, see&nbsp;<A title="Original URL: https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-submission-support. Click or tap if you trust this link." href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Fdashboard%2Fhardware-submission-support&amp;data=05%7C02%7CNatacha.Roger%40microsoft.com%7C759a08cca25c47e4f1df08dc6f5ba473%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638507686676898591%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&amp;sdata=AEX50PLKqj4BLECHmqqK2vQplyQ6ivpimQiek7OVWFI%3D&amp;reserved=0" target="_blank" rel="noopener" data-auth="Verified" data-linkindex="6">Get support for Partner Center dashboard issues - Windows drivers | Microsoft Learn</A>.&nbsp;</description> <pubDate>Wed, 29 May 2024 00:04:51 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-new-agreement-governing-access-to-hardware-dev/ba-p/4138809</guid> <dc:creator>NatachaC</dc:creator> <dc:date>2024-05-29T00:04:51Z</dc:date> </item> <item> <title>InfVerif Error Code 1199</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/infverif-error-code-1199/ba-p/4107493</link> <description>HDC incorporates new capability to verify the usage of unsupported syntax for a particular DDInstall section with InfVerif error code 1199. &nbsp; This error reports the usage of unsupported syntax for a particular DDInstall section to help prevent the driver from installing on product versions where it will not function properly.&nbsp;&nbsp; &nbsp; Compliance with InfVerif error code 1199 is now a requirement for a driver to be certified as Declarative. &nbsp; Details The impacted DDInstall section will install on product versions that do not support the specified syntax. A build number should be added to the Models section to limit applicability of the DDInstall to only supported product versions. &nbsp; To aid with this error, a new infverif output mode has been introduced to the command line infverif.exe available in the WDK. This new mode will help to report syntax used in the INF and what the minimum applicable OS for that syntax is. It can be invoked with: infverif.exe /syntax &lt;filename&gt;.inf&nbsp; &nbsp; Infverif Error Message: The syntax '&lt;value&gt;' was introduced in OS version &lt;MajorVersion&gt;.&lt;MinorVersion&gt;.&lt;BuildNumber&gt; but DDInstall sections utilizing the syntax will install on earlier OS versions. Those DDInstall sections should be restricted to only install on &lt;MajorVersion&gt;.&lt;MinorVersion&gt;.&lt;BuildNumber&gt; or higher using a TargetOSVersion decoration. &nbsp; For additional information, see the following pages:&nbsp; <UL> <LI><A href="https://aka.ms/infverif#1199" target="_blank">https://aka.ms/infverif#1199</A></LI> <LI><A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/install/inf-manufacturer-section" target="_blank">INF Manufacturer Section</A>&nbsp;</LI> <LI><A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/install/combining-platform-extensions-with-operating-system-versions" target="_blank">Combining Platform Extensions with Operating System Versions</A></LI> </UL> &nbsp; &nbsp;</description> <pubDate>Thu, 09 May 2024 19:07:14 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/infverif-error-code-1199/ba-p/4107493</guid> <dc:creator>AndyW</dc:creator> <dc:date>2024-05-09T19:07:14Z</dc:date> </item> <item> <title>Get Verifiable Credentials</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/get-verifiable-credentials/ba-p/4086927</link> <description>A new Account Verification will be required to access Partner Center programs. All participants in the Windows Hardware Program on Partner Center will be required to complete Verifiable Credentials or they will be blocked from accessing the Hardware Program. <A href="https://learn.microsoft.com/en-us/partner-center/get-verifiable-credentials" target="_blank">Verifiable Credentials (VCs)</A> is an open standard for digital credentials. The Primary Contact for your account will be the initial individual required to obtain Verifiable Credentials. We ask that you take action now to confirm the Primary Contact information on your account in Partner Center is accurate and current. Please note the information you provide to obtain Verifiable Credential will be verified by Au10tix Ltd, an industry leader engaged to support this effort. You will not need to disclose the information with Microsoft. To complete your Verifiable Credential, you will need to install the Microsoft Authenticator app on your mobile device and follow the instructions. Microsoft Authenticator will store your Verifiable Credential. You will need a current and valid government ID in the physical form. The name on the government ID must match the Partner Center Primary Contact. For security purposes there are fixed time limits in the steps to obtain Verifiable Credentials. You may need thirty (30) minutes to complete the steps. When you receive the Verifiable Credentials request from Partner Center, we urge you to complete the steps as soon as possible to avoid losing access to the Hardware Program. If you have any questions or issues, please reach out to our support team. For details on how to contact support, see&nbsp;<A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-submission-support" target="_blank">Get support for Partner Center dashboard issues - Windows drivers | Microsoft Learn</A>. Thank you for your cooperation.</description> <pubDate>Fri, 15 Mar 2024 20:00:00 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/get-verifiable-credentials/ba-p/4086927</guid> <dc:creator>NatachaC</dc:creator> <dc:date>2024-03-15T20:00:00Z</dc:date> </item> <item> <title>RESOLVED: HDC Web Dashboard Outage</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/resolved-hdc-web-dashboard-outage/ba-p/4017210</link> <description>Updated 12/29/2023 Thank you for your patience. The issue has been resolved and service restored. &nbsp; *** We are aware of an issue with the hardware dashboard and are working to remediate. As this issue occurred during our scheduled <A title="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/driver-release-cadence" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/driver-release-cadence" target="_blank" rel="noopener">US Winter Holiday timeframe release moratorium</A>, we are targeting restoration of service early in January. In the meantime, the&nbsp;<A title="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/dashboard-api" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/dashboard-api" target="_blank" rel="noopener">API interface</A>&nbsp;should still be available to you. &nbsp; Please check the <A title="https://techcommunity.microsoft.com/t5/hardware-dev-center/bg-p/HardwareDevCenter" href="https://techcommunity.microsoft.com/t5/hardware-dev-center/bg-p/HardwareDevCenter" target="_blank" rel="noopener">Hardware Dev Center Community Hub</A>&nbsp;for updates. &nbsp;</description> <pubDate>Fri, 29 Dec 2023 23:33:37 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/resolved-hdc-web-dashboard-outage/ba-p/4017210</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2023-12-29T23:33:37Z</dc:date> </item> <item> <title>2024 Driver Release Calendar and Block Out Dates</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/2024-driver-release-calendar-and-block-out-dates/ba-p/4004626</link> <description>Here is our Driver Release Calendar for 2024! &nbsp; The Driver Shiproom Release Calendar serves as a predictable way to understand our release windows when delivering drivers through Windows Update. For a full breakdown on the process, please visit our&nbsp;<A title="Driver Shiproom Release Cadence" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/driver-release-cadence" target="_blank" rel="noopener noreferrer">complete overview</A>. &nbsp; <img /> &nbsp;</description> <pubDate>Fri, 08 Dec 2023 20:30:48 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/2024-driver-release-calendar-and-block-out-dates/ba-p/4004626</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2023-12-08T20:30:48Z</dc:date> </item> <item> <title>NX Exception for SHIM Community</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/nx-exception-for-shim-community/ba-p/3976522</link> <description>Due to the complexity of the Linux boot process, the number of active releases from different distributions with compatibility challenges, and the support and serviceability timelines of in-market products, a limited exception to the NX signing requirements has been granted.&nbsp; &nbsp; This limited exception is granted for shims serving in-market products.  This exception will be reviewed regularly, and once component versions are identified that meet the compatibility requirements, new shim signing requests for products targeting the identified components will no longer be exempt. Additionally, when shim functionality is developed to provide compatibility for older, non-compliant boot components, new shim signings will no longer be exempt. &nbsp; &nbsp; Please reach out to:&nbsp;<A class="fui-Link ___10kug0w f3rmtva f1ewtqcl fyind8e f1k6fduh f1w7gpdv fk6fouc fjoy568 figsok6 f1hu3pq6 f11qmguv f19f4twv f1tyq0we f1g0x7ka fhxju0i f1qch9an f1cnd47f fqv5qza f1vmzxwi f1o700av f13mvf36 f1cmlufx f9n3di6 f1ids18y f1tx3yz7 f1deo86v f1eh06m1 f1iescvh fhgqx19 f1olyrje f1p93eir f1nev41a f1h8hb77 f1lqvz6u f10aw75t fsle3fq f17ae5zn" title="mailto:uefisign@microsoft.com" href="mailto:uefisign@microsoft.com" target="_blank" rel="noreferrer noopener" aria-label="Link uefisign@microsoft.com">uefisign@microsoft.com</A>&nbsp;with any questions on this policy.</description> <pubDate>Wed, 08 Nov 2023 19:53:24 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/nx-exception-for-shim-community/ba-p/3976522</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2023-11-08T19:53:24Z</dc:date> </item> <item> <title>Update: Create a New Support Request</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/update-create-a-new-support-request/ba-p/3921311</link> <description>You may have noticed a change when submitting an incident to HDC support team. This <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-submission-support" target="_blank" rel="noopener">Technical Support Issue</A> guidance remains the same. However, the form to submit the incident to HDC support team has changed. &nbsp; &nbsp; Below is a step-by-step guide to help navigate the new form. &nbsp; Step 1: Creating a new ID, with official email address. <OL> <LI>Go to&nbsp;<A href="https://developer.microsoft.com/windows/support/?tabs=Contact-us" target="_blank" rel="noopener">Windows developer support</A>.</LI> <LI>In the&nbsp;Non-Technical Support-Dashboard&nbsp;section, click&nbsp;“Submit an incident’.</LI> </OL> <img /> &nbsp; &nbsp; &nbsp; &nbsp;3. First time users will be directed to the “Welcome to Support for Business” page to create a new ID before they can create a new&nbsp; &nbsp;support request. (Users with an ID will not be required to complete this page. Clicking on “Submit an incident” will take them directly to Step 2 to create the new support request.) &nbsp; &nbsp; &nbsp;4. Click “Save” to save the information and move to the next step. &nbsp; <img /> &nbsp; Step 2: Creating a New Support Request. <OL> <LI>A new page will appear to select the Product Family, Product or Service, and Category.</LI> <LI> Choose the options shown below to submit an incident to HDC support team.&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<img /> &nbsp; </LI> </OL> Step 3: Type of Support, Time Zone, and Contact method. <OL> <LI>Click on "Professional No Charge".</LI> <LI>Choose the Time Zone as per your convenience.</LI> <LI>Select “Email” for the contact method. HDC Support team will only communicate via email and not by phone.</LI> </OL> &nbsp; <img /> &nbsp; Step 4: Issue Description and Details. <OL> <LI>Provide a summary of the issue. For example, write "Driver Submission Failures" if the issue is related to submission failures.</LI> <LI>Answer the questions provided in the template to describe the issue in detail.</LI> <LI>Click on “Attach Files” to attach any relevant information that will help the support team to quickly identify and solve the problem.&nbsp;<img /> &nbsp; </LI> </OL> Step 5: Contact information. <OL> <LI>Click "Add a new Contact" and complete the steps to add additional stakeholders if needed.</LI> <LI>Click “Submit” to submit the incident and open the ticket to HDC support team.</LI> </OL> <img /> &nbsp; Step 6: Confirmation of the Submission. A confirmation email with a support request number will be sent to the contacts confirming receipt of the submission.</description> <pubDate>Thu, 07 Sep 2023 17:25:12 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/update-create-a-new-support-request/ba-p/3921311</guid> <dc:creator>NatachaC</dc:creator> <dc:date>2023-09-07T17:25:12Z</dc:date> </item> <item> <title>Update to Graphics Ecosystem Measures</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/update-to-graphics-ecosystem-measures/ba-p/3813985</link> <description>Driver Servicing leverages <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/measure-attributes" target="_blank" rel="noopener">three types of measures</A> when assessing the quality of a driver; standard, expanded, and ecosystem. Where standard &amp; expanded measures assess drivers that match targeting constraints of the shipping label, ecosystem audiences expand data collection beyond a driver’s targeting constraints to reduce sampling noise and increase the measures’ statistical significance. These measures collect telemetry from any machine that downloaded the driver from any source, including untargeted machines that downloaded an identical version of the driver. A graphics driver is considered identical to another driver when they share the same Driver INF Version. &nbsp; New Measure Dimension Capabilities Historically, our telemetry systems required creating separate ecosystem specific measures when leveraging this audience type. This was displayed most prominently in the graphics category: <img /> As part of recent work overhauling how our driver measures are built, this separation of a single evaluation criteria (ex. Driver Crashes and Hangs in Windows Components &lt;=15.00) into multiple measures for different audience types is no longer required. Moving forward we will begin phasing out our ecosystem specific measures as our standard evaluation measures will automatically fallback to an ecosystem audience when insufficient standard or expanded audience data is available. In this case you’ll see a reference in the rejection messaging indicating that an Ecosystem Audience &nbsp;was used for the evaluation. &nbsp; {[Ecosystem Audience]&nbsp;Measure ID&nbsp;21839288&nbsp;:: "[DDP] UM: Driver Crashes and Hangs in Windows Components" :: 632.34 (VALUE) &lt;= 15.00 (TARGET)&nbsp;::&nbsp;VSO ID: 43939583; PUID: 806773; HOP: 1316.92 (REJECTED)} &nbsp; Graphics Measures Being Deprecation and Updated Navigation For Graphics Support Documentation As part of this work, the following ecosystem measures will no longer being used for evaluation and will be removed from the measure dictionary. <UL> <LI>16507562:&nbsp;[Ecosystem] KM: Devices with Bluescreens in Drivers on Discrete GPUs</LI> <LI>23253402:&nbsp;[Ecosystem] KM: Devices with Bluescreens in Drivers on Integrated GPUs</LI> <LI>20350972:&nbsp;[Ecosystem] KM: Devices with TDRs in Drivers on Discrete GPUs</LI> <LI>24633147:&nbsp;[Ecosystem] KM: Devices with TDRs in Drivers on Integrated GPUs</LI> <LI>25912731:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Communication and Collaboration Applications</LI> <LI>20240835:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Creative Applications</LI> <LI>25389120:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Microsoft Edge (Chromium)</LI> <LI>20240794:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Microsoft Photos</LI> <LI>17377268:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Top Microsoft Applications</LI> <LI>20240811:&nbsp;[Ecosystem] UM: Driver Crashes and Hangs in Windows Components</LI> <LI>26124773:&nbsp;[Ecosystem] Driver Rollbacks or Reinstallations within 2 Days of Installation</LI> <LI>27057557:&nbsp;[Ecosystem] WinML: Devices with Runtime Error (GPU Session Only)</LI> </UL> For the next few months these entries will remain active in the measure dictionary as they are reflected in reports shared previously with driver publishers. These will eventually be phased out in Q3 2023. At that time, we will also be phasing out the separate categories for Standard vs. Ecosystem measures inside our docs.microsoft.com navigation as this additional layer is no longer necessary.</description> <pubDate>Fri, 05 May 2023 21:26:17 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/update-to-graphics-ecosystem-measures/ba-p/3813985</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2023-05-05T21:26:17Z</dc:date> </item> <item> <title>Updated Attestation Signed Driver Publication Requirements - December 2023 Reminder</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/updated-attestation-signed-driver-publication-requirements/ba-p/3754825</link> <description>Attestation signing for Windows device drivers was introduced to allow a fast path for testing critical driver functionality and security fixes. For retail audiences however, our intention has always been that drivers should be signed through the <A title="Windows Hardware Compatibility Program (WHCP)" href="https://learn.microsoft.com/en-us/windows-hardware/design/compatibility/" target="_self">Windows Hardware Compatibility Program (WHCP)</A> release signing process creating a consistent baseline for defining a high-quality driver. Offering attestation signed drivers to non-test audiences contradicts the quality expectations Microsoft holds itself to. &nbsp; Attestation Signed Driver Publishing Update Moving forward, requests for Microsoft to publish attestation signed drivers targeting retail audiences to Windows Update are no longer supported and will be rejected upon submission. This update is specific to publishing and does not change the existing behavior of attestation signed drivers once they are loaded onto a Windows device. &nbsp; Requests to publish attestation signed drivers for testing scenarios on Windows Update are still supported. To submit a publishing request with an attestation signed driver for test scenarios, configure your submission for CoDev or by selecting the restricted audience with the Test Registry Key option. &nbsp; Attestation Signing Plans for Firmware Packages Moving forward, our goal is that all packages submitted through HDC leverage the WHCP process when targeting retail audiences. This statement is also true for firmware submissions, however we recognize there are some considerations with this class of package. To accommodate this need, we are delaying this&nbsp;requirement specific to firmware submissions until 12/1/2023. If you have concerns about this timeline, please reach out to your Microsoft account team.&nbsp; &nbsp; November 2023 Update Thank you for your support in improving the security of our ecosystem through meeting the WHCP requirements. For firmware submissions, please remember that moving into December we will begin enforcing our WHCP attestation signing requirements for all device classes.&nbsp;If you have concerns about this timeline, please reach out to your Microsoft account team.&nbsp; &nbsp; <TABLE width="553px"> <TBODY> <TR> <TD width="217.602px">WU Retail Publication</TD> <TD width="40px">Before Feb 1, 2023&nbsp;</TD> <TD width="152.695px">Before Dec 1, 2023</TD> <TD width="141.703px">After Dec 1, 2023</TD> </TR> <TR> <TD width="217.602px">Attestation signed driver**</TD> <TD width="40px">✓</TD> <TD width="152.695px">X</TD> <TD width="141.703px">X</TD> </TR> <TR> <TD width="217.602px">Attestation signed firmware</TD> <TD width="40px">✓</TD> <TD width="152.695px">✓</TD> <TD width="141.703px">X</TD> </TR> <TR> <TD width="217.602px">HLK signed driver &amp; firmware</TD> <TD width="40px">✓</TD> <TD width="152.695px">✓</TD> <TD width="141.703px">✓</TD> </TR> </TBODY> </TABLE> ** Attestation signing process will remain unchanged, the update above only affect WU publication process. <LI-WRAPPER></LI-WRAPPER> &nbsp; Conclusion While we recognize that this might be disruptive for some who have grown accustomed to leveraging attestation as their signing process, our data shows that most partners are leveraging the WHCP&nbsp;as intended. Moving forward, this will help customers have the best experience possible when updating a driver through Windows Update.</description> <pubDate>Thu, 16 Nov 2023 00:16:05 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/updated-attestation-signed-driver-publication-requirements/ba-p/3754825</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2023-11-16T00:16:05Z</dc:date> </item> <item> <title>ACTION REQUIRED: New Agreements governing access to HDC</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-new-agreements-governing-access-to-hdc/ba-p/3722828</link> <description>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. &nbsp; The four agreements listed below will govern your access to the Hardware Program. Legacy agreements will be deprecated. <UL> <LI><A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flegal%2Fwindows%2Fhardware%2Fcode-signing-agreement-2208&amp;data=05%7C01%7CNatacha.Roger%40microsoft.com%7C292171c0a36346e01c9008dad849d1c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060108939337906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=O8Ni74RWyqbEJmWe8PDqj%2Fl4noCXHJr0aSwmP9zmtQM%3D&amp;reserved=0" target="_blank">Code Signing Agreement&nbsp;(New)</A></LI> <LI><A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Flegal%2Fwindows%2Fhardware%2Fwindows-hardware-compatibility-program-2208&amp;data=05%7C01%7CNatacha.Roger%40microsoft.com%7C292171c0a36346e01c9008dad849d1c4%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638060108939337906%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=E4HYO8HyI6h5NZoJzE%2BlzPGieQaWXvAioG6XYaxdtIs%3D&amp;reserved=0" target="_blank">Windows Hardware Compatibility Agreement (New)</A></LI> <LI><A href="https://learn.microsoft.com/en-us/legal/windows/hardware/windows-logo-license-agreement-fy22" target="_self">Windows Logo License Agreement (LLA) v. 2021</A></LI> <LI><A href="https://view.officeapps.live.com/op/view.aspx?src=https%3A%2F%2Fquery.prod.cms.rt.microsoft.com%2Fcms%2Fapi%2Fam%2Fbinary%2FRE1T4mt&amp;wdOrigin=BROWSELINK" target="_self">Windows Analytics Agreement v2.0</A></LI> </UL> &nbsp; If you encounter issues accessing the new agreements, please reach out to our support team. For details on how to contact support, see&nbsp;<A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-submission-support" target="_blank">Get support for Partner Center dashboard issues - Windows drivers | Microsoft Learn</A>.&nbsp;</description> <pubDate>Wed, 25 Jan 2023 14:00:00 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/action-required-new-agreements-governing-access-to-hdc/ba-p/3722828</guid> <dc:creator>NatachaC</dc:creator> <dc:date>2023-01-25T14:00:00Z</dc:date> </item> <item> <title>New Audio & Graphics Measures</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-audio-amp-graphics-measures/ba-p/3721503</link> <description>To improve our capabilities in evaluating driver quality, the Windows Audio and Graphics Teams have developed new machine measures to improve the evaluation of Windows drivers. &nbsp; New measures The following measures are currently in evaluation for feedback through 2/21/23 and will be operationalized into Driver Shiproom publishing decisions in February of 2023. &nbsp; <TABLE> <TBODY> <TR> <TD width="312"> Evaluation </TD> <TD width="312"> New Measure ID </TD> </TR> <TR> <TD width="312"> <A title="Percentage of devices with SWDRM playback that triggered the Catalog reload event" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-devices-with-swdrm-playback-that-triggered-the-catalog-reload-event" target="_blank" rel="noopener">Percentage of devices with SWDRM playback that triggered the Catalog reload event</A> </TD> <TD width="312"> 41328752 </TD> </TR> <TR> <TD width="312"> <A title="Percent of machines with at least one APO disablement in past 7 days" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-apo-disablement-in-past-7-days" target="_self">Percent of machines with at least one APO disablement in past 7 days</A> </TD> <TD width="312"> 41929221 </TD> </TR> </TBODY> </TABLE> &nbsp;</description> <pubDate>Fri, 20 Jan 2023 20:56:33 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-audio-amp-graphics-measures/ba-p/3721503</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2023-01-20T20:56:33Z</dc:date> </item> <item> <title>Forbidden characters in filenames, and INF encoding</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/forbidden-characters-in-filenames-and-inf-encoding/ba-p/3707744</link> <description>Brief reminder that filenames within your submissions cannot contain any of the following characters:&nbsp;! * ' ( ) ; : @ &amp; = + $ , / ? % # [ ] &nbsp; Additionally, INFs included in your submissions must following the encoding requirements:&nbsp;<A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/display/general-unicode-requirement" target="_blank">General Unicode requirement in INF files - Windows drivers | Microsoft Learn</A></description> <pubDate>Tue, 03 Jan 2023 20:55:54 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/forbidden-characters-in-filenames-and-inf-encoding/ba-p/3707744</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2023-01-03T20:55:54Z</dc:date> </item> <item> <title>New Audio Measures</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-audio-measures/ba-p/3669999</link> <description>To improve our capabilities in evaluating driver quality, the Windows Audio Team has developed several new machine endpoint measures along with updates to the existing system level measures to facilitate the evaluation of audio drivers. &nbsp; Updates to existing measures As our targeting abilities have improved, we have identified several legacy measures that are in the process of being replaced with new measures that will more comprehensively test for the same passing criteria: &nbsp; <TABLE> <TBODY> <TR> <TD width="208"> Evaluation </TD> <TD width="208"> Legacy Measure ID </TD> <TD width="208"> New Measure ID </TD> </TR> <TR> <TD width="208"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-audio-crash" target="_self">Percent of machines with at least one audio crash</A> </TD> <TD width="208"> 23032999 </TD> <TD width="208"> 38373370 </TD> </TR> <TR> <TD width="208"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-audio-hang" target="_self">Percent of machines with at least one audio hang</A> </TD> <TD width="208"> 11458540 </TD> <TD width="208"> 38880837 </TD> </TR> <TR> <TD width="208"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-audio-stream-initialization-failure" target="_blank" rel="noopener">Percent of machines with at least one audio stream initialization failure</A> </TD> <TD width="208"> 12111510 </TD> <TD width="208"> 39415055 </TD> </TR> </TBODY> </TABLE> &nbsp; While these new measures are coming online, the existing legacy measures will continue to be used and reflected in reports shared with driver publishers until they are phased out in Q1 2023. &nbsp; New measures In addition to leveraging system level measures, Microsoft can now evaluate driver quality at the machine endpoint level. The following measures are currently in evaluation for feedback through 12/21/23 and will be operationalized into Driver Shiproom publishing decisions in January of 2023. &nbsp; <TABLE> <TBODY> <TR> <TD width="312"> Evaluation </TD> <TD width="312"> New Measure ID </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-at-least-one-audio-capture-stream-initialization-failure-per-driver" target="_self">Percent of machine endpoints with at least one audio capture stream initialization failure per driver</A> </TD> <TD width="312"> 27593331 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-at-least-one-audio-crash" target="_self">Percent of machine endpoints with at least one audio crash</A> </TD> <TD width="312"> 295682777 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-at-least-one-audio-hang" target="_self">Percent of machine endpoints with at least one audio hang</A> </TD> <TD width="312"> 29745823 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-at-least-one-audio-render-stream-initialization-failure-per-driver" target="_self">Percent of machine endpoints with at least one render stream initialization failure per driver</A> </TD> <TD width="312"> 27539296 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-at-least-one-audio-stream-initialization-failure-per-driver" target="_self">Percent of machine endpoints with at least one audio stream initialization failure per driver</A> </TD> <TD width="312"> 26628516 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machine-endpoints-with-subpar-stream-initialization-success-rate" target="_self">Percent of machine endpoints with subpar stream initialization success rate</A> </TD> <TD width="312"> 27657901 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-audio-capture-stream-initialization-failure" target="_self">Percent of machines with at least one audio capture stream initialization failure</A> </TD> <TD width="312"> 29415321 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-at-least-one-audio-render-stream-initialization-failure" target="_self">Percent of machines with at least one audio render stream initialization failure</A> </TD> <TD width="312"> 39415262 </TD> </TR> <TR> <TD width="312"> <A href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/pct-machines-with-subpar-stream-initialization-success-rate" target="_self">Percent of machines with subpar stream initialization success rate</A> </TD> <TD width="312"> 11458866 </TD> </TR> </TBODY> </TABLE> &nbsp; &nbsp;</description> <pubDate>Tue, 22 Nov 2022 20:23:23 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-audio-measures/ba-p/3669999</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2022-11-22T20:23:23Z</dc:date> </item> <item> <title>2023 Driver Release Calendar and Block Out Dates</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/2023-driver-release-calendar-and-block-out-dates/ba-p/3666854</link> <description>Here is our Driver Release Calendar for 2022! &nbsp; The Driver Shiproom Calendar serves as a predictable way to understand our release windows when delivering drivers through Windows Update. For a full breakdown on the process, please visit our <A title="Driver Shiproom Release Cadence" href="https://learn.microsoft.com/en-us/windows-hardware/drivers/dashboard/driver-release-cadence" target="_blank" rel="noopener">complete overview</A>. &nbsp; <img /> &nbsp; &nbsp;</description> <pubDate>Wed, 02 Nov 2022 22:17:28 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/2023-driver-release-calendar-and-block-out-dates/ba-p/3666854</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2022-11-02T22:17:28Z</dc:date> </item> <item> <title>New Graphics Ecosystem Measure</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-graphics-ecosystem-measure/ba-p/3574389</link> <description>To&nbsp;monitor the overall health &amp; reliability of graphics drivers supporting Software Digital Rights Management (SWDRM), we have developed a new ecosystem measure that provides visibility into the health of graphics drivers when hitting media engine errors. <OL> <LI>Percent of machines using PresentAT that hit one or more media engine errors during video playback on the Netflix app, which supports Software Digital Rights Management (SWDRM). This measure monitors media engine errors that arise for driver versions using Present AT on Netflix app.&nbsp;(<A href="https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/presentat-netflix-app-sdrm-machines-hitting-one-or-more-media-engine-errors" target="_blank" rel="noopener">PresentAt on Netflix app (Software Digital Rights Management) where the % of machines hit one or more media engine errors - Windows drivers | Microsoft Docs</A>)</LI> </OL></description> <pubDate>Fri, 26 Aug 2022 21:00:52 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-graphics-ecosystem-measure/ba-p/3574389</guid> <dc:creator>Garrettd</dc:creator> <dc:date>2022-08-26T21:00:52Z</dc:date> </item> <item> <title>New UEFI CA memory mitigation requirements for signing</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-uefi-ca-memory-mitigation-requirements-for-signing/ba-p/3608714</link> <description>Microsoft, in conjuncture with partners in the PC ecosystem, has developed a set of capabilities and new operating environment conditions for UEFI based systems.&nbsp; This environment will leverage common, architecturally defined mitigations to improve the device security and boot process.&nbsp; For software running in this environment there are new requirements that must be adhered to.&nbsp; For the continuity of our joint customers, it is critical we move the UEFI third-party ecosystem forward together.&nbsp; &nbsp; Starting November 30th, 2022 the memory mitigations described below will be required for all applications to be signed by the Microsoft third-party Unified Extensible Firmware Interface (UEFI) Certificate Authority (CA).&nbsp;&nbsp; &nbsp; Requirements&nbsp; &nbsp; PE-COFF metadata&nbsp;&nbsp; <OL> <LI data-leveltext="%1." data-font="Calibri" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">Section Alignment of the submitted PE file must be aligned with page size.&nbsp; This must be 4kb, or a larger power of 2 (ex 64kb)&nbsp;</LI> <LI data-leveltext="%1." data-font="Calibri" data-listid="2" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">Section Flags must not combine IMAGE_SCN_MEM_WRITE and IMAGE_SCN_MEM_EXECUTE for any given section.&nbsp;</LI> </OL> &nbsp; If-implemented: PE-COFF DLL Attestation&nbsp; <UL> <LI data-leveltext="" data-font="Symbol" data-listid="8" data-list-defn-props="{&quot;335552541&quot;:1,&quot;335559684&quot;:-2,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769226&quot;:&quot;Symbol&quot;,&quot;469769242&quot;:[8226],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">DLL Characteristics must include IMAGE_DLLCHARACTERISTICS_NX_COMPAT&nbsp;</LI> </UL> &nbsp; If a developer is building full support for NX firmware, then they must follow the steps below to fully support and test. Then, since these app characteristics can not be detected statically, setting IMAGE_DLLCHARACTERISTICS_NX_COMPAT attests that the submitted application has successfully implemented and tested the following behavior:&nbsp; <OL> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">The application must not run self-modifying code; meaning that the code sections of the application may not have the write attribute.&nbsp; Any attempt to change values within the memory range will cause an execution fault.&nbsp;&nbsp;</LI> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">If the application attempts to load any internal code into memory for execution, or if it provides support for an external loader, then it must use the EFI_MEMORY_ATTRIBUTE_PROTOCOL appropriately.&nbsp; This optional protocol allows the caller to get, set, and clear the read, write, and execute attributes of a well-defined memory range.&nbsp;&nbsp; <OL class="lia-list-style-type-lower-alpha"> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">Loading internal code into memory must maintain WRITE and EXECUTE exclusivity. It must also change the attributes after loading the code to allow execution.&nbsp;&nbsp;&nbsp;&nbsp;</LI> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">External loaders must support the protocol if available on the system. The loader must not assume newly allocated memory allows code execution (even of code types).&nbsp;&nbsp;&nbsp;</LI> </OL> </LI> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">The application must not assume all memory ranges are valid; specifically, page 0 (PA 0 – 4kb).&nbsp;</LI> <LI data-leveltext="%1." data-font="Calibri" data-listid="3" data-list-defn-props="{&quot;335552541&quot;:0,&quot;335559684&quot;:-1,&quot;335559685&quot;:720,&quot;335559991&quot;:360,&quot;469769242&quot;:[65533,0],&quot;469777803&quot;:&quot;left&quot;,&quot;469777804&quot;:&quot;%1.&quot;,&quot;469777815&quot;:&quot;hybridMultilevel&quot;}" aria-setsize="-1" data-aria-posinset="1" data-aria-level="1">Stack space cannot be used for code execution&nbsp;</LI> </OL> &nbsp; To assist with quickly testing the metadata requirements and setting the DLL characteristic bit, please use this provided <A href="https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_image_validation_tool.md" target="_self">validation tool</A>.&nbsp; The following links and FAQ are here to support the ecosystem and developers with learning about and implementing these new requirements. Thank you to all for continued collaboration. For any questions around signing, please contact <A href="mailto:uefisign@microsoft.com" target="_blank">uefisign@microsoft.com</A>.&nbsp;&nbsp; &nbsp; LINKS:&nbsp; New Reqs doc: <A href="https://docs.microsoft.com/en-us/windows-hardware/drivers/bringup/uefi-ca-memory-mitigation-requirements" target="_self">UEFI CA Memory Mitigation Requirements for Signing - Windows drivers | Microsoft Docs</A>&nbsp; EFI_MEMORY_ATTRIBUTE_PROTOCOL definition: <A href="https://bugzilla.tianocore.org/show_bug.cgi?id=3519" target="_blank">3519 – Add Memory Protection proposal - UEFI_MEMORY_ATTRIBUTE protocol (tianocore.org)</A>&nbsp; Section Alignment: <A href="https://docs.microsoft.com/windows/win32/debug/pe-format%22%20/l%20%22optional-header-windows-specific-fields-image-only%22HYPERLINK%20%22https://docs.microsoft.com/en-us/windows/win32/debug/pe-format%22%20/l%20%22optional-header-windows-specific-fields-image-only" target="_blank">https://docs.microsoft.com/windows/win32/debug/pe-format#optional-header-windows-specific-fields-image-only</A>&nbsp; Section Flags: <A href="https://docs.microsoft.com/windows/win32/debug/pe-format#section-flags" target="_blank">https://docs.microsoft.com/windows/win32/debug/pe-format#section-flags</A>&nbsp; DLL Characteristics: <A href="https://docs.microsoft.com//windows/win32/debug/pe-format#dll-characteristics" target="_blank">https://docs.microsoft.com//windows/win32/debug/pe-format#dll-characteristics</A>&nbsp; Binary test tool documentation: <A href="https://github.com/tianocore/edk2-pytool-extensions/blob/master/docs/usability/using_image_validation_tool.md" target="_blank">edk2-pytool-extensions/using_image_validation_tool.md at master · tianocore/edk2-pytool-extensions (github.com)</A>&nbsp; Binary test tool code: <A href="https://github.com/tianocore/edk2-pytool-extensions/blob/master/edk2toolext/image_validation.py" target="_blank">edk2-pytool-extensions/image_validation.py at master · tianocore/edk2-pytool-extensions (github.com)</A>&nbsp; Open source QEMU based UEFI test environment: <A href="https://github.com/microsoft/mu_tiano_platforms/blob/release/202202/Platforms/QemuQ35Pkg/Docs/Development/building.md" target="_blank">mu_tiano_platforms/building.md at release/202202 · microsoft/mu_tiano_platforms (github.com)</A>&nbsp; &nbsp; FAQ:&nbsp; Q – Does this mean binary images sizes will grow?&nbsp; A – In most cases, no.&nbsp; Most binary files can have different file and section alignment values.&nbsp; For example, the MSVC linker has the /FILEALIGN and /ALIGN flags.&nbsp; File align controls the binary file layout while align controls how the various sections will be aligned in memory once loaded.&nbsp; As mentioned, section alignment is what is critical for these features.&nbsp;&nbsp;&nbsp; &nbsp; <A href="https://docs.microsoft.com/cpp/build/reference/filealign?view=msvc-170%22HYPERLINK%20%22https://docs.microsoft.com/en-us/cpp/build/reference/filealign?view=msvc-170" target="_blank">/FILEALIGN (Align sections in files) | Microsoft Docs</A>&nbsp; <A href="https://docs.microsoft.com/cpp/build/reference/align-section-alignment?view=msvc-170%22HYPERLINK%20%22https://docs.microsoft.com/en-us/cpp/build/reference/align-section-alignment?view=msvc-170" target="_blank">/ALIGN (Section Alignment) | Microsoft Docs</A>&nbsp; &nbsp; Q - Given how long it takes for 3rd party binaries to be deployed and old versions "phased out", how does Microsoft expect OEMs to move forward with these enforcements.  &nbsp; A - It is expected that an OEM will use the presence of the IMAGE_DLLCHARACTERISTICS_NX_COMPAT in 3rd party binaries as a trigger to support compatibility.  When the flag is not set the OEM, if it wants to continue to support the older binary, would restore the memory environment and page attributes.   Our expectation is this compatibility will go away over time as new versions become prevalent in the ecosystem.  This behavior will be required to support all versions of Windows boot prior to 22621.1.  &nbsp;</description> <pubDate>Wed, 24 Aug 2022 20:52:11 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/new-uefi-ca-memory-mitigation-requirements-for-signing/ba-p/3608714</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2022-08-24T20:52:11Z</dc:date> </item> <item> <title>Introducing preproduction signing level</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/introducing-preproduction-signing-level/ba-p/3483336</link> <description>Background Prior to the deprecation of the cross-certificate program (<A href="https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates" target="_blank" rel="noopener">https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates</A>), many partners were leveraging their cross-certificates to sign content for engineering bring up scenarios, and internal testing. While this was convenient, it also presented a risk to our mutual customers. Cross-certificate signatures are trusted by the Windows kernel, and thus signing early in-development drivers with them meant that engineering content, and drivers that had yet to complete security reviews could be weaponized against the Windows userbase. With the end of the cross-certificate program came a gap in testing capabilities when looking at the signing levels offered by HDC. &nbsp; Preproduction driver signing support Microsoft is releasing a new driver signing feature via Hardware Dev Center. The goal is to allow our partners to safely test preproduction content with OS security features like Secure Boot enabled. Leveraging preproduction signed content our partners can perform higher fidelity testing of drivers that are under active development and have not completed the normal security validations. &nbsp; The table below maps out the four driver signing levels available in HDC, and the Windows operating system configurations that support each signing level. &nbsp; <TABLE class=" lia-align-left" style="border-style: solid; width: 743px;" width="742px"> <TBODY> <TR> <TD width="92.0208px" height="84px"> &nbsp; </TD> <TD width="130.167px" height="84px"> Signature Type </TD> <TD width="125.885px" height="84px"> Retail Windows OS </TD> <TD width="120.719px" height="84px">Flight Signed OS&nbsp;+ Secure Boot off&nbsp;</TD> <TD width="136.854px" height="84px"> PreProd Signing Enabled </TD> <TD width="136.688px" height="84px"> Test Signing Enabled </TD> </TR> <TR> <TD rowspan="5" width="92.0208px" height="177px"> Driver Install </TD> <TD width="130.167px" height="30px" style="background-color: #000000; width: 147px;"> &nbsp; </TD> <TD width="125.885px" height="30px" style="background-color: #000000; width: 144px;"> &nbsp; </TD> <TD width="120.719px" height="30px" style="background-color: #000000; width: 144px;"> &nbsp; </TD> <TD width="136.854px" height="30px" style="background-color: #000000; width: 163px;"> &nbsp; </TD> <TD width="136.688px" height="30px" style="background-color: #000000; width: 163px;"> &nbsp; </TD> </TR> <TR> <TD width="130.167px" height="30px"> Test Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> NO </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD width="130.167px" height="30px"> Preprod Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> YES </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD width="130.167px" height="57px"> Attestation Signed </TD> <TD width="125.885px" height="57px"> YES </TD> <TD width="120.719px" height="57px"> NO </TD> <TD width="136.854px" height="57px"> YES </TD> <TD width="136.688px" height="57px"> YES </TD> </TR> <TR> <TD width="130.167px" height="30px"> WHQL Signed </TD> <TD width="125.885px" height="30px"> YES </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> YES </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD rowspan="5" width="92.0208px" height="177px"> Driver Load </TD> <TD width="130.167px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="125.885px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="120.719px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="136.854px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="136.688px" height="30px" style="background-color: #000000;"> &nbsp; </TD> </TR> <TR> <TD width="130.167px" height="30px"> Test Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> YES </TD> <TD width="136.854px" height="30px"> NO </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD width="130.167px" height="30px"> Preprod Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> YES </TD> <TD width="136.854px" height="30px"> YES </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD width="130.167px" height="57px"> Attestation Signed </TD> <TD width="125.885px" height="57px"> YES </TD> <TD width="120.719px" height="57px"> YES </TD> <TD width="136.854px" height="57px"> YES </TD> <TD width="136.688px" height="57px"> YES </TD> </TR> <TR> <TD width="130.167px" height="30px"> WHQL Signed </TD> <TD width="125.885px" height="30px"> YES </TD> <TD width="120.719px" height="30px"> YES </TD> <TD width="136.854px" height="30px"> YES </TD> <TD width="136.688px" height="30px"> YES </TD> </TR> <TR> <TD rowspan="5" width="92.0208px" height="177px"> Driver Load - PE </TD> <TD width="130.167px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="125.885px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="120.719px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="136.854px" height="30px" style="background-color: #000000;"> &nbsp; </TD> <TD width="136.688px" height="30px" style="background-color: #000000;"> &nbsp; </TD> </TR> <TR> <TD width="130.167px" height="30px"> Test Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> NO </TD> <TD width="136.688px" height="30px"> YES SL150 </TD> </TR> <TR> <TD width="130.167px" height="30px"> Preprod Signed </TD> <TD width="125.885px" height="30px"> NO </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> YES SL150 </TD> <TD width="136.688px" height="30px"> YES SL150 </TD> </TR> <TR> <TD width="130.167px" height="57px"> Attestation Signed </TD> <TD width="125.885px" height="57px"> YES SL2000 </TD> <TD width="120.719px" height="57px"> NO </TD> <TD width="136.854px" height="57px"> YES SL2000 </TD> <TD width="136.688px" height="57px"> YES SL2000 </TD> </TR> <TR> <TD width="130.167px" height="30px"> WHQL Signed </TD> <TD width="125.885px" height="30px"> YES SL2000 </TD> <TD width="120.719px" height="30px"> NO </TD> <TD width="136.854px" height="30px"> YES SL2000 </TD> <TD width="136.688px" height="30px"> YES SL2000 </TD> </TR> </TBODY> </TABLE> &nbsp; The table below identifies support for various security features when the OS is configured to trust the different driver signing levels supported by HDC. &nbsp; <TABLE class=" lia-align-left" style="border-style: solid; width: 659px;" width="659"> <TBODY> <TR> <TD width="232.523px" height="57px"> OS Security Feature </TD> <TD width="131.844px" height="57px"> Retail Windows OS </TD> <TD width="143.82px" height="57px"> PreProd Signing Enabled </TD> <TD width="149.812px" height="57px"> Test Signing Enabled </TD> </TR> <TR> <TD width="232.523px" height="57px"> Hypervisor based Code Integrity (HVCI) </TD> <TD width="131.844px" height="57px"> Supported </TD> <TD width="143.82px" height="57px"> Supported&nbsp; </TD> <TD width="149.812px" height="57px"> Supported </TD> </TR> <TR> <TD width="232.523px" height="30px"> Secure Boot </TD> <TD width="131.844px" height="30px"> Supported </TD> <TD width="143.82px" height="30px"> Supported </TD> <TD width="149.812px" height="30px"> Off </TD> </TR> <TR> <TD width="232.523px" height="30px"> Kernel mode Code Integrity </TD> <TD width="131.844px" height="30px"> Supported </TD> <TD width="143.82px" height="30px"> Supported </TD> <TD width="149.812px" height="30px"> Off </TD> </TR> <TR> <TD width="232.523px" height="30px"> User mode Code Integrity </TD> <TD width="131.844px" height="30px"> Supported </TD> <TD width="143.82px" height="30px">Supported</TD> <TD width="149.812px" height="30px"> Off </TD> </TR> </TBODY> </TABLE> &nbsp; The expected behavior of a&nbsp;Flight Signed OS + Secure Boot on will be the&nbsp;same as retail. One would need to follow the same preproduction provisioning steps. as below.&nbsp; &nbsp; The following sections detail the preproduction signing feature in Hardware Dev Center, collateral availability in the Windows Driver Kit (WDK), and a pointer to public documentation for configuring your test machines to trust the preproduction signatures. &nbsp; Hardware Dev Center The preproduction signing feature in Hardware Dev Center is currently only available via our REST API service. Preproduction signed drivers cannot be published to Windows Update, nor can they be shared with a partner via Shipping Label at this time. This is a simple signing only feature. As this feature is intended to sign drivers that are not “retail” ready. We do not scrutinize preproduction submissions with INFverif, or API validator. Your INFs must be properly formed, but we do not require /w, /u, or /k compliance. &nbsp; Input file type Driver submissions must be submitted in a CAB archive. The CAB must be signed with a certificate that has been associated with your Partner Center account. Build your CABs in the same manner you would for an attestation submission. &nbsp; Supported driver signature attributes <UL> <LI>ELAM</LI> <LI>HalExt</LI> <LI>PETrust</LI> <LI>DRM</LI> <LI>WindowsHello</LI> </UL> &nbsp; Symbol submissions Symbol submission and indexing are not supported by the preproduction signing feature. &nbsp; Availability Preproduction signing via HDC is GA &nbsp; Windows Driver Kit The Windows Driver Kit beginning with Windows Insider Preview WDK version 22557 contains the provisioning tools, and collateral needed to properly configure your test hosts running retail versions of Windows to trust this new signature. If you are using EEAP drops of Windows in your testing. Those builds will not require any special configuration to trust the new preproduction signature type. Public documentation is also available here: <A href="https://docs.microsoft.com/en-us/windows-hardware/drivers/install/preproduction-driver-signing-and-install" target="_blank" rel="noopener">https://docs.microsoft.com/en-us/windows-hardware/drivers/install/preproduction-driver-signing-and-install</A> &nbsp;</description> <pubDate>Thu, 30 May 2024 14:00:58 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/introducing-preproduction-signing-level/ba-p/3483336</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2024-05-30T14:00:58Z</dc:date> </item> <item> <title>Hardware Dev Center Submission Portal is now accepting Windows 11, version 22H2 submissions</title> <link>https://techcommunity.microsoft.com/t5/hardware-dev-center/hardware-dev-center-submission-portal-is-now-accepting-windows/ba-p/3452612</link> <description>For information on how to make a submission, see <A href="https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-certification-submissions" target="_blank">Hardware submissions - Windows drivers | Microsoft Docs</A>&nbsp; &nbsp; Windows Hardware Lab Kit can be found here - <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Ftest%2Fhlk%2F&amp;data=05%7C01%7CNaim.Mohammad%40microsoft.com%7Cc1f843e8aae345befcf608da3d945688%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637890004568146211%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=Zi%2Frm8VcCbIvd2adkexEs6oC%2B0CBbHZrUYd%2BORDPwzA%3D&amp;reserved=0" target="_blank">Windows Hardware Lab Kit</A>. Please refer to the <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Ftest%2Fhlk%2Fgetstarted%2Fwindows-hlk-getting-started&amp;data=05%7C01%7CNaim.Mohammad%40microsoft.com%7C3f57416d1c6c474e318408da3de3202d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637890342953886800%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=v7KCkRJ4ThpoEoBVpS%2FeKQ5PzBMuQcES2HmHUfy3%2By0%3D&amp;reserved=0" target="_blank">HLK Getting Started Guide</A> for details on HLK client setup and playlist use.&nbsp; &nbsp; The new versions of the release playlist for submission target x64 and ARM64 architecture are located here, <A href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2FHLKPlaylist&amp;data=05%7C01%7CNaim.Mohammad%40microsoft.com%7Cc1f843e8aae345befcf608da3d945688%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637890004568146211%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=%2BciwL4lFssYUOYoXTWyJa53%2Fi4JZU3WWZLfiDPuBj00%3D&amp;reserved=0" target="_blank">HLKPlaylist</A>.&nbsp;&nbsp;&nbsp;</description> <pubDate>Tue, 31 May 2022 22:46:48 GMT</pubDate> <guid>https://techcommunity.microsoft.com/t5/hardware-dev-center/hardware-dev-center-submission-portal-is-now-accepting-windows/ba-p/3452612</guid> <dc:creator>kevintremblay</dc:creator> <dc:date>2022-05-31T22:46:48Z</dc:date> </item> </channel> </rss>

CINXE.COM

Hardware Dev Center articles