none
Driver install fails on Windows 10 when using UpdateDriverForPlugAndPlayDevices RRS feed

  • Question

  • Attempting to install a signed 64 bit driver on windows 10 preview. When installing the driver from the device manager, the install is successful.  When installing the same driver programmatically using UpdateDriverForPlugAndPlayDevices, installation fails.  The same install using UpdateDriverForPlugAndPlayDevices works on Windows 8.1, and all previous versions of windows.  I posted this question on Windows 10 insider forum for Device and Drivers, and the Microsoft support engineer said this is the appropriate forum.


    Here is the log using UpdateDriverForPlugAndPlayDevices, which fails:


    =====================================================================================


    >>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - PCI\VEN_127E&DEV_0070&REV_00]
    >>>  Section start 2015/06/26 11:36:18.154
          cmd: "C:\Users\Cbox\AppData\Local\Temp\Helper.exe" i
         dvi: {Update Device Driver - PCI\VEN_127E&DEV_0070&SUBSYS_01070000&REV_00\4&283D7260&0&00E4}
         dvi:      {Build Driver List} 11:36:18.165
         dvi:           Searching for hardware ID(s):
         dvi:                pci\ven_127e&dev_0070&subsys_01070000&rev_00
         dvi:                pci\ven_127e&dev_0070&subsys_01070000
         dvi:                pci\ven_127e&dev_0070&cc_048000
         dvi:                pci\ven_127e&dev_0070&cc_0480
         dvi:           Searching for compatible ID(s):
         dvi:                pci\ven_127e&dev_0070&rev_00
         dvi:                pci\ven_127e&dev_0070
         dvi:                pci\ven_127e&cc_048000
         dvi:                pci\ven_127e&cc_0480
         dvi:                pci\ven_127e
         dvi:                pci\cc_048000
         dvi:                pci\cc_0480
         sig:           {_VERIFY_FILE_SIGNATURE} 11:36:18.298
         sig:                Key      = wnvavsmultifunction.inf
         sig:                FilePath = c:\users\cbox\appdata\local\temp\wnvavsmultifunction.inf
         sig:                Catalog  = c:\users\cbox\appdata\local\temp\WnvAvsMultiFunction.cat
    !    sig:                Verifying file against specific (valid) catalog failed! (0x800b0109)
    !    sig:                Error 0x800b0109: A certificate chain
    processed, but terminated in a root certificate which is not trusted by
    the trust provider.
         sig:           {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:36:18.320
         sig:           {_VERIFY_FILE_SIGNATURE} 11:36:18.323
         sig:                Key      = wnvavsmultifunction.inf
         sig:                FilePath = c:\users\cbox\appdata\local\temp\wnvavsmultifunction.inf
         sig:                Catalog  = c:\users\cbox\appdata\local\temp\WnvAvsMultiFunction.cat
         sig:                Success: File is signed in Authenticode(tm) catalog.
         sig:                Error 0xe0000242: The publisher of an
    Authenticode(tm) signed catalog has not yet been established as trusted.
         sig:           {_VERIFY_FILE_SIGNATURE exit(0xe0000242)} 11:36:18.351
         dvi:           Created Driver Node:
         dvi:                HardwareID   - PCI\VEN_127E&DEV_0070
         dvi:                InfName      - c:\users\cbox\appdata\local\temp\wnvavsmultifunction.inf
         dvi:                DevDesc      - Winnov Viola
         dvi:                Section      - Winnov.AVX4.AV.NTAMD64
         dvi:                Rank         - 0x00ff2001
         dvi:                Signer Score - Authenticode
         dvi:                DrvDate      - 06/17/2015
         dvi:                Version      - 0
         dvi:      {Build Driver List - exit(0x00000000)} 11:36:18.378
         ndv:      No drivers found for device.
         ndv: {Update Device Driver - exit(00000103)}
    !    ndv: No drivers were found that are better matching drivers for
    device instance
    PCI\VEN_127E&DEV_0070&SUBSYS_01070000&REV_00\4&283D7260&0&00E4
     (Error 0x00000103)
    !    ndv: No devices were updated.
    <<<  Section end 2015/06/26 11:36:18.394
    <<<  [Exit status: FAILURE(0x00000103)]


    =====================================================================================

    I attempted to put the from the device manager (which succeeds) here, but this forum does not accept posts over 60000 characters.  But the post on the Windows 10 form does, so you can look at it here:

    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_devices/driver-install-fails-when-using/8f312591-189f-4704-8e72-009756c255be?tm=1435653968131

    Any suggestions on how to proceed would be appreciated.

    Harry

    Tuesday, June 30, 2015 1:52 PM

All replies

  • Most likely, the driver you are trying to add with UpdateDriverForPlugAndPlayDevices is the same rank or a worse rank than what is currently installed on the device so it does not get installed.  Please see how windows ranks drivers.
    Friday, July 17, 2015 10:05 PM
  • Jason, thanks for the response.  However, this is definitely not the case.

    1) There is no prior driver installed.

    2) The INSTALLFLAG_FORCE is set when invoking UpdateDriverForPlugAndPlayDevices.

    Harry

    Monday, July 20, 2015 6:18 AM
  • Hi Jason,

    Have you found a way to solve this in the meantime? Because we're facing exactly the same problem (working fine on Win 8.1 x64; problems on Win 10 x64)...

    Regards,

    Ele

    Monday, December 14, 2015 2:38 PM
  • The only solution I have found is to get an EV certificate, and sign the driver with the MS Portal.  Then UpdateDriverForPlugAndPlayDevices works.  I still find it odd that exactly the same driver, not signed through the portal, works OK using the Device Manager.

    Harry

    Monday, December 14, 2015 8:03 PM