process to submit files for signing

Question

Please share the process to submit files for signing (we are submitting driver files)

Answer 1

Hello @Vijay Balan ,

Following up on your request, I have outlined the official process for submitting driver files for signing via the Microsoft Hardware Dev Center / Partner Center dashboard.

The process involves the following key steps:

1. Prepare and Test: Build your driver package (INF, SYS, CAT, etc.) using the Windows Driver Kit (WDK) and successfully pass the required Windows Hardware Lab Kit (HLK) tests.
2. Package HLK Results: Use HLK Studio to package your test results and driver package into an .hlkx file.
3. Create Submission: Sign in to the Partner Center hardware dashboard, select "Submit new hardware", and upload your .hlkx package.
4. Choose Signature Options: Select the requested Windows OS versions and architectures. (You can also select Perform test-signing if this submitted package is only for internal testing).
5. Download Signed Files: Once Microsoft completes the review and signing process, you can download the signed driver package (which includes the security catalog) directly from your dashboard. (Note: If you are opting for the Attestation Signing flow instead of full WHQL, you can skip the HLK testing. You only need to wrap your driver in a .cab file, sign it locally with your company's EV certificate, and upload it to the Partner Center).

For more in-depth instructions, please review the official Microsoft documentation at the following links:

• Managing the Signing Process
• Attestation sign Windows drivers
• Create a new hardware submission

Please let me know if you have any questions or need assistance with any specific step. If you found my response helpful or informative, I would greatly appreciate it if you could follow this guide for your confirmation.

Thank you.

Answer 2

Use the Hardware Dev Center / Partner Center hardware dashboard to submit driver files for signing. At a high level, the process is:

1. Prepare and test the driver package
   • Build a proper driver package (INF, SYS, CAT, and any required binaries) using the WDK.
   • Install the package on a System Under Test (SUT) and run the required Windows Hardware Lab Kit (HLK) tests. For firmware-delivered drivers, ensure the device passes the required HLK tests before submission.
   • If you only need a test-signed driver (for internal testing), you can request test-signing instead of full release signing.
2. (Optional) Test-sign during development
   • During development, create a signed driver package for internal testing. See “Signing Drivers during Development and Test” and “How to test-sign a driver package” referenced from the managing-signing documentation.
3. Package HLK results (for WHQL / release signing)
   • In HLK Studio, package your HLK results into an .hlkx (or .hckx for older WLK) file.
   • For WLK-based submissions, create a .cab file as required.
4. Sign in to Partner Center hardware dashboard
   • Go to the Partner Center hardware dashboard and sign in with your registered Hardware Developer account.
5. Create a new hardware submission (driver signing)
   • Select Submit new hardware.
   • In Packages and signing properties, enter a product name for the driver submission.
   • Upload the .hlkx/.hckx (or .cab for WLK) package that contains your HLK results and driver package.
   • If you want a test-signed driver (not for public release, not via Windows Update), select Perform test-signing. Otherwise leave it unchecked for release signing.
   • Under Request Signatures, choose the OS signatures you need (e.g., specific Windows versions/architectures). Available options depend on the package and tests.
   • Complete any additional questionnaires required for your product type.
   • Finalize and submit.
6. Download the signed driver
   • After Microsoft completes the signing process, download the signed driver package from the hardware dashboard.
   • The signed package includes a security catalog used by Windows to verify integrity.
7. (Attestation / EV-signed CAB scenario)
   • For attestation signing flows, first create a CAB that contains your driver package.
   • Sign the CAB with an EV code-signing certificate using SignTool, for example:

          SignTool sign /s MY /n "Company Name" /fd sha256 \
            /tr http://sha256timestamp.ws.symantec.com/sha256/timestamp \
            /td sha256 /v "C:\Echo\Disk1\Echo.cab"
     

   • Then submit this EV-signed CAB via the Partner Center hardware dashboard under Submit new hardware, choose the requested signatures, and submit.
   • After processing, download the Microsoft-signed driver package.
8. Special cases (firmware, UEFI, LSA, Windows Hello)
   • Firmware packages: Build the firmware driver package, run HLK, then submit to Partner Center for signing. Once signed, optionally publish via Windows Update using the Driver Distribution feature.
   • UEFI firmware or LSA plugins: Use File Signing Services in the hardware dashboard, create a new UEFI/LSA submission, upload a CAB containing the binary, and submit. After processing, download the signed package.
   • Windows Hello biometric drivers: Ensure the INF includes the required [SignatureAttributes] and [SignatureAttributes.WindowsHello] sections so adaptor DLLs receive the Windows Hello signature, then run HLK and submit via DevCenter/Partner Center for review and signing.
9. Manage the signing process internally
   • Decide on the appropriate signature type (test vs. release, WHQL vs. attestation).
   • Obtain the required release or test certificates.
   • Manage digital signature / code-signing keys according to best practices.

This end-to-end flow covers preparing the driver, running HLK, packaging results, submitting via Partner Center, and retrieving the signed driver package.

---

References:

• Managing the Signing Process
• Attestation sign Windows drivers
• Build and submit a firmware package to Windows Update (WU)
• File-sign a Local Security Authority (LSA) plugin or Unified Extensible Firmware Interface (UEFI) firmware binary
• Create a new hardware submission
• Windows Hello: Steps to submit a fingerprint driver
• Submit a Bulk Metadata Package
• Manage product submissions