@oduis :
Welcome at Win-RAID Forum and thanks for your report!
@dubba :
Welcome at Win-RAID Forum!
I doubt, that it will be possible to get any Intel USB 3.0 driver working with Windows XP. Nevertheless I will do a deeper look into this sort of compatibility problem, when I will have some time to do it.
Regards
Dieter (alias Fernando)
@dubba
Intel has never provided xHCI drivers for Windows XP, unlike Renesas, for example.
Your MB has a BIOS setting that permits to downgrade Intel USB 3.0 ports to USB 2.0, thereby allowing the MS EHCI driver to function ("Intel xHCI Mode" set to "Auto" or "Smart Auto")
Thanks for your replies, Dieter and @shroeder. I was aware that Intel has never provided xHCI drivers for XP and that the Smart Auto xHCI mode is recommended but I got excited by the phrase āusable with all Windows OSās from Win7 (maybe even from XP) up to Win10 and all Intel chipsets from 7-Series upā in the first post in this thread ā perhaps the reference to XP should be removed! The lack of Intel xHCI drivers for XP is a shame because my board is otherwise an excellent bridge between the Windows 10 and XP worlds, the latter being the OS I still use for a lot of music production work with vintage PCI audio hardware. Intel provides XP drivers for every other one of their components on the board so why not the USB3 controller?
@dubba
xHCI support is not built-in XP.
So, in order to have a functionnal xHCI implementation Under XP, apart from the driver in itself, you have to build on your own a correct xHCI stack, and thatās not a trivial task (you can also licence a successful implementation like ASMedia did with MCCI).
When the first Intel chipsets with native USB 3.0 appeared (2012), XP was already on the decline in terms of market share.
Hence this sad decision.
@Fernando
FYI, v1.16.43.1 drivers for ASMedia USB chips comes from MS (http://download.windowsupdate.com/d/msdoā¦99d304dbeb1.cab)
As it has always been the case in the past, MS WHQL certify the drivers they offer only for the latest incarnation of Windows available ATTB, which is Windows 10 Anniversary Edition aka Redstone 1 (before v1.16.38.1, it was Windows 10 NOT anniversary Edition).
You can verify this with sigcheck -d.
I found this thread while searching for a Renesas driver for streamlining my Win7 installation disk. I have an MSI AMD motherboard and the USB 3.0 driver is a compressed setup file which doesnāt let me extract it down to the base driver files level. It seems Renesas doesnāt provide the basic driver to the general public like, say, Realtek does for their network controller chips.
My motherboard uses the UPD720202 controller whereas the drivers provided by Fernando are for the UPD720200 and 720201. I havenāt gone through the whole thread yet to see if there are any updates or reports on whether these drivers work with a 720202. Iām not lazy but so far I simply havenāt had the time to wade through 45 pages of posts. So if anyone knows of any post about this concern, would you be kind enough to point it out?
In the meantime, thank you Fernando.
@Pimpom
In fact, to be precise
.drivers v2.1.39 are intended for ĀµPD720200/ĀµD720200A
.drivers v3.0.23 are intended for ĀµPD720201/ĀµPD720202
(maybe Fernando should modify the description)
As for the reason for not providing bare drivers, well Renesas has always released their drivers in 2 packages : 1 Installshield setup EXE and a 1 ZIP archive, but most manufacturers prefers to strip down the package with only the Installshield version because itās simpler to use for end-users.
For example, here is the full package for your chip (EXE+ZIP) : http://www.adnaco.com/doc/USB3-201-202-DR-WIN-20120928.zip
Thanks a lot, shroeder, for the clarification and for the download link. This seems to be exactly what I was looking for.
@Pimpom
Welcome at Win-RAID Forum!
Yes, the Renesas Gen2 USB 3.0 drivers v3.0.23.0 do support your Renesas USB 3.0 Controller.
Regards
Dieter (alias Fernando)
Done!
Thanks for the info and the tip!
I wanted to thank you Fernando, you saved me a huge headache. I personally registered just to thank you. Iāve been having problems with my 5TB external hard drive (Seagate) which would hang and stop working when transferring huge files (4gigs+) onto it. My other 2TB external hard drive (Western Digital) never had this problem. I was going to RMA it but then I tested it on my Haswell build and speeds were fine. So I knew it was a driver issue with my Gigabyte Z170 motherboard.
I googled Z170 USB 3.0 Drive issues and this thread popped up. https://communities.intel.com/thread/98173
Even Intel admits that there was a problem. Someone linked this thread and you saved me a huge headache from not RMAing a perfectly fine harddrive. Also, now my USB 3.0 hub works on my monitor and donāt get recognized as a USB 2.0 hubā¦
@MintFresh :
Welcome at Win-Raid Forum and thanks for your positive feedback!
I am glad, that my modded drivers helped you to solve your problem.
Regards
Dieter (alias Fernando)
There is a new sofware and drivers Asmedia 1.16.41.3 from Station drivers.http://www.station-drivers.com/index.phpā¦id=2522&lang=fr
@Big_Barn :
Welcome at Win-RAID Forum (I am sorry for the delay) and thanks for the info!
@ all:
Update of the Start Post
Changelog:
- new: ASMedia USB 3.0+3.1 Drivers & Software Set v1.16.41.3 WHQL 10/25
- optimized and re-uploaded: āpureā ASMedia USB 3.0+3.1 Drivers v1.16.41.3 WHQL dated 10/07/2016 (now with 32/64bit DPInst files for an easy installation)
Thanks to Station-Drivers for the source package.
Enjoy it!
Dieter (alias Fernando)
Helllo
(newbie here)
Sorry to crash-in but Iām being tormented by a problem to which this topic seems relevant (if it isnāt, no doubt the mods will move it to where it is).
I recently swapped-out my obsolescent motherboard for a Skylake one (MSI Z170-PRO), plus upgraded cpu and memory. Previously, I was dual-booting Windowa 10 Pro and XP Home and my plan was - and still is, if only I can achieve it - to carry on doing that because I have some valued software which wonāt run on anything later than XP.
Iāve been struggling for some time to put that into effect, and failing every time so far. My latest approach (based on info found elesewhere) has been to install a third-party usb3 controller because Windows 10/Intel have no native usb drivers which support XP. The idea is to use this to instal XP from a usb flash-drive (I have prepared one), in the process installing the necessary SATA/AHCI drivers.
Iāve bought such a third-party device (can be seen here: https://www.startech.com/Cards-Adapters/ā¦ower~PEXUSB3S23 ); StarTech claim that it supports XP. Though itās branded as StarTech the chip is an Etron Tech EJ168A and I assume that Etrom is OEM for the whole thing.
The problem Iāve now come up against and canāt find any solution to is that the Etron driver supplied with the StarTech card fails every time to install under Windows 10, with the error: āThis device is not configured correctly (Code 1)ā and āInstallation of this device is forbidden by system policyā¦ā (no such system policy exists). So Iām completely stymied.
Is anyone able to suggest a workaround? Or do I have to give up the whole idea (and junk the StarTech card)?
@roberto :
Welcome at Win-RAID Forum!
Not me, I donāt know any. It is generally not a good idea to run an extremely old Operating System with brandnew hardware. Both parts have problems to communicate with each other.
If I were you, I would remove the StarTech card and use the Intel USB 3.0/3.1 ports in 2.0 mode as long as you really have to run Windows XP.
Regards
Dieter (alias Fernando)
P.S.: Please shorten your signature, because it uses too much space within each of your posts. 2-3 lines are enough for the informations (mainboard, chipset, OS, SATA/NVMe mode) we need within this Forum.
@Fernando
Thanks for replying (and so swiftly)
Iām afraid I donāt understand this. How does one select what mode these ports are to be run in?
Maybe your mainboard BIOS offers the option to disable the USB 3.0 resp. USB 3.1 functionality of the Intel USB ports, with the result, that they are running in USB 2.0 mode.
Another option is to use the native USB 2.0 ports of your mainboard (provided, that such ports are available).
Not me, I donāt know any. It is generally not a good idea to run an extremely old Operating System with brandnew hardware.
Further thoughts, if youālll pardon me.
While certainly taking your point more generally, my specific question didnāt in fact relate to that.
What Iām struggling with at the moment concerns only Windows 10-compatible hardware (the StarTech card) and software (the Etron controller-chip driver). Iām trying to install the provided Etron driver into Windows 10 Pro (not into XP; I havenāt, since changing the motherboard, got XP installed yet).
Sorry if I didnāt make that clearer.
Iām seeking some way in which to overcome Windows 10 refusal/inability to install this driver. Itās not something Iāve ever encountered before.
Doesnāt the Win10 in-box generic USB 3.0 driver support the Etron USB 3.0 Controller?
If not, have you tried to manually install the latest Etron USB 3.0 driver?
@ Fernando
After the card is installed in the machine it shows-up in āDevice Managerā, under āOther Devices > PCI to PCI bridgeā, with yellow exclamation-marks.
I presume this means Windows 10 has no native driver for it?
But that shouldnāt be a problem because an Etron driver for it is provided, on a bundled CD. But all my attempts to install that bundled driver (and alternatively a different version of it dlād from the StarTech website) have been fruiitless so far, producing the error-messages I quoted.
One other thing. Iāve gone through I forget how many āSystem Restoreā cycles in the process of making several attempts to install it trying different options. The first time I did this, System Restore reported the drivers which would be removed as the Etron driver (as expected) and - puzzlingly - another driver which I hadnāt known had been installed at the same point:- INTEL (System) 13/10/2016 (oem71.inf). It never appeared again at any of the subsequent install device/System Restore iterations I performed.
Itās probably of no significance - I only mention it just in case.