[Outdated] USB 3.0/3.1 Drivers (original and modded)

@Mithi :
Thanks for having answered my questions.
The performance of the USB connected devices depends not only on the USB Controller and the in-use USB driver, but on the quality and the data caching ability of the used USB devices themselves.
Have you already tested the speed of a high quality USB 3.0 Flash Drive, when it was connected to any of your USB 3.0/3.1 ports?

@Fernando :

Intel USB 3.0-3.1 Drivers v5.0.4.43 [MOD] works fine on Z77 (Win8.1, x64), same as v5.0.3.42.
So, I’m suggest it’s NOT “only for Intel Chipsets from 8-Series up”, but for the 7-Series also.

Thank you for your nice modding, as ever.

UPD:
------
I’ve found that “Controller Driver” (Intel(R) USB 3.0 eXtensible Host Controller) wasn’t updated within DPInst64 and the version is still 5.0.3.42.
Manual installation wasn’t applied also (the x64 driver was not found in the “Controller Driver” folder).

The “Hub Driver” and “Switch Driver” are OK, they were updated to v5.0.4.43.

It’s strange… For now, within this configuration (5.0.3.42+5.0.4.43), USB 3.0 devices working as expected.

@iWARR :
Thanks for your feedback.
So I will continue to add the related HardwareIDs to the INF files of the future Intel USB 3.0 driver versions.

@iWARR :
Can you please re-check, whether the “Controller Driver” folder contains the 64bit driver v5.0.4.43 or not?

Name from the *.inf (v5.0.3.42): PCI\VEN_8086&DEV_1E31&REV_04
Full ID Name (Device Manager): PCI\VEN_8086&DEV_1E31&SUBSYS_84CA1043&REV_04

In some case my ID is not represented in the “iusb3xhc.inf”.

I can try to fix *.inf file and reinstall, if I’m understand correctly.
UPD: Just adding my ID didn’t worked… But the driver was found this time…

@iWARR :
Thanks for the quick reply.
Since the correct 64bit driver is within the “Controller Driver” folder of the packae named “pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando”, you should be able to manually update the Controller driver (maybe you have to use the “Have Disk” method).


Correctly. "Have Disk" method was used to check if my fix will work. But it doesn’t, as I’m said in previous post.
The driver was found this time, but within the error in case of unsigned driver. (I have your cert insalled, of course).

@Fernando Thank You

I have problems only when I try to transfer large single files, the drives frequently disconnects & connects again.

@Fernando :

I have “Controller Driver” working. What I’ve done:

1) Fix “Controller Driver” *.inf file with my ID.
2) Reboot into Unsigned drivers install mode
3) Install “Controller Driver” manually

Note: other drivers from the pack - “Hub Driver” and “Switch Driver” - have absolutely no issues and have been insalled automatically within DPInst64.

So, you have to fix something in your pack, because the drivers working.


Just tried to write and read 10Gb file on the 64Gb flash drive (Intel USB 3.0 port) - no issues. This is on your side, I think.

That is interesting, because the original INF files of the Intel USB 3.0 Controller drivers (no matter which version), even those, which are natively designed for DEV_1E31 Controllers, do not contain any SUBSYS-ID.
I am not sure, whether I will remember to add the specific SUBSYS-ID of your Controller, when I am going to mod+sign the next upcoming Intel USB 3.0 drivers.

Don’t worry, just put back the standard strings for ASUS Z77 you had all the time before (but missing in the last version), this will be enough (I’ve use it right now also):

1
2
3
4
5
6
7
 
[Intel.NTAMD64]
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_00
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_01
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_02
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_03
%IUsb3XhcDeviceDesc01% = IUsb3XhcModel, PCI\VEN_8086&DEV_1E31&REV_04
 
 
... etc

@Fernando :

ASMedia USB 3.0+3.1 Drivers & Software Set v1.16.49.1 works fine on ASUS P8Z77-V DELUXE !

It’s hard to find good versons of the ASMedia USB 3.0 for the ASUS mobos, not every pack will work.
For example, v1.16.45.1 and v1.16.47.1 didn’t.

So, I’m happy to have recent v1.16.49.1 working at last. Thank you very much for your great support, Fernando :slight_smile:

Ahhhh, now I remember, that I had prepared 2 different variants of the last mod+signed Intel USB 3.0 drivers, one of them with DEV_1E31 support, the other without, but only the latter variant has been uploaded and linked within the start post of this thread (Title: “Only for Intel Chipsets from 8-Series up”).
So it would be no problem for me to offer the variant with DEV_1E31 Controller support within the start post.

@Fernando :
The question is why "Controller Driver" was recognized as "Unsigned" (can be installed rebooting into Windows unsigned driver install mode only), but "Hub Driver" and "Switch Driver" have no issues?

@iWARR :
I don’t know the reason why the Controller driver was detected by the OS as “unsigned”.
To find it out I just have re-signed all drivers of the “pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando with DPInst option”, which additionally do support the DEV_1E31 Controllers of Intel 7-Series Chipset systems.
This package is attached.
Can you check, whether the installation of all 3 components works and all 3 drivers are detected as being correctly signed?

pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando with DPInst option.rar (2.3 MB)


• all 3 components works and can be (re)installed within DPInst64 / Have Disk options with no issues

• Signatures (Device Manager):

Controller Driver___Intel(R) Corporation | Unsigned !!!
Hub Driver_______ Intel(R) Corporation | Win-RAID CA
Switch Driver_____Intel | Win-RAID CA

@Fernando :
I’ve tried to reinstall your cert also from your new updated pack. But script says that cert was already found in my system…
May be I have some obsolete sert? And system won’t install the new one?

UPD:
------
My “Win-RAID CA” cert - until 01.01.2040

@iWARR :
Thanks for having tested my freshly signed attached Intel USB 3.0 drivers.
Your test result confirms your previous find, that the Controller driver is not shown by your system as being digitally signed (although it definitively is digitally signed).
In a few minutes we will know, whether this is caused by the fact, that your Intel 7-Series Chipset is natively not supported by the driver or not.
As a second test I will install now the exact same mod+signed Intel USB 3.0 drivers onto my new Xiaomi Air 13,3 notebook, which has a KabyLake CPU and is running Win10 x64 as well.
Then we will see, what happens to my system.

That is absolutely normal. You have to import the Certificate once and will have it as long as your are running your current system (until 2040).

The installation of the Intel USB 3.0 drivers went flawlessly.
Here are the pictures:

USB driver Pic1.png

USB driver Pic2.png

USB driver Pic3.png