none
Attestattion signing kernel driver steps and fees RRS feed

  • Question

  • I got the kernel mode driver for a proprietary USB device working well on Windows 10 (Driver is signed  prior to 2015)

    Now I want to make some changes in INF section of this driver. Signing with my code signinng certificat is no longer supported in Windows 10.

    And I understand, that my steps is as follows:

    1. By EV cert from for example SSL.com

    2. Make Azure AD account (free of charge)

    3. Register in Microsoft Hardware dev center

    4. Make the signed with EV cert CAB file.

    5. Upload file to Dev Center

    6. Wait for a couple of days and receive signed CAB.

    7. profit

    So, am I right?

    The driver submission is free of charge?

    The only fee I have to pay is for EV cert?

    Attestation signing is still avalible?

    Do I need to make tests, to provide test results, to setup some test envinronment?

    Thursday, February 13, 2020 6:20 AM

All replies