@Tumko:
Just to avoid misunderstandings: You were talking about the ASMedia USB 3.1 drivers. This thread is about all available USB 3.0/3.1 drivers.
Hello, I created an account just to say THANK YOU! This thread helped me on a annoying error that was happening for weeks. I had some problem with my external drives that whenever it reads/write all of the usb ports in the mobo would crash. That was driving me crazy and the only solution I found here. I searched for a solution everywhere, tried everything. Turns out the problem was the USB 3.0 divers.
@andreksu :
Welcome at Win-RAID Forum and thanks for your feedback!
It is fine, that you were able to solve your problem and I am glad, that our Forum could help.
Regards
Dieter (alias Fernando)
@Fernando ,
Do you have an idea what these outdated ASMedia Package that WU does seem install in anyway after v1.16.44.1 were DPinstalled ?
No.
What lets you tink, that Windows Update has installed anything after you had installed the v1.16.44.1 drivers?
@Fernando ,
Looking at GEEK uninstaller tool, I see for these 2 suspect entries an āInstallation Folderā named DIFX:
I totally ignore what is DIFX, and why DPinst64 is here.
I suspect, that these entries have something to do with the formerly used DPInst method without associated DPInst.xml file.
This is the relevant entry of the new xml file: "<suppressAddRemovePrograms/>".
That means, that after the usage of the new "ASMedia USB 3.0/3.1 DPInst driverpack v1.16.44.1 WHQL" you may not see such entry.
@Fernando ,
Thanks, I understand.
I have now uninstalled these 2 āWindows ASMedia packageā and so it is now clean, and the current driver v1.6.44.1 does continue to work fine.
@Fernando ,
I come back again to this strange action of Windows Update about ASMedia USB3.x driver.
The official SETUP of ASMedia package WHQL seems do update only the Host Controller and do forget the Root Hub driver.
Windows Update does detect this abnormal situation and does apply the "ASMedia USB Root Hub" driver update:
Hi,
I registered just to give feedback:
Intel USB 3.0/3.1 Drivers do NOT work properly on a Microsoft Surface Pro 4 with Surface Dock.
The installation of the Intel drivers goes smoothly, however - the Network adapter on the Surface Dock ceases to function (it connects and disconnects from Device Manager every 10 seconds).
There is hidden linkage/association of the MS Networking Adapter with USB 3.0 drivers.
Unfortunately, all the drivers listed in this thread produce the same result: They break the Network adapter on the Surface Dock and render it unusable.
Rolled back to Intel drivers provided by Microsoft.
EDIT by Fernando: Unneeded blank lines removed (to save space)
@ctp9 :
Welcome at Win-RAID Forum and thanks for your feedback, which will be very useful for other users of a Micosoft Surface Pro 4!
I personally had no problem to get the latest Intel USB 3.0 drivers properly working with my Surface Pro 3, but contrary to the Pro 4 model the Pro 3 Surface Dock doesnāt have an Ethernet Controller.
Regards
Dieter (alias Fernando)
Hi @Fernando ,
Iām glad Iāve found this forum, because it seems thereās no chance Iām gonna find help anywhere else.
Hereās the issue Iām having and Iād appretiate if you could suggest something.
I have a Dell XPS 9550 with windows 10 on it (fresh reinstalled, as a result of trying many things over the past couple of weeks).
Iām trying to connect my Nikon D810 via 3m long usb 3.0-micro-b cable and getting ādevice is not recognizedā.
I also have a simple usb to type-c connector and with this connector via same cable via type-c port everything works like charm.
I know for a fact that my usb 3.0 ports potentially have enough power to handle 3m long cable, thereās just something wrong with driversā¦
Iāve tried everything suggested on the web, Iāve tried Intel modded driver presented here and Iāve also tried USB 3 Link Power Managment setting (which sounded like exectly what I needed) , but no result so far.
@kkonst :
Welcome at Win-RAID Forum!
Which are the HardwareIDs of the Nikon D810?
Regards
Dieter (alias Fernando)
@Fernando
Thatās a shame 
And it is working with a small usb 3.0 cable, but not with the long one.
A couple of month ago I had D800, which is basically almost the same, and it was working perfectly with usb 3.0 long cable. Something mustāve changed with one of the recent drivers or updates.
If it would be a driver problem, you wouldnāt have gotten your Nikon D810 working by simply using an USB > Type C Adapter.
@Fernando
It sure seems to be a driver problem.
It seems like there (suddenly) isnāt enough amperage in USB 3.0 ports. Type-c is capable of more in terms of power, isnāt it? Thatās why itās working, I think.
Drivers are not responsible for amperage in ports.
I totally agree with you.