Fernando, re ASMedia USB 3.0/3.1 Drivers, Due to problems with the previous asus motherboard, I cannot guarantee my test results in post no 1177. I now have a gigabyte board and will rerun them and re post/update the results in #1177 by the end of next week. Sorry for any inconvinience to you and other users. 
Alright Dieter⌠Iâm having the same issue as several other folks. Windows 10 Pro x64 1703, fresh install on an Asus Z170 motherboard. I installed the Win-RAID CA cert in all the certificate stores that are circled in the attached MMC screenshot below and rebooted the system prior to attempting any driver installs. I hash-checked the old Win-RAID cert I installed several months ago with the one in your latest Intel .zip file, and theyâre exactly the same.
The drivers refuse to install via the Update Driver wizard from the Device Manager. A screenshot of the error message is attached below.
The drivers will install via DPInst64.exe. HOWEVER, if you install them that way, thatâs when the real fun begins. After a reboot, Windows doesnât load and instead goes straight into its Automatic Repair routine. Automatic Repair finds nothing actionable, and essentially what youâre left with is a dead stick of a computer. Windows will not load again until Secure Boot is disabled. After Secure Boot is disabled, Windows loads perfectly fine, and the modded drivers also work perfectly fine, but Secure Boot is essentially busted from that point on until the drivers are removed.
Iâve tried installing the drivers with Secure Boot disabled and nointegritychecks on, but as soon as I re-enable Secure Boot, Windows refuses to load.
setupapi.dev.log outputs the following when attempting to install the XHCI controller driver via the Update Driver Wizard (not DPInst64.exe):
>>> [Device Install (DiShowUpdateDevice) - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0]
>>> Section start 2017/08/26 14:52:09.363
cmd: âC:\Windows\system32\mmc.exeâ C:\Windows\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 14:52:09.363
dvi: Default installer: Enter 14:52:09.363
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 14:52:09.378
ndv: {Update Driver Software Wizard - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: {DIF_SELECTDEVICE} 14:52:19.536
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:19.536
dvi: {DIF_SELECTDEVICE} 14:52:44.654
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:44.654
sto: {Setup Import Driver Package: <REDACTED>\iusb3xhc.inf} 14:52:51.436
inf: Provider: Intel(R) Corporation
inf: Class GUID: {36FC9E60-C465-11CF-8056-444553540000}
inf: Driver Version: 05/11/2017,5.0.4.43
inf: Catalog File: iusb3xhc.cat
sto: {Copy Driver Package: <REDACTED>\iusb3xhc.inf} 14:52:51.452
sto: Driver Package = <REDACTED>\iusb3xhc.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}
sto: Copying driver package files to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}â.
flq: Copying â<REDACTED>\iusb3xhc.catâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.catâ.
flq: Copying â<REDACTED>\iusb3xhc.infâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.infâ.
flq: Copying â<REDACTED>\iusb3xhc.sysâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sysâ.
sto: {Copy Driver Package: exit(0x00000000)} 14:52:51.624
pol: {Driver package policy check} 14:52:51.624
pol: {Driver package policy check - exit(0x00000000)} 14:52:51.624
sto: {Stage Driver Package: C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.624
inf: {Query Configurability: C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.671
inf: Driver package âiusb3xhc.infâ is configurable.
inf: {Query Configurability: exit(0x00000000)} 14:52:51.671
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.catâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.catâ.
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.infâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.infâ.
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sysâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.sysâ.
sto: {DRIVERSTORE IMPORT VALIDATE} 14:52:51.686
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.686
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.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)} 14:52:51.702
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.702
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
sig: Success: File is signed in Authenticode⢠catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode⢠catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:52:51.702
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 14:52:51.702
sig: Signer Score = 0x0F000000
sig: Signer Name = Win-RAID CA
sto: {DRIVERSTORE IMPORT BEGIN} 14:52:51.702
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 14:52:51.702
cpy: {Copy Directory: C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}} 14:52:51.702
cpy: Target Path = C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5
cpy: {Copy Directory: exit(0x00000000)} 14:52:51.718
idb: {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Created driver package object âiusb3xhc.inf_amd64_448d1c959f5d15e5â in SYSTEM database node.
idb: Created driver INF file object âoem15.infâ in SYSTEM database node.
idb: Registered driver package âiusb3xhc.inf_amd64_448d1c959f5d15e5â with âoem15.infâ.
idb: {Register Driver Package: exit(0x00000000)} 14:52:51.718
idb: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Activating driver package âiusb3xhc.inf_amd64_448d1c959f5d15e5â.
cpy: Published âiusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.infâ to âoem15.infâ.
idb: Indexed 40 device IDs for âiusb3xhc.inf_amd64_448d1c959f5d15e5â.
sto: Flushed driver database node âSYSTEMâ. Time = 16 ms
idb: {Publish Driver Package: exit(0x00000000)} 14:52:51.733
sto: {DRIVERSTORE IMPORT END} 14:52:51.733
dvi: Flushed all driver package files to disk. Time = 0 ms
sig: Installed catalog âiusb3xhc.catâ as âoem15.catâ.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 14:52:51.749
sto: {Stage Driver Package: exit(0x00000000)} 14:52:51.749
sto: {Setup Import Driver Package - exit (0x00000000)} 14:52:51.749
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Plug and Play Service: Device Install for PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: Driver INF Path: C:\Windows\INF\oem15.inf
dvi: Driver Node Name: iusb3xhc.inf:f8231471b5248d3d:IUsb3XhcModel:5.0.4.43:pci\ven_8086&dev_a12f&rev_31,
dvi: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Core Device Install} 14:52:51.780
dvi: {Install Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
dvi: {Configure Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
sto: {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf}
sto: Source Filter = pci\ven_8086&dev_a12f&rev_31
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Class Options = Configurable BootCritical
inf: {Configure Driver: Intel(R) USB 3.0 eXtensible Host Controller}
inf: Section Name = IUsb3XhcModel
inf: {Add Service: iusb3xhc}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\iusb3xhc.sys
inf: Display Name = Intel(R) USB 3.0 eXtensible Host Controller Driver
inf: Group = Base
inf: Created new service âiusb3xhcâ.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = PCI\VEN_8086&DEV_A12F&REV_31
inf: {Configure Driver Configuration: IUsb3XhcModel}
inf: Service Name = iusb3xhc
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Copying âC:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.sysâ to âC:\Windows\System32\drivers\iusb3xhc.sysâ.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
dvi: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (oem15.inf:pci\ven_8086&dev_a12f&rev_31,IUsb3XhcModel). 14:52:51.796
dvi: Install Device: Configuring device completed. 14:52:51.796
dvi: {Restarting Devices} 14:52:51.796
dvi: Query-remove: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
dvi: Restart: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
! dvi: Device âPCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0â required reboot: Device has problem: 0x34 (CM_PROB_UNSIGNED_DRIVER), problem status: 0xc0000428.
dvi: {Restarting Devices exit} 14:52:53.594
dvi: {Configure Device - exit(0x00000000)} 14:52:53.594
dvi: {Install Device - exit(0x00000000)} 14:52:53.611
dvi: {Core Device Install - exit(0x00000000)} 14:52:53.611
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Install Related Drivers} 14:52:53.619
ndv: {Install Related Drivers: exit(0x00000000)} 14:52:53.625
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 14:52:53.638
dvi: Default installer: Enter 14:52:53.640
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 14:52:53.643
ndv: {Update Driver Software Wizard exit(00000000)}
<<< Section end 2017/08/26 14:54:46.535
<<< [Exit status: SUCCESS]
>>> Section start 2017/08/26 14:52:09.363
cmd: âC:\Windows\system32\mmc.exeâ C:\Windows\system32\devmgmt.msc
dvi: {DIF_UPDATEDRIVER_UI} 14:52:09.363
dvi: Default installer: Enter 14:52:09.363
dvi: Default installer: Exit
dvi: {DIF_UPDATEDRIVER_UI - exit(0xe000020e)} 14:52:09.378
ndv: {Update Driver Software Wizard - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: {DIF_SELECTDEVICE} 14:52:19.536
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:19.536
dvi: {DIF_SELECTDEVICE} 14:52:44.654
dvi: {DIF_SELECTDEVICE - exit(0xe000020e)} 14:52:44.654
sto: {Setup Import Driver Package: <REDACTED>\iusb3xhc.inf} 14:52:51.436
inf: Provider: Intel(R) Corporation
inf: Class GUID: {36FC9E60-C465-11CF-8056-444553540000}
inf: Driver Version: 05/11/2017,5.0.4.43
inf: Catalog File: iusb3xhc.cat
sto: {Copy Driver Package: <REDACTED>\iusb3xhc.inf} 14:52:51.452
sto: Driver Package = <REDACTED>\iusb3xhc.inf
sto: Flags = 0x00000007
sto: Destination = C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}
sto: Copying driver package files to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}â.
flq: Copying â<REDACTED>\iusb3xhc.catâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.catâ.
flq: Copying â<REDACTED>\iusb3xhc.infâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.infâ.
flq: Copying â<REDACTED>\iusb3xhc.sysâ to âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sysâ.
sto: {Copy Driver Package: exit(0x00000000)} 14:52:51.624
pol: {Driver package policy check} 14:52:51.624
pol: {Driver package policy check - exit(0x00000000)} 14:52:51.624
sto: {Stage Driver Package: C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.624
inf: {Query Configurability: C:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.inf} 14:52:51.671
inf: Driver package âiusb3xhc.infâ is configurable.
inf: {Query Configurability: exit(0x00000000)} 14:52:51.671
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.catâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.catâ.
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.infâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.infâ.
flq: Copying âC:\Users<REDACTED>\AppData\Local\Temp{8e695538-04d8-df47-b359-371c3648b664}\iusb3xhc.sysâ to âC:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.sysâ.
sto: {DRIVERSTORE IMPORT VALIDATE} 14:52:51.686
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.686
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.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)} 14:52:51.702
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.702
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
sig: Success: File is signed in Authenticode⢠catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode⢠catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:52:51.702
sto: {DRIVERSTORE IMPORT VALIDATE: exit(0x00000000)} 14:52:51.702
sig: Signer Score = 0x0F000000
sig: Signer Name = Win-RAID CA
sto: {DRIVERSTORE IMPORT BEGIN} 14:52:51.702
sto: {DRIVERSTORE IMPORT BEGIN: exit(0x00000000)} 14:52:51.702
cpy: {Copy Directory: C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}} 14:52:51.702
cpy: Target Path = C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5
cpy: {Copy Directory: exit(0x00000000)} 14:52:51.718
idb: {Register Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Created driver package object âiusb3xhc.inf_amd64_448d1c959f5d15e5â in SYSTEM database node.
idb: Created driver INF file object âoem15.infâ in SYSTEM database node.
idb: Registered driver package âiusb3xhc.inf_amd64_448d1c959f5d15e5â with âoem15.infâ.
idb: {Register Driver Package: exit(0x00000000)} 14:52:51.718
idb: {Publish Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf} 14:52:51.718
idb: Activating driver package âiusb3xhc.inf_amd64_448d1c959f5d15e5â.
cpy: Published âiusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.infâ to âoem15.infâ.
idb: Indexed 40 device IDs for âiusb3xhc.inf_amd64_448d1c959f5d15e5â.
sto: Flushed driver database node âSYSTEMâ. Time = 16 ms
idb: {Publish Driver Package: exit(0x00000000)} 14:52:51.733
sto: {DRIVERSTORE IMPORT END} 14:52:51.733
dvi: Flushed all driver package files to disk. Time = 0 ms
sig: Installed catalog âiusb3xhc.catâ as âoem15.catâ.
sto: {DRIVERSTORE IMPORT END: exit(0x00000000)} 14:52:51.749
sto: {Stage Driver Package: exit(0x00000000)} 14:52:51.749
sto: {Setup Import Driver Package - exit (0x00000000)} 14:52:51.749
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Plug and Play Service: Device Install for PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0}
dvi: Driver INF Path: C:\Windows\INF\oem15.inf
dvi: Driver Node Name: iusb3xhc.inf:f8231471b5248d3d:IUsb3XhcModel:5.0.4.43:pci\ven_8086&dev_a12f&rev_31,
dvi: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf
dvi: Searching for hardware ID(s):
dvi: pci\ven_8086&dev_a12f&subsys_86941043&rev_31
dvi: pci\ven_8086&dev_a12f&subsys_86941043
dvi: pci\ven_8086&dev_a12f&cc_0c0330
dvi: pci\ven_8086&dev_a12f&cc_0c03
dvi: Searching for compatible ID(s):
dvi: pci\ven_8086&dev_a12f&rev_31
dvi: pci\ven_8086&dev_a12f
dvi: pci\ven_8086&cc_0c0330
dvi: pci\ven_8086&cc_0c03
dvi: pci\ven_8086
dvi: pci\cc_0c0330
dvi: pci\cc_0c03
dvi: Class GUID of device changed to: {36fc9e60-c465-11cf-8056-444553540000}.
dvi: {Core Device Install} 14:52:51.780
dvi: {Install Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
dvi: {Configure Device - PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0} 14:52:51.780
dvi: Parent device: ACPI\PNP0A08\0
sto: {Configure Driver Package: C:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.inf}
sto: Source Filter = pci\ven_8086&dev_a12f&rev_31
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Class Options = Configurable BootCritical
inf: {Configure Driver: Intel(R) USB 3.0 eXtensible Host Controller}
inf: Section Name = IUsb3XhcModel
inf: {Add Service: iusb3xhc}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\iusb3xhc.sys
inf: Display Name = Intel(R) USB 3.0 eXtensible Host Controller Driver
inf: Group = Base
inf: Created new service âiusb3xhcâ.
inf: {Add Service: exit(0x00000000)}
inf: Hardware Id = PCI\VEN_8086&DEV_A12F&REV_31
inf: {Configure Driver Configuration: IUsb3XhcModel}
inf: Service Name = iusb3xhc
inf: Config Flags = 0x00000000
inf: {Configure Driver Configuration: exit(0x00000000)}
inf: {Configure Driver: exit(0x00000000)}
flq: Copying âC:\Windows\System32\DriverStore\FileRepository\iusb3xhc.inf_amd64_448d1c959f5d15e5\iusb3xhc.sysâ to âC:\Windows\System32\drivers\iusb3xhc.sysâ.
dvi: Existing files modified, may need to restart related services.
sto: {Configure Driver Package: exit(0x00000bc3)}
dvi: Restart required for any devices using this driver.
dvi: Install Device: Configuring device (oem15.inf:pci\ven_8086&dev_a12f&rev_31,IUsb3XhcModel). 14:52:51.796
dvi: Install Device: Configuring device completed. 14:52:51.796
dvi: {Restarting Devices} 14:52:51.796
dvi: Query-remove: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
dvi: Restart: PCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0
! dvi: Device âPCI\VEN_8086&DEV_A12F&SUBSYS_86941043&REV_31\3&11583659&0&A0â required reboot: Device has problem: 0x34 (CM_PROB_UNSIGNED_DRIVER), problem status: 0xc0000428.
dvi: {Restarting Devices exit} 14:52:53.594
dvi: {Configure Device - exit(0x00000000)} 14:52:53.594
dvi: {Install Device - exit(0x00000000)} 14:52:53.611
dvi: {Core Device Install - exit(0x00000000)} 14:52:53.611
ump: {Plug and Play Service: Device Install exit(00000000)}
ndv: {Install Related Drivers} 14:52:53.619
ndv: {Install Related Drivers: exit(0x00000000)} 14:52:53.625
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL} 14:52:53.638
dvi: Default installer: Enter 14:52:53.640
dvi: Default installer: Exit
dvi: {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)} 14:52:53.643
ndv: {Update Driver Software Wizard exit(00000000)}
<<< Section end 2017/08/26 14:54:46.535
<<< [Exit status: SUCCESS]
The juiciest part of which appears to be this:
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.686
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.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)} 14:52:51.702
sig: {_VERIFY_FILE_SIGNATURE} 14:52:51.702
sig: Key = iusb3xhc.inf
sig: FilePath = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.inf
sig: Catalog = C:\Windows\System32\DriverStore\Temp{a3e215e8-8dbc-384b-8aec-13e175d46275}\iusb3xhc.cat
sig: Success: File is signed in Authenticode⢠catalog.
sig: Error 0xe0000241: The INF was signed with an Authenticode⢠catalog from a trusted publisher.
sig: {_VERIFY_FILE_SIGNATURE exit(0xe0000241)} 14:52:51.702
There is no certification âpathâ for the certificate you used to sign these drivers, so Iâm not sure why itâs saying this. I tried adding the three timestamping countersignatures from Thawte and Symantec to the necessary stores just for fun, but this had no effect.
Whatâs very interesting, though, is that I CAN install version 5.0.1.38 of your modded drivers without any issues, whatsoever. Iâll try installing some newer ones that precede 5.0.4.43 and see where the problem lies exactly.
I believe that either something has changed with 1703 as it pertains to Secure Boot and/or driver signing, or thereâs something going on with the drivers themselves past a certain version. Are you open to such possibilities? Did you upgrade to 1703, or do a fresh install like the folks (myself included) who are having this issue?
I know youâve stated multiple times now that youâre able to install the drivers fine on 1703, but there also multiple, dissociated reports of people who cannot, and the symptoms are strikingly similar amongst the different people who have reported difficulties with these drivers and 1703.
Take a look at this⌠https://blogs.technet.microsoft.com/configurationmgr/2017/04/14/known-issue-with-the-windows-adk-for-windows-10-version-1703/
Looks and sounds familiar, doesnât it??? How about this?
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/1e34a9e4-5520-43a4-8fe0-f68458db2fff/windows-10-creators-update-device-driver-issue?forum=wdk
Could really use some help here⌠Iâll help you however I can, but first, itâd probably be constructive if youâd be kind enough to concede that there may actually be a problem here.
EDIT by Fernando: Screenshots resized and re-inserted as attachments (can be enlarged by clicking onto them), added a spoiler and removed unneeded blank lines (to save space)
Hey there⌠Looks like youâre only hosting version 5.0.4.43 of the modded Intel drivers. Is there some place where I can download the other ones youâve released since 5.0.1.38? Thanks
Thanks for your detailed report, which verifies,
a) that the Intel USB 3.0 drivers v5.0.4.43 mod+signed have been correctly digitally signed by me and can be properly installed even while running Win10 v1703 and
b) that it is the âSecure Bootâ option, which prevents booting into Win10 v1703, when there are any drivers installed, which havenât been âcorrectly digitally signedâ according to the Win10 v1703 Device Management,
No, but I will attach such driver, if you tell me which version you want to test.
If you would please, I need all the modded versions youâve released after 5.0.1.38, but prior to 5.0.4.43. I donât know how many there are or what the version numbers are. 5.0.1.38 is the last version I downloaded several months ago, so I donât know what versions were released after that.
Yes, thatâs how it appears, but in a a lot of ways, that makes absolutely no sense. Donât you agree? If 5.0.4.43 and 5.0.1.38 are signed exactly the same way, and 5.0.1.38 installs without issue, then why does only 5.0.4.43 trip Secure Boot? Why doesnât 5.0.1.38 trip it as well?? What does "correctly digitally signed" mean exactly, according to Windows? This doesnât make any sense. There must be something weâre missing hereâŚ
@cousinit99 :
Attached is the 64bit DPInst Set with Intel USB 3.0+3.1 Drivers v5.0.3.42 mod+signed by me at 04/19/2017.
Unfortunately I have deleted the previously offered mod+signed Intel USB 3.0 drivers.
64bit DPInst Set with Intel USB 3.0+3.1 Drivers v5.0.3.42 mod+signed by Fernando.rar (2.32 MB)
@Fernando
Ok, essentially, 5.0.3.42 doesnât work on my system either. I say essentially because it kind of does at first, but then it totally doesnât, as odd as that might sound.
- The 5.03.42 drivers install via the Device Manager without issue, with one minor caveat. The 5.0.1.38 drivers donât ask for a system restart when I plug them into the Device Manager, but the 5.0.3.42 drivers do. Iâm absolutely certain that this is significant somehow, because the 5.0.4.43 drivers do the same thing. The difference is that the 5.0.4.43 drivers break the connection to all my USB devices as soon as theyâre installed, whereas the 5.0.3.42 drivers do not. Iâm not sure what exactly causes drivers to set a âreboot requiredâ flag in Windows after theyâre installed, but perhaps you do??
- After a reboot, the 5.0.3.42 drivers will appear to function normally, and they do not trip Secure Boot, but after a relatively short period of system uptime (8-12 hours), something about the way the drivers interact with the Windows kernel causes catastrophic system instability. It starts out as mini-freezes, 6-10 seconds a piece in 0.5-3 minute intervals, but eventually, the system ends up crashing with either a KERNEL_SECURITY_CHECK_FAILURE or a PAGE_FAULT_IN_NONPAGED_AREA bug check, and upon restarting, the system crashes with a PAGE_FAULT_IN_NONPAGED_AREA bug check. At this point, Windows will not load again until Secure Boot is disabled or Driver Signature Enforcement is disabled from the Advanced Startup menu.
My XHCI controller hardware ID is DEV_A12F. Whatâs yours, Fernando? At this point, Iâd say itâs highly unlikely to be the same as mineâŚ
Also, I know this might be a silly question, but did you acquire the 5.0.1.38 drivers from a different person or source than you did the 5.0.3.42 and 5.0.4.43 drivers?
@cousinit99 :
Thanks for your report.
The DeviceID of my on-board Intel USB 3.0 Controller is exacty the same as yours (DEV_A12F).
I generally do not offer any mod+signed driver, whose source files are not taken from the chipset manufacturer.
sound familiar to my problem.
that last version its problematic
In which way? Did you enable the âSecure Bootâ option?
@ all:
Update of the Start Post
Changelog:
- new: âpureâ 32/64bit ASMedia USB 3.0/3.1 Drivers v1.16.49.1 WHQL incl DPInst dated 08/16/2017
- new: ASMedia USB 3.0+3.1 Drivers & Software Set v1.16.49.1 WHQL dated 09/06/2017 Thanks to Station-Drivers for the source package!
I have just installed the âpureâ 64bit ASMedia USB 3.1 drivers onto my Z170 system running Win10 v1703 by using the DPInst method and everything works fine here.
Good luck with these new USB 3.0/3.1 drivers!
Dieter (alias Fernando)
This driver is not worked on Windows XP ???
Which driver do you mean?
Hi geniusâŚthis year i again needed your help âŚ
I need text mode driver for intel h230 chipset motherboard for windows xp installationâŚapart of this driver I also needed usb 3.0 modded driver for eindiws xp
Here a quick compare of driver Intel USB 3.0, ASMedia USB 3.1 performance with a external SATA6G 850 EVO 1TB SSD.
@nitin_jindal :
Without any specification about what you really want (sort of textmode driver and HardwareIDs of the USB 3.0 Controller) I cannot help you.
@100PIER
is the first screenshot with Intel or Microsoft drivers?
comparison of the two drivers on the same hardware could be useful.
the third screenshot is taken with the internal Intel AHCI driver, right?
@elisw
The three tests were done on the same PC (Sabertooth X99 running W10 64bit RS2).
Please look at the black subscreens âDriveControllerInfoâ, you can see what exact driver (manufacturer and version) was used for each test.
The LIAN LI Aluminium USB 3.1 C-Type 2.5" HDD External Enclosure is connected via a USB Cable A Male (PC side) to C-type Gen.1 Male (enclosure side).
Enclosure Internal Interface is SATA I/II/III 6GMbps.
I have updated USB 3.1 ASMEDIA driver without any problem.
Host first, then the Hub when yelow icon appeared at the top of Device Manager console.
I hope your USB keyboard/mouse were not plugged on ASMEDIA ports ?
You should have the both updated to get a proper ASMEDIA USB 3.1 functionality.
It truly relies upon what you are endeavoring to utilize. Another words are you endeavoring to interface an advanced camera, MP3 player, or something different that uses the USB association. On the off chance that you are endeavoring to interface something particular the you have to introduce the drivers that accompanied the gadget or go to the makerâs site. Now that being said if the gadget you are endeavoring to interface is more established than your PC it may not be perfect with it frantic similar remains constant the other route around an old PC and a more up to date gadget. Essay Help UK yet on the off chance that itâs none of the later and you canât discover the product for what you are endeavoring to associate at that point go to the makers site there you can get what you require.
EDIT by Fernando: Since this post has been a reply to posts dated 04. November 2016, I have added the related quotes.