Create a new hardware submission

With the Partner Center hardware dashboard, you can submit your Windows tested drivers for certification. This article describes how to create a new hardware submission in the Partner Center hardware dashboard.

All hardware submissions to the dashboard will be processed within 5 business days or less, depending on whether the submission requires manual review. Manual review may be required if your submission's tests fail, if it doesn't have a valid filter applied, or due to an internal business policy.

Note

In order to make Windows 10 more secure without affecting performance, all binaries are now receiving embedded signatures. This applies to all submissions for certification, not only Windows 10 submissions.

Prerequisites

Submit your new hardware

  1. Go to Partner Center hardware dashboard and sign in using your credentials.

  2. Select Submit new hardware.

    Screenshot of the the list of submitted hardware list.

  3. In the Packages and signing properties section, enter a product name for your driver submission. This name can be used to search for and organize your driver submissions.

    Note

    If you share your driver with another company, they will see this name.

  4. Either drag or browse to the .hlkx/.hckx file that you want to submit. If you're submitting WLK hardware, you must submit a .CAB file. To learn how to create a WLK .cab file submission, see see Create a WLK hardware submission package.

    Screenshot that shows the new hardware submission form.

  5. If you wish to test a driver prior to release, select either Perform test-signing for Win10 and above or Perform test-signing for OS below Win10 (legacy). Test-signed drivers are similar to drivers signed for public release, but don't require HLK testing. They're also not distributed through Windows Update, but can be downloaded from the hardware submission site. They can be installed on test machines only. For more information about test-signing driver packages, see WHQL Test Signature Program and How to test-sign a driver package.

  6. Complete any other any questionnaires that are presented. The portal presents any questionnaire that's required for the product type being submitted for Windows Server certification.

  7. Under Request Signatures, select which operating system signatures (including allowable downlevel operating systems) should be included with your driver. Available certifications vary depending on your driver submission package, so there may not be any certifications listed.

    Note

    If you're signing a driver package for a single architecture, only include logs for the intended architecture. For example, to sign for x64 only, submit only the x64 logs.

    Screenshot that shows possible signatures for a driver submission, and the finalize button.

  8. In the Certification section, complete the following information:

    Field Description
    Device type Indicate if your device is:

    An internal component, if your device is part of a system and connects inside the PC.

    An external component, if your device is an external device (peripheral) that connects to a PC.

    Both, if your device can be connected internally (inside a PC) and externally (peripheral).
    Device metadata category Select an icon for your device from a list of default icons based on your device category. This determines which icon appears in Devices and Printers. If you don't want your device to appear, select "Internal device".

    For information about delivering a rich experience with Windows Device Stage, see Create a Device Metadata Experience.
    Device metadata model ID These GUIDs are used to validate your Device Metadata submissions to the legacy Sysdev dashboard. If provided, they must match the model IDs in your device metadata package.
    Announcement date Enter the date when you want your product included on the Windows Server Catalog, the Windows Certified Product List, and the Universal Driver List.
    Marketing names Enter the marketing name(s) for your submission. Marketing names allow you to provide aliases for your product. You can provide as many names as you want.

    Screenshot that shows the certification section.

    Important

    Make sure to check the announcement date that's been set. Once the announcement date has passed, you won't be able to add a new name.

  9. Select Submit at the bottom of the page.

  10. The Distribution section is used to publish your driver to Windows Update. For information about how to use the Distribution section, see Manage driver distribution with shipping labels.

  11. You can monitor the progress of your submission with the progress tracker at the top of the page. Once all steps show a green check, the submission is complete and your organization will receive a notification in the dashboard header.

    Screenshot that shows the progress tracker.

  12. Review the results. If your submission failed, make any necessary changes and resubmit.

Troubleshoot submission errors

Files missing errors

Your error message is one of the following:

  • There are files at the root of the cabinet.
  • No .inf files found in driver directory/directories: XYZ.

The failure is caused by an incorrect .cab file structure. The .CAB structure was created with driver files in the root folder of the .CAB file instead of having them in a subfolder. For instructions on how to create a proper .CAB file for your driver signing submissions, see Attestation sign Windows 10+ drivers.

Zip64 error

Your error message is:

File is using Zip64(4gb+file Size)

This error is caused when the uploaded archive's filetype is .zip64 instead of .zip. This is caused by a large filesize. To fix this error, repackage the submission using the below steps.

  1. Rename the current .hckx/hlkx file to .zip.
  2. Extract to a folder.
  3. Open the folder.
  4. Select all items, then select and hold (or right-click) and select Send to Compressed zip folder.
  5. Rename the new .zip folder as .hckx/.hlkx.
  6. Upload the new .hckx/.hlkx file.

Failed to open DUA package

Your error message is:

Failed to open package: Not compatible with a version (3.2.0.0) with this instance package manager

Use HLK studio to open the downloaded DUA shell package and to create DUA submission.

Next Steps