My 3TB Hitachi Desk Pro is recognized by Windows 10 device manager but is is not recognized by Disk Management. To be more precise, it is unknown in Disk Management thereby incapable of being initialized. See the error message below.
Background info I have had this issue since I first upgraded from Windows 7 to Windows 8 and now on the latest Windows 10 (v.1703) (OS Build 15063.138). It works flawlessly on Windows 7 and on Apple OSX.
I have pretty much spent a lot of time gathering information about this, trying everything to find a solution. . What I have learned & tried Fortunately, your USB 3.0 drivers provide the closest thing to a solution. However, after a few minutes after I installing your drivers, the HDD begins to disconnect when I attempt to use it. It gets worse whenever I unplug and plug it back in or restart the computer. At this time, as I attempt to copy a file etc., after a second or more later, it disconnects then reconnects, interrupting the read/write process. See a full video showing what happens in spoiler.
I have disabled all the power suspend options in Windows 10 for all USB controllers, in control panel and using registry tweaks with no avail.
For the purpose of testing to see if the HDD is functional, I have recently installed Windows 7 on two a Dell and Toshiba notebooks and have used on those machines GParted Live CD (a small bootable GNU/Linux distribution). The HDD works flawlessly on USB 2.0/3.0 ports, which is not possible in Windows 8/10. After upgrading back again to Windows 10 on both machines, the problem persists.
I have also come to understand that this is the issue with many other people with the same HDD and with different brands. Unfortunately, Microsoft have proven to be incapable of providing a fix for this which is incredibly frustrating at this point for many users.
Suggestions Can you or anyone else out there make a suggestions on something else that I could try?
Motherboard - Gigabyte H110M-DS2 OS - Windows XP SP3 (32-bit)
>32bit Intel USB 3.0/3.1 Drivers v5.0.1.38 mod+signed by Fernando< (>MIRROR<)
Driver is installed, but regrettably USB does not work. Get the error in Device Manager - "Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)" Exist other driver for Win XP and HardwareID= VEN_8086&DEV_A12F?
@YuriyCN : Where have I written that the Intel USB 3.0/3.1 drivers, which have been mod+signed by me, do support Windows XP? These drivers have been designed by Intel exclusively for Win7 and I made them usable with Win8/8.1/10, but I am not able to customize them in a way to be usable with Windows XP.
There cannot exist any Windows XP driver, which natively supports the HardwareIDs of modern Intel USB 3.0/3.0 Controllers, because these devices didnāt exist at the time, when XP was up-to-date.
Wow, I may have found the issue that was causing my HDD to disconnect repeated with your drivers. I will confirm this after using it for a couple days. Thanks Fernando! Your drivers are working perfectly now.
@Fernando , Last red line typo : v5.0.3.42 for the modded version. After the W10 āupgradeā (via āWindows10Upgrade9252ā application) from āRS1ā to āRS2ā do we have again to apply Certification ?
Fernando is right you cannot mod the Intel USB 3.0 drivers to work on XP. They never made any for XP to begin with so that already makes it impossible to modify since it never worked for XP. I did try modifying a Z77 Intel USB 2.0 driver which worked on XP but it does not work on Skylake in my initial tests. There might be a way to mod it successfully but I donāt have the time to keep testing it so I recommend you look at my guide and purchase a cheap $7 USB card off eBay which allows full functional USB ports with Windows XP drivers.
Can you help me, how to upgrade from moded v5.0.1.38 ?
I dont want to use DPInst set. I would like to upgrade classically via device manager. Drivers only. I can find appropriate places for Controller Driver = Intel(R) USB 3.0 eXtensible Host Controller and Hub Driver = Intel(R) USB 3.0 Root Hub in my device manager, but i cant find right place for Switch Driver. Im sure last time i updated it from generic MS driver to intel v5.0.1.38 aswell. Or should i roll back to MS generic and update from MS generic to v5.0.1.38 (now i will use v5.0.3.42 ofcourse) as you described in 1st post under intel driver spoiler? (After you edited post with v5.0.3.42, itās gone).
Many Thanks to Fernando for making these Intel Win7 drivers available for Windows 10!
My system is an ASRock Q2900 (Intel J2900, DEV_0F35) with Windows 10 Pro 64 bit Creators Update 15063.138 installed. (No UEFI used)
My problem with the Microsoft drivers for the Intel USB ports is, that I can either use my USB devices (like mouse and keyboard) for accessing the BIOS and when using MSDOS or FreeDOS drivers (when the BIOS setting is āAutoā) but not in the Windows boot manager or on the Windows desktop until I start a script with āDevCon Rescanā - or I can set the BIOS to āSmart Autoā and then it works under Windows but no more in the BIOS or with DOS.
My hope was that your modded Intel drivers could fix this problem and I wonāt need my selfmade script with āDevcon Rescanā any longer to activate my USB devices under Windows. So I installed your certificates and your drivers and rebooted. But unfortunately, the mouse and the keyboard were not activated for the boot manager nor for the Windows desktop or by my script with āDevCon Rescanā.
With a PS/2 keyboard I opened the device manager and found there 3 of your devices properly installed and activated but the USB mouse and keyboard were still not working. Iāve reverted to the previous installed Microsoft drivers then and the USB devices were activated immediately without a reboot. What can I do to solve this problem?
So, Iām afraid Iām back to troubleshooting but I have learned something new. The reason why it was working perfectly with your driver was because the system couldnāt eject the HDD. Basically, nothing I did could eject it even though nothing was using the HDD. I assume I created a scenario that somehow caused some part of the OS that regulated USB ejections to lock up. As soon as I restarted the machine, the symptoms returned. What do you think about this?
@100PIER : Thanks for posting the exact location of the typo you had found (I had searched for it within the complete start post). The related typo has meanwhile been corrected.
Seems like a problem with your system not with the drivers. Try reverting to the stock drivers that come with Windows. If that doesnāt help i would suggest itās a wrong BIOS setting?
Please read my post #970 more carefully again, e.v.o.
Iāve tried all the USB3 BIOS settings already: "Enabled" and "Disabled" are unusable, "Auto" and "Smart Auto" are both doing only half of the job. There is no setting that enables my USB devices all the time for BIOS+DOS usage and also under Windows. Then I thought that Intel should know their system (J2900 chipset) maybe a little better than Microsoft, and so I tried Fernandoās modded Win7 drivers. The installation was simple and successful, but my USB mouse and keyboard did not switch on at all, not even after unplugging and reconnecting them. Finally, I reverted to the previously installed stock Windows drivers and my mouse and keyboard appeared back to life immediately.
@Fernando I found this message (shortened) in the event log:
EDIT by Fernando: I have put the event log details into a "spoiler" (to save space) and attached the screenshots by using the Forum software (for a better visibility)
So with these usb drivers on windows 10 creators update x64 pro should xhci hand-off be disable or enabled in the bios. I know the bios says to enable it for older operating systems, but is it needed since the intel usb 3 driver is modded for widnows 10?
Since I donāt have this BIOS setting option with my ASRock Z170 mainboard, I cannot answer your question. The mod+signed Intel USB 3.0 drivers v5.0.3.42 are running fine here with a fresh installed Win10 x64 Pro v1703 ("Creatorās Update"), although I havenāt changed any BIOS setting.
