none
driver signing for Windows 10 IoT Enterprise 2016 LTSB 64bits RRS feed

  • Question

  • Hi 
    We have some questions on driver signing for Windows 10 IoT Enterprise 2016 LTSB 64bit.
    The steps which I found on internet is in below.
    1.Drivers need to be signed by an Extended Validation (EV) Code Signing Certificate 
    2.Submit drivers to Microsoft via the Windows Hardware Developer Center Dashboard portal.
    Is this right?
    May I know the cost and how long will it take for submitting drivers to Microsoft?



    • Edited by PCP_Yen Thursday, March 1, 2018 4:59 AM
    Thursday, March 1, 2018 4:58 AM

All replies

  • For a complete list of steps for submitting drivers for signing please review this:

    https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/hardware-certification-submissions

     

    There is no cost for submitting drivers and the length of time for a driver to process through the signing process can very from ~4hrs to a couple of days depending on the signing method chosen.

     

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

    • Marked as answer by Doron Holan [MSFT] Thursday, March 1, 2018 7:56 PM
    • Unmarked as answer by PCP_Yen Sunday, March 4, 2018 2:47 AM
    Thursday, March 1, 2018 6:33 PM
    Moderator
  • This driver doesn't need "windows update" and "windows logo". 
    We will release it to our customer directly and they will use this driver to do something in their windows application.
    So we only have to sign this driver with "EV Codesigning Certificate" and our customer could use this driver in Windows 10 IoT Enterprise 2016 LTSB 64bits, am I right?
    or we also have to commit the driver to "Windows Hardware Dev Center Dashboard"? 
    Sunday, March 4, 2018 2:47 AM