New to forums, but want to express my thanks to you for your USB 3.0 modded drivers for Intel. I went practically crazy talking to Microsoft support. and the Microsoft and Intel forums. I used the dpinst.exe. and the drivers went in just fine. Thanks a lot. Bob Neufeld
Iāve just installed your latest drivers on windows 10/64bit. - before installation, i ran the cmd-script for the certification - after installation has completed, my computer needed to restart - after restart, no usb-device works anymore. i canātenter windows as my keyboard is not recognized. i donāt have an ps2-adapter for mouse and keyboard. How do i enter windows now? This is the worst BS iāve ever seen.
edit: - installation included the intel extensible USB3.0 inf, no other drivers have been installed. - computer is an i4770 on an asrock H87 pro 4 with 24 GB ram desktop machine
Are you not able to connect the keyboard and the mouse with any non-Intel USB port? Are you sure, that you have updated the correct Intel USB 3.0 Controller?
USB devices were recognized during boot up. As soon as logon screen appears, every single USB port on my computer is dead. This is a REAL nightmare. Tons of software activations run on that system and none of them can be deactivated for later reinstallation! I did everything as explained during installation and have NEVER experienced such a mess. Iām using windows since 3.11-
No, i didnātā¦i modified the usb3-drivers on win7 without any issue, so i felt comfortable. The ASROCK H87 i use has HEAVY issues with usb3.0 on 64bit OS. Devices with high power consuption such as musical input devices and external sound cards donāt work properly on 64bit. I realized, itās the intel extensible host driver that causes the issues. On win 7 you can deactivate the device, in win 10 you canāt: the only option is to uninstall the drivers. So i wanted to use modified to see, if the problems could be solved that way. I have never imagined that all usb devices could just end working when updating the extensible driver. As i said: this is a real mess now.
edit: is there any chance to remove drivers via dos prompt?
Hi Fernando, Coup27 from the Anandtech foruns. Amazing website. Iāve been on here about 2 hours now learning a lot.
Iām afraid like Sunbe I am also having problems.
I have an ASUS H87I-PLUS mITX motherboard. According to my motherboard specifications:
IntelĀ® H87 chipset : 6 x USB 3.0 port(s) (4 at back panel, , 2 at mid-board) IntelĀ® H87 chipset : 8 x USB 2.0/1.1 port(s) (4 at back panel, , 4 at mid-board)
So 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.
Edit: 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.
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.
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.
I have no idea if this will work or not but itās a suggestion.
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.
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.
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.
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?
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.
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!!!
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!