I updated the driver "Intel(R) 8 Series C220 Series B xHCI HC - 8C31" as recommended by you.
After that, exclamation mark on it, with another description: "Controlador host eXtensível Intel(R) USB 3.0".
It seems, this modded driver isn’t working yet. 
Have another mod to test?
Which message do you get, when you right click onto the device and choose the option "Properties"?
Please check, which ones of the listed USB Hub devices belong to the Intel USB 3.0 Controller, and try to update their driver by using the file named iusb3hub.inf, which is within the modded driverpack. Then reboot and look, what happens.
Not yet.
I have suceed to install USB 3.0 v4.0.0.36 modded to replace the native W10 MS 1.0 driver.
Performances are now as expected. This demonstrate that native driver MS 1.0 driver is very bad because working at a USB 2.0 level performance… not really more.
The Setting procedure to "Disable Driver Signature Enforcement" is quite more complex (may be depending of W10 version).
For a W10 x64 Home Edition the path is:
settings->update/security->recovery->advanced startup->restart now->reboot->repair->advanced option->settings to change windows startup->start->select F7 key->W10 is now up with the "disable driver signature enforcement" feature and then we can modify the driver(s) via the classic "have disk" method (ignoring again the Red warning message).
("Windows cannot load the device driver for this hardware. Driver is corrupt or absent (Cod 39).")
Images for the other Device Manager USB entries:
"Windows cannot load the device driver for this hardware. Driver is corrupt or absent (Cod 39)."
???
Here, you said:
And here, you said:
???
Nevertheless, this is driver detail:
Both of them gives exclamation mark, even after reboot.
I installed both, but iusb3hub.inf itself asked for the iusb3xhc.sys file (because I put it in another folder to force just iusb3hub only files). Because it asked for the other, I put it back to original folder.
But exclamation came back.
Both INF files gives the same picture above, with iusb3xhc file.
And here, you said:
The picture verifies, that you took the correct inf file.
My conclusion: It seems, that it is either not possible to get any Intel USB 3.0 driver running with Windows XP or the needed modification is more difficult than I thought.
Nevermind. You’ve already done the best modded drivers for the users community.
Thanks!
If you really should have installed both INF files, when you tried to update the driver of the Intel USB 3.0 Controller, then you have made a mistake.
These would have been the correct steps:
I uppdated this one (arrow):
Note that I have 2 “Generic USB Hub” and 2 “USB Root Hub”. And other 2 Intel(R).
I don’t know exactly which ones is to apply your steps.
Yes, but did you retry the update according my last post? If yes, did you succeed?
Yes, you have to find out, which ones are the Intel USB 3.0 Hub devices, before you continue with step 3.
I’m having the same slow usb 3 issues under windows 10 pro, motherboard uses the stock x99 chipset with an added renesas hub for the 4x rear usb3 ports. pnputil lists several 1.0x intel usb drivers. My plan is to start with the hubs and uninstall ALL of them from device manager, restart with driver signing disabled, install your modded usb 3 driver controller manually, and then hub manually, and then use the extracted inf files if there are any left overs.
1 - I updated the first iusb3xhc.inf for "Intel(R) 8 Series C220 Series B xHCI HC - 8C31"
2 - Exclamation mark.
3 - Reboot.
4 - I looked for the right USB hub attaching a pendrive into a blue connector (USB 3).
1st Generic USB Hub (before pendrive):
1st Generic USB Hub (after attach pendrive):
(Note "USB Mass Storage Device" entry that came up)
2nd Generic USB Hub:
1st USB Root Hub:
2nd USB Root Hub:
(USB 3.0 - blue connector - is 1st Generic USB Hub)
5 - I unplugged pendrive (using safe remove procedure).
6 - I tried to update 1st Generic USB Hub using iusb3hub.inf.
7 - Message "Location has no information about your hardware).
8 - I tried to update all other USB entries (Generic and Root).
9 - Same message.
I missed something?
Other mistake?
I am able to try any test.
My plan failed, it simply reinstalled the in-box drivers after a shutdown, and when I tried to update driver, said already using better drivers. Will try again later.
I don’t know.
Since you didn’t even get the USB 3.0 Controller driver properly installed (there was still a yellow flag), I suspect, that it is impossible to get these modded drivers to work with Windows XP.
Thanks for having done the tests.
You will always get this message, when you try to replace an original driver by an older or a modded one.
You have to force the installation by using the "Have Disk" button!
@Fernando
NOTA:
I succeed the update from USB 3.0 MS native driver to the modded USB driver only for my P8Z77 W10 platform.
On the Asus Sabertooth x99 platform the process stops during the "have disk" operation and this operation seems to destroy the keyboard/mouse driver and so i get no longer the hand !!
So, i have had to reinstall a last (AOEMI) backuped image and uses the MS USB 3.0 native driver at the moment.
Do you see why this conflict ?
Not really.Which DeviceID has the on-board Intel USB 3.0 Controller of your X99 system?
@ 100PIER:
Thanks for your screenshots.
As soon as I have the needed time, I will think about your problem and a possible solution.
