Skip to main content

 none
Confused-Question about Digital Driver Signing by Microsoft..Need help asap RRS feed

  • Question

  • 1. How much does it cost by Microsoft to sign a driver for Windows 10 (x64 ,x86), Windows 7 (x64, x86), Windows Server 2012, Windows Server 2016 (excluding cost to buy EV certificates)?

    2. How long does the signing process take by Microsoft?

    3. Can you create the HLK and HCK tests from an unsigned driver that is an ".exe" ?

    4. I am trying to generate the HLK and HCK tests but they are failing. Where can I get additional support? I am following the Microsoft tutorial but am wondering if am doing the test right.

    5. I started by Installing the studio (HLK and the HCK on the Server as well as on the client), create machine pool, creating a project, then selecting the machine pool,  In the Selection tab I saw systems, device and printers, device manager, software device then I selected the name of the driver from the device manager and then I ran the test. It ended failing 47 out of 50.

    For example, the "DF InfVerif INT Verification" test failed and the error says: Fail to get primary INF, error 0X00000490

    Thank you very much for your time and consideration.

    Friday, October 19, 2018 6:18 PM

Answers

  • Hello,

    There is a lot of information needed to answer these questions fully, its recommended that the links below be reviewed for the answers to these questions. For the easy ones, there is no cost for Microsoft to sign drivers, the fee was dropped 1/2014. The average time it takes for the signing process I believe is something around 5hrs. 

    Links to useful information:

    https://blogs.msdn.microsoft.com/windows_hardware_certification/2013/12/13/hardware-certification-submission-fees-update/ 

    https://blogs.msdn.microsoft.com/windows_hardware_certification/

    https://docs.microsoft.com/en-us/windows-hardware/design/compatibility/

    https://docs.microsoft.com/en-us/windows-hardware/test/hlk/windows-hardware-lab-kit

    Friday, October 19, 2018 11:55 PM
    Moderator

All replies

  • A driver cannot possibly be .exe.  Is this your own driver, or you're trying to sign someone else's stuff?

    -- pa


    • Edited by Pavel A Friday, October 19, 2018 10:44 PM
    Friday, October 19, 2018 10:43 PM
  • Hello,

    There is a lot of information needed to answer these questions fully, its recommended that the links below be reviewed for the answers to these questions. For the easy ones, there is no cost for Microsoft to sign drivers, the fee was dropped 1/2014. The average time it takes for the signing process I believe is something around 5hrs. 

    Links to useful information:

    https://blogs.msdn.microsoft.com/windows_hardware_certification/2013/12/13/hardware-certification-submission-fees-update/ 

    https://blogs.msdn.microsoft.com/windows_hardware_certification/

    https://docs.microsoft.com/en-us/windows-hardware/design/compatibility/

    https://docs.microsoft.com/en-us/windows-hardware/test/hlk/windows-hardware-lab-kit

    Friday, October 19, 2018 11:55 PM
    Moderator