After having read your post, I have done a test with my currently running Win10 x64 Insider Preview 14372. As you can see here, I had no problems to get the mod+signed Intel USB 3.0 drivers v4.0.5.55 properly installed onto my Z97 system:
Since I do not believe, that your problem has anything to do with the Insider Preview Build 14366, I propose to repeat the driver installation.
Here are more details about the āsignatureā problem I have:
1) with W10 x64 v1511 (french version) I observe this signature abnomalie (for Controller Host and Root Hub), however the Intel USB 3.0 modded driver is properly working. Why this āmismatchā about signature ?
2) with W10 x64 Preview Build 14366 (english version) I observe this: Trying again to import CA, W10 detects āCertificate āWin-RAID CAā already in storeā (so I assume CA in well imported):
Native driver:
Intel USB 3.0 Modded driver installation "First step":
Have disk method:
Signature problem detected (Code Error 52):
So, I donāt understand whe signature mismatch in case 1) and the Error Code 52 in case 2).
EDIT by Fernando: Picture size minimized (to save space), can still be enlarged by clicking onto them
@100PIER : I just have repeated the test with Win10 x64 Build 14367 (very similar to your Build number) and could not verify any problem during or after the installation of the mod+signed Intel USB 3.0 drivers v4.0.5.55. To make sure, that we are using the exact same drivers, I downloaded the drivers from my MEGA account and installed them. Here are some pictures regarding the Intel USB 3.0 Controller and its driver:
The pictures verify, that my mod+signed USB 3.0 Controller driver has been accepted by my system as correctly digitally signed.
As you can see within your own picture, the related driver was shown as having an Authenticodeā¢ signature, before you completed the installation. The error message you have gotten thereafter may be caused by an interference with the 2 "Intel(R) C610 series/X99 chipset USB Enhanced Host Controllers" (probably the Intel USB 3.1 Controllers), which are listed within the "Universal Series Bus Controllers" section of your Device Manager.
@Fernando , Thanks, I understand your analysis, however the 2 "Intel(R) C610 series/X99 chipset USB Enhanced Host Controllers" are USB 2.0 only as reported here: Controller 1:
Controller 2:
So, i donāt think to a potential interference.
Moreover, with W10 v1511 I got no Intel USB 3.0 modded driver installation āproblemā, except the āsignatureā abnomalie which is seen as āauthenticā on one sub-menu and seen as āwithout numerical signatureā on one other sub-menu.
So I suspect, that you have installed the related INF file of the Intel Chipset Device Utility. Maybe ths installation has caused your problem to get the mod+signed Intel USB 3.0 drivers properly installed. Questions: 1. Why did you install this Intel INF file? 2. Have you seen a "missing driver" flag within the Device Manager after having completed the Win10 x64 installation?
It would be fine, if you would be able to replace the Intel USB 2.0 "drivers" by the generic MS ones (see the right picture above), to reboot and then to retry the installation of the Intel USB 3.0 drivers.
I donāt know the reason, why you got the message "without numerical signature", because this is what I always get, when I install the mod+signed Intel USB 3.0 Controller driver:
@Fernando , Yes, i have installed āIntel Chipset Device Software v10.1.2.19 WHQLā after completed the Build 14366 installation because there were many āflagsā within the Device Manager Panel. After installed it, all āflagsā disapeared ! May be I should have to install modded USB 3.0 drivers prior to install the Intel Chipset Device Software ? I see in Relese note of Intel Chipset Device Software a fix has been done on USB 2.0 controllers for x99 systems.
I 'll do test to try to replace Intel USB 2.0 drivers with MS USB 2.0 drivers and let you know the results.
@Fernando I have uninstalled the 2 specific USB 2.0 controller (uninstall option Device Manager) and tried to install modded USB 3.0 āfirstā step. I have let the Intel Chipset Device Software WHQL installed because i donāt see an easy āuninstallā option. Here are the screens: You see āsignatureā Err code 52 problem is always present.
After reinstalled the native MS USB 3.0 (automatic serach option) i come back to the native screen:
EDIT by Fernando: The size of the inserted pictures have been minimized by me to save space. Please use the āautoā option, when you insert screenshots (unless it is really important to see all details without enlarging the picture).
Hi Fernando, I am running a ASUS G75VX, I had Windows 10 on it but run into countless driver issues. I reinstalled Windows 8.1 with Update X64 Ver 6.3 Build 9600.
I wish to use the drivers you updated but when I try the force update I get a message that says The folder you spesified doesnāt contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
The USB 3.0 eXtensible Host Controller Hardware Ids are: PCI\VEN_8086&DEV_1E31&SUBSYS_201F1043&REV_04 PCI\VEN_8086&DEV_1E31&SUBSYS_201F1043 PCI\VEN_8086&DEV_1E31&CC_0C0330 PCI\VEN_8086&DEV_1E31&CC_0C03
The "pure" mod+signed Intel USB 3.0 drivers v4.0.5.55, which I am offering within the start post of this thread, should support your on-board Intel USB 3.0 Controller, because I have added the matching DeviceIDs to the related INF files. Please retry to install these drivers according my guide (start post) and make sure, that you a) import the Win-RAID CA certificate (look >here<), before you start with the driver update, b) choose the driver with the correct platform (32bit resp. 64bit) and c) choose the "Have Disk" option, when you are going to update the driver for the "Intel(R) USB 3.0 eXtensible Host Controller". Good luck! Dieter (alias Fernando)
First of all, thank you so much for these modded drivers.
I tried installing the latest v4.0.5.55. Like you said, I first imported and installed the certificates and then proceeded to install the drivers using the have disk option. First I installed the controller driver, but in my system the name was already Intel(R) USB 3.0 eXtensible Host Controller, so there was no change in name. However, I noticed that the name of the hub changed to Intel(R) USB 3.0 Root Hub even before I installed the hub driver. Anyway, I proceeded to install the hub driver too, and rebooted. But sadly, Iām not getting USB 3.0 speeds when I copy content to my pen drive (SanDisk Ultra). Please do take a look at this screenshot and see if thereās anything wrong that I did. I have been struggling with slow USB speeds on Windows 10 as long as I can remember.
Why didnāt you install the USB 3.0 Switch driver? Do you have within the "System Devices" section any device named "PCI Express Root Complex" (or similar)? Regards Dieter (alias Fernando)
Yes, you should update the driver for the device name "PCI Express Root Complex". By the way: If you would have read the start post, you would have known it already.
A couple of days ago I purchased the Dell DA200 adapter to use with a Dell XPS15 9550 notebook (Windows 10 x64) over the USB-C port. It was very hard to make it work: from the first insertion the devices were blinking in and out of the device manager. Iāve found advices on the internet telling to reduce the power of the WLAN card to 75%ā¦ It did not always work, it was better to disable the card completely. Long story short, after two days of frustrations Iāve found your modded drivers for USB 3.1 and installed it. First tests are running quite well, no devices blinking and Iāve restored full power to the WLAN adapter. Weāll see how itās going on from now. Thank you!
@Gix : Welcome at Win-RAID Forum and thanks for your feedback!
Since I havenāt yet modded the Intel USB 3.1 drivers, I would like to know, if you have installed my modded USB 3.0 drivers or the original USB 3.1 drivers.
Yes, you are right - my bad. Thanks for the reminder. I didnāt even remember, that I had already attached these mod+signed Intel USB 3.1 drivers for testing purposes (I cannot test them myself, because I donāt have any system with USB 3.1 ports. So according your report these modded and signed drivers obviously are working fine while running Win10. As a consequence I will offer them within the start post of this thread. Thanks again for having tested these drivers and giving me your feedback!