Thank you for your advice, Fernando. Which INF file should I use with dpinst64 command? There are 3 inf files in the driver pack.
I have also tried to install 5.0.4.42 driver pack, the installation process was absolutely smooth without any warnings and PC restarted directly into Windows without any complications from Secure boot.

@Fernando :

I am using your procedure and drivers with mixed results on 3 machines. On my laptop that is windows 10 (but used to be windows 7) it works 100%. On two laptops that are native windows 10, it works partially on one and not at all on the other. My theory is that the poor generic microsoft drivers that are still sitting underneath your good drivers are still being used on the windows 10 machine. I think the procedure works on the laptop that used to have windows 7 because the software using USB 3.0 connections will tap into those older good drivers. Is that possible? If so, what would be your recommended procedure to remove the EHCL 3.0 and 3.0 HUB generic drivers? Manually in the system32 folder and editing the registry? Or some piece of software?

@Fernando

I apologize for not being more clear. I have been able to successfully install your mod+signed drivers on all machines without an issue. Let me give one laptop as an example:

This computer is partitioned with Windows 8.1 on one partition and Windows 10 on a separate partition, so hardware is the same. I am using the computer to control a high speed USB 3.0 camera. On windows 8.1, the camera runs at full frame capture with native drivers (as expected). On Windows 10, I only get about 60% of frame capture with native drivers. I installed your mod+signed drivers and operated the camera at full fps. I rebooted the computer and it continued to capture full fps. I plugged in a second USB device (USB 2.0) into that same computer and now the camera is back to capturing only 60% of frames. The 3 areas (controller, hub, and pci) all show your signed drivers with certificate as the driver they are using so they did not roll back to the old drivers. But it appears that the controller and/or hub and using the other driver in some way to slow down data transfer. That is why I want to try removing the old drivers on windows 10 for usb 3.0.

Does that make sense?

ASMedia_xHCI_Host_Controller_Driver_v1.16.45.1 works in XP SP2 to 100%
on Asus ROG Apex motherboard with z370 chipset.
But you have to copy all USB files from XP SP1 to the folder of XP SP2 Windows\system32\drivers.
I count 400 MByte/sec from this USB 3.1 port on that Asus board,
Dietmar

PS: HardwareID of the ASMEDIA chip is PCI\VEN_1B21&DEV_2142

Hello Fernando, thank you for the great work, I am no longer capped at 35 mb/s and now at 290-300 mb/s! THAT IS FANTASTIC! :) Now I have one small problem, every 10 seconds I hear the sound that the computer makes when you plug a USB into the USB port, the "dun-dun" and then the "dun-don" sound as if something is plugged in and then out over and over and over again.

It is slowly driving me nuts but I cannot figure out what is causing it to happen, do you know a fix for this?

My info:
Gigabyte X99 Designare
i7-6950X
64GB DDR4
980TI

Thanks again kindly,
Michael

In the meantime, I have temporarily disabled the sounds from driving me nuts by going into Windows sounds and shutting off the device disconnect and device connect sound

Good morning Fernando, so I reckon there is no current solution to this problem eh?