Zitat von Coup27 im Beitrag #330So all my USB ports are Intel ones. I have added the CA certificate using the batch file method and rebooted. I then try and update the "Intel(R) USB 3.0 eXtensible Host Controller" by pointing device manager to the iusb3xhc.inf file but after clicking next it says the driver file is already up to date. I then try the "have disk" method and force it to accept the iusb3xhc.inf file and then all my USB ports stop working. My PC doesn't crash, but I now have no keyboard or mouse. If I force shutdown using the power button and reboot my USB ports are still not functioning.

This is absolutely the same procedure and result that i am experiencing.How can we circumvent your drivers to be loaded during boot? Mouse and keyboard work until your driver is loaded during bootup. I have no idea how to avoid/fix that by command line.

Zitat von Coup27 im Beitrag #330Edit: Sounds like Gekko and I are having the same issue. Both lost all USB ports as soon as "Intel(R) USB 3.0 eXtensible Host Controller" has been updated. I think you should pull these drivers temporarily until we can investigate what is happening. Fortunately for me I am just messing around and I have a spare SSD I have loaded up Windows 10 on and I can switch back to my other SSD with Windows 7 on. I updated the USB drivers on Windows 7 using the original drivers and everything went fine.

Did you manage to repair windows 10 by using windows 7 on a separate SSD or vice versa?

Zitat von Gekko im Beitrag #332Did you manage to repair windows 10 by using windows 7 on a separate SSD?

No. Basically I am just messing about. I bought a new larger SSD which I installed Windows 10 on and I am messing around with Windows 10 before I decide how my final installation is going to look. If it breaks, like now, I just secure erase it and start again. I can swap the SATA lead onto my other SSD and boot my working Win 7 install like now.

This doesn't help you much and I really don't know how you're going to get out of this one. I must say I was surprised the driver borked my USB ports. I spent ages reading and following everything to the letter. When device manager wouldn't accept the driver because it said it was up to date I knew something was wrong because the whole point of it being signed was so that didn't happen. I decided to try the have disk method anyway and then this happened.

I think you should perform a full image of your broken install. At least then you can try multiple fixes without worrying about making things worse. If we can find one that works at least then if we have made it worse you can restore back to now and apply the fix. And in my experience, system restore / Windows repair never work. You can install Windows over the top of a Windows but that generally makes a mess of things, but if you image first you've got that option in the bag.

After making a full image of what you have now just in case boot a Linux live distro and delete the current driver for the Intel(R) USB 3.0 eXtensible Host Controller. Obviously I can't screenshot from my Win10 install but this is what it looks like on Win7. Maybe if the driver is deleted when Windows boots up it will fall back to the Microsoft driver?

That is probably because you tested a hard drive. Really it needs to be either a high performance USB stick or an SSD via a SATA>USB3 adapter. I would do the test but at the moment I can't get the latest ones to work on Windows 10.

@ Coup27:Welcome at Win-RAID Forum and thanks for your contributions. It is fine, that you joined my Forum as a member.

Zitat von Coup27 im Beitrag #330Sounds like Gekko and I are having the same issue. Both lost all USB ports as soon as "Intel(R) USB 3.0 eXtensible Host Controller" has been updated.

According to my knowledge your issues are not caused by a faulty Intel USB 3.0 Controller driver (I am pretty sure, that the modded Intel USB 3.0 drivers are working fine with your systems), but by the dependencies between the USB 3.0 Controller and Hub drivers. It is the missing Intel USB 3.0 Hub driver after having rebooted, which seems to be responsable for your problems.Maybe it can be solved by updating both drivers (the Controller and the Hub driver) before doing the reboot.

ZitatI think you should pull these drivers temporarily until we can investigate what is happening.

Since I don't believe, that the drivers themselves are faulty, I will add an additional warning for users, who don't have the possibility to temporarily switch to an USB port, which is managed by another (non-Intel) USB Controller.

ZitatFortunately for me I am just messing around and I have a spare SSD I have loaded up Windows 10 on and I can switch back to my other SSD with Windows 7 on. I updated the USB drivers on Windows 7 using the original drivers and everything went fine.

Gekko - I loaded a Linux live distro and deleted the iusb3xhc.sys file and booted back into Windows but it did not work. I found PS/2 mouse in my attic which I used to open device manager and it had a yellow symbol on it saying "Windows could not find the driver file or the driver file is currupt". The USB ports still did not work. I clicked on rollback driver and it rolled back to the Microsoft driver and they instantly started working again. I've checked and your motherboard does have a PS/2 port on it so the easiest way out of this for you is to buy either a cheap PS/2 mouse or PS/2 to USB adapter and then use that to rollback the driver in device manager.

Fernando - Firstly, even after installing the CA certificate the controller driver will not install by browsing to the directory. Device manager says the driver is up to date so that is not correct. Second, it is not possible to install both the Controller and Hub drivers before rebooting. By using the have disk method, the moment the controller is updated the USB ports stop working.

I have confirmed with the use of a PS/2 mouse that your theory is correct and the problem is the dependencies between the USB 3.0 Controller and Hub are missing. Once I update the Hub (did not need to use "have disk" this time, presumably because no driver was installed) the USB ports instantly started working again. At least on some motherboards which don't have a 3rd party USB controller you will need either a PS/2 or Bluetooth mouse to complete the task. Although is this because the controller is not installing without the "have disk" method?

Zitat von Coup27 im Beitrag #337Even after installing the CA certificate the controller driver will not install by browsing to the directory. Device manager says the driver is up to date so that is not correct.

Yes, the user will get the following message:The answer to the question, whether the installation of a mod+signed driver works automaticly (after having browsed to the driver software on the computer) or has to be forced by using the "Have Disk" button, depends on the details (date/version number/digital signature) of the driver you want to update and the details of the driver you want to get installed.The Windows Operating Systems may evaluate the generic MS driver for Intel USB 3.0 Controllers as "better" than any not WHQL certified Intel USB 3.0 driver.

ZitatSecond, it is not possible to install both the Controller and Hub drivers before rebooting.

That is true, if you try to update the related drivers manually, but I thought about using a customized Intel USB 3.0 Drivers Installer.I started already some tests with such package on my Z97 system running Win10 x64 and was able to prevent a quick abortion by renaming the driver folder from "Win7" to "Win10", but at least I got this message:

I registered just to confirm that the issue is not a driver issue. It is most definitely the communication between Hub/Controller. I am using a Z97 Asus Sabertooth Mark2 /USB 3.1. Luckily I was able to use the ASMedia 3.1 plugs for mouse & keyboard after I installed the Intel 3.0 controller driver. I have never seen a "Hub" device located within device manager so I was hesitant about trying it. Working with it got it working and all my USB devices, intel and asmedia, are working as expected.

It for sure is frustrating but you can do it! Thank you Fernando!!! :D

Note - do NOT update ASMedia 3.1 USB drivers if you use the Z97 ASUS Sabertooth Mark2/USB3.1. Use original included drivers. I was unable to use USB2.0 devices in the USB 3.1 ASMedia port after updating, and sure enough, to Fernando's point, you will most definitely need a PS/2 mouse or USB2 different manufacturer controller to get this to work!

(oops I guess this is in the wrong place, don't know where to post it)

Thanks to mrces2, e.v.o and in particular Zwulf for being a big part of the project, and to Fernando: Dude, you are a computer god!

I have a 2-month-old laptop with the latest components (Skylake quad-core CPU, Samsung 950 Pro PCI-e NMVe M.2 SSD, etc.) and have had issues with Intel USB 3.0 since near the beginning. I did a fresh install of Win 10 Pro on the M.2 drive, and installed the needed drivers from a Drivers partition on the HDD that came with the system (replaced with SSD), plus anything remaining from the Lenovo support page for my system.

When all was said and done, my system listed Intel host controller with "- Microsoft 1.0" or similar. After installing the certificate, and needing to use the "have disk..." method for steps 1 & 2, I now have full speed! Woooooooooooooooohoooooooooooooooo!!!

First of all you are doing an awesome job. I hope you can help me with my problem. I am having a Rosewill RC505 usb 3.0 add on card with Renesas/NEC uPD720200A chipset with windows 10 Pro 64 bit OS. The driver version 2.1.39 is already installed. But the card is not detecting any USB devices connected(WD My BOOK/Pendrives). After some troubleshooting, i found out that it will work when the OS is booted into safe mode. PFA the screenshot of the device manager when booted in normal mode and also the device hardware id

Unfortunately it didn't solve the problem. After a few minutes connected or a large file transfer the adapters gets disconnected :/

I've searched all over and it seems there's something to do with usb drivers. Actually with your drivers it improved a bit (with unmodedd ones as soon as I transfer something from my network ..boom! Dead!)