Share via

Best way to create HLK submission for multiple Windows versions

Mark Bewley 71 Reputation points
2025-07-28T13:36:22.9+00:00

For our first driver submission I merged tests against Windows 10 and Windows 11. In the Microsoft signed download was two copies of the signed driver.

I will be submitting a driver update soon. Is this still the expected behaviour, or is there a correct method to submit tests for a single driver against Windows 10 and Window 11 and only get one MS signed driver back? Or, is this still correct I get two differently signed versions.

FYI: I am still testing against Windows 10, as our hardware is using IoT Enterprise LTSC so will still have a mix of Windows 10 and 11 to support for the next 5 years.

We are also not publishing these to Windows Update.

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up upgrades and drivers
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Brian Huynh (WICLOUD CORPORATION) 540 Reputation points Microsoft External Staff Moderator
    2025-08-01T05:45:58.1233333+00:00

    Hello,

    Thank you for reaching out.

    Yes, receiving two separate signed driver packages when you merge tests for Windows 10 and Windows 11 is the expected and correct behavior.

    The attestation signing process generates a unique signature (in the catalog file, .cat) for each major Windows version family you target. Even if your driver binaries are identical, the signing process validates them against the specific policies and test requirements of each OS.

    Since Windows 11 has different and stricter driver requirements than Windows 10, the Partner Center creates a distinct, signed package for each.

    For more information, you can review the official documentation:

    Hope this clarifies the process.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.