Once for the 2 different versions? As I have to made this again…
After having read your reports I am not sure anymore regarding this point. On the other hand your reports and my own test have verified, that the drivers have been correctly digitally signed and the "Win-RAID CA" certificate has been accepted by the OS as trustworthy. So it is not easy to understand why you had to import the "Win-RAID CA" certificate once more.
I have this problem, but I don’t know if this is modded drivers-related: I fitted a new internal USB 3.0 card reader (onto Intel header), but it can be detected only if hot-connected. From cold boot I get the unsuccesful device enumeration in device manager (no excclamation marks). What do you think? Edit: it seems drivers related, no issues with Win 10 stock drivers…
Hi Fernando, are there any real world advantages in using Intel USB 3.0 drivers on Windows 10? Does speed or reliability improve with Intel over Microsoft? I am asking because I see no reason for Intel not to make improvements available on latest hardware and software.
I installed your modded Intel 3.0 drivers, because my Device Manager says: "Code 10: This device cannot start" with the USB xHCI device, and the USB3 ports are working as USB2.
Installation was succesfull, but I still get the same message. Any idea what could be the culprit?
I am using a fresh install of Win10 Pro, on a Clevo W650SZ laptop.
This happened already before you tried to install my modded drivers? If yes, this indicates an uncomplete or faulty installation of the Win10 in-box USB 3.0 drivers. If a reboot doesn’t solve the problem, you can try to uninstall the related device from withijn the Device Manager and to reboot again.
You have to make sure, that you update the driver software of the Intel USB 3.0 eXtensible Host Controller. 2. After the update of the Intel USB 3.0 Controller’s driver software you should reboot your computer. 3. Then you can update the driver software of the Intel USB 3.0 Hub device(s).
Yes, it happened after I updated from Win7 Ultimate x64 to Win10 Pro x64. Then I used Media Creation Tool and did a clean install of Win10 Pro x64. I have uninstalled / reinstalled / rebooted many times now, but the error still remains.
I added your digital signature, went to Device Manager > xHCI update driver > select manually > go to your iusb3xhc.inf and succesfully installed the driver (also the hub driver and switch driver).
I feel like I tried everything right about now, ha…
btw, When I install the hub driver as step 2, that one gets a code 10 as well.
EDIT by Fernando: Unneeded parts of the quoted text removed (to save space)
I have tried to install the last version x64 bits of Intel modded USB 3.0 driver to replace the native USB 3.0 MS driver on my Asus x99, W10 x64. Unfortunatly I does not succeed. I got no error message when install, but after updating part 1 , then part 2, then reboot I observe that the MS driver remains and i does not see any appearance of the installed new modded in device manager panel. All seems the modded driver is "ignored". The Intel USB 3.0 MS is still working properly.
You should switch to the default MS in-box USB 3.0 driver. It doesn’t make sense to get the modded Intel driver installed, when not even the default MS driver works.
This issue may be caused by the fact, that I have used a new certificate while giving the drivers a digital signature. Maybe it would have been better to use the old certificate, which was created at home with my normal computer. Actually I have to use my laptop.
After having seen your reports, I just have installed the latest mod+signed Intel USB 3.0 drivers v4.0.2.42 onto my Surface Pro 3 laptop running Win10 x64 Pro. Result: They are working fine.
I’m new to this great forum. Installed the modded drivers on my Z77 system. Did the certificate installation procedure first with the .cat files. Working perfect. Thanks a lot Fernando