new: ASMedia USB 3.0+3.1 Drivers & Software Set v1.16.47.2 WHQL dated 05/02/2017
Thanks to 100PIER for the info and vmanuelgm for the source file!
I have just installed the “pure” 64bit ASMedia USB 3.1 drivers onto my Z170 system running Win10 v1703 by using the DPInst method and everything works fine here:
Good luck with these new USB 3.0/3.1 drivers! Dieter (alias Fernando)
I still wonder if its usefull to update these drivers , I did so after every Asmedia-update, I keep the same transfer-speed from intern HDD to extern HDD , about 180MB/sec. Never encountered any speed-improvements after updating them… Or am I doing something wrong …??
@Pete12 : The users can expect some benefits from an updated SATA/NVMe/USB Controller driver, but this does not mean, that each driver update will automaticly boost the performance of the connected devices. Functionality enhancement and bug fixes are the most common reasons for a driver update.
@YuriyCN : Is this a serious question? Do you really believe, that Intel spends any money for the development of XP drivers, which do support the latest Intel chipsets?
Finally an Asmedia driver that works correctly on my Asus Rampage IV Extreme X79, the 1.16.47.2 I downloaded it from driverscloud.com, the first driver that works after 1.16.41.3
I have find in the controller that whatever version driver i use, it dont use uasp protocol. And then i found this : Note: UASP feature requires in conjunction with the in-box drivers on Windows 10/8 and Mac OS X. The ASMedia driver currently does not support UASP. -http://ableconn.com/products_2.php?gid=46
but if i restart my machine windows 10 download from windows update the asmedia driver so i lost uasp. lets hope asmedia that will realease a driver with uasp enabled.
@Fernando , The today published ASMedia USB 3.x v1.16.47.2 driver on Station_Drivers does specify WHQL W10 RS2 compliance. I used it on ASUS P8Z77 and does work fine, so seem no longer need v1.16.45.1 for a Z77 machine. For X99 machine the new published v1.16.47.2 does work fine also.
@Fernando , The AMD drivers listed here are for old AMD chipsets, so i’m wondering if there is any chance you can include the drivers for the new chipset (Ryzen)?
new: “pure” 32/64bit Intel USB 3.0/3.1 Drivers v5.0.4.43 WHQL for Win7 dated 05/11/2017 (with added DPInst file for an easier installation)
new: Intel USB 3.0/3.1 Drivers & Software Set v5.0.4.43 WHQL for Win7 dated 05/12/2017 (thanks to Pacman resp. Station-Drivers for the source package)
new: mod+signed 32/64bit DPInst Sets with Intel USB 3.0/3.1 Drivers v5.0.4.43 mod+signed by me at 06/26/2017
freshly signed by Microsoft: “pure” 32/64bit ASMedia USB 3.0/3.1 Drivers v1.16.47.2 WHQL refreshed dated 04/12/2017 (now with WHQL stamp for all Operating Systems from Win7 up to Win10 v1703)
freshly signed by Microsoft: ASMedia USB 3.0+3.1 Drivers & Software Set v1.16.47.2 WHQL refreshed dated 05/02/2017 (now with WHQL stamp for all Operating Systems from Win7 up to Win10 v1703) Thanks to 100PIER for the info and Station-Drivers for the source file!
Good luck with these new USB 3.0/3.1 drivers! Dieter (alias Fernando)
@quetzalin : Thanks for your request and the posted DeviceIDs. As soon as I will have the required time, I will modify the old AMD USB 3.0/3.1 drivers by adding the posted DeviceIDs, give them the Win-RAID CA signature and offer them within this thread. Hopefully they will work (I am not sure about it).
Only adding the device ids to the ones posted here won’t work, i think they are completly different and newer drivers. You can get (extract) them from the AMD Chipset driver pack here (linking the latest version i could find): https://www2.ati.com/drivers/amd-chipset…rcp22-apr27.exe And i think they are also officially signed for Windows 10… not sure about this, i was just gathering all the USB 3.0 drivers i can find to integrate on my Win7 ISO and discovered the AMD USB 3.0 for Ryzen drivers are missing here.
EDIT by Fernando: Unneeded parts of the fully quoted post and unneeded blank lines removed (to save space)
new: “pure” 64bit AMD USB 3.0 Drivers v2.0.0.26 WHQL dated 02/10/2017 for AMD Zeppelin Chipsets (with Ryzen CPU)
Notes:
A 32bit version of these drivers is not available.
For an easier installation I have added the 64bit DPInst files. Since I cannot try it myself, I am hoping for a feedback from users, who have tried the DPInst method.
Thanks to quetzalin for the info regarding these USB 3.0 drivers.
@Fernando Hi, Fernando, I’m running into a problem with the Intel USB 3.0/3.1 drivers.
Specs: i7 3770K Asus P8Z77-V Pro 980 TI 4 X 4GB DDR3 2 X 128GB Crucial M4 RAID0 1TB Seagate HDD
I followed the steps to importing the certificate as directed here. I copied the 2 files, “ImportCertificate.cmd” and “Win-RAID CA.cer” into “C:\Cerfiticate”, right-clicked Start Button, chose the option “Windows PowerShell (Admin)”, wrote “cd C:\Certificate” and hit the “Enter” key, wrote “.\ImportCertificate.cmd” and hit the “Enter” key again, entered “y” (for “Yes!”), when prompted and everything seemed to have worked out ok. I then proceeded to install the driver found in this thread (“64bit DPInst Set with Intel USB 3.0/3.1 Drivers v5.0.4.43 mod+signed by me”), and I received 2 errors about the installation being blocked because of unsigned / invalid certificate (can’t remember which). I rebooted and I was hit with the Windows automatic repair screen. I tried to exit out to Windows 10 but that failed and I ended up back at the same screen. Then I chose the advanced troubleshooting options to disable driver signature enforcement and was able to boot into Windows. Now, I installed the driver again and this time all 3 drivers updated without any error messages about the installation being blocked, so I thought this was it. Rebooted and I was once again hit with the automatic repair screen. Again, I chose to disable driver signature enforcement and got into Windows. Final attempt, I did the Win-RAID CA.cer method and restarted only to encounter the same problem. How do I stop Win10 from blocking your modded driver? Help!
@hoeman : Thanks for your report. To be honest, I do not really know the reason why you got these problems after having installed the related mod+signed Intel USB 3.0 drivers. Maybe it has something to do with the fact, that the v5 platform Intel drivers have not been designed for Z77 Chipset USB 3.0 Controllers. I had added the related HardwareIDs within the related INF file to get these new drivers installed onto Intel 7-Series Chipset systems, but maybe there is a compatibility issue. Questions: 1. Are you using a clean installed Win10 or have you upgraded from anyother Windows OS? 2. Have you ever used any of my mod+signed Intel USB 3.0 drivers before? If yes, which driver version was it and which was your experience? 3. Which “pure” USB 3.0 drivers resp. which Installer Set version did you use, before to installed the latest mod+signed Intel USB 3.0 drivers?
To get rid from the annoying “Automatic Repair” screen and the need to disable driver signature enforcement at each (re)boot, I recommend to replace the currently used mod+signed Intel USB 3.0 drivers by the generic MS Win10 in-box ones.
This is the way how to do it: 1. Let Win10 create a restore point. 2. Open the Device Manager and expand the “Universal Serial Bus Controllers” section. 3. Right-click oto the listed “Intel(R) USB 3.0 eXtensible Host Controller” and choose the options “Update driver” > “Browse my Computer…” > “Let me pick…”. 4. Provided, that the box “Show compatible Hardware” is checked, you will see the device named “USB xHCI Compliant Host Controller”. 5. Click onto it, choose “Next” and let it be installed. 6. Maybe you have to update the driver for the device named “USB 3.0 Hub” the same way. 7. After the next reboot your on-board Intel USB 3.0 Controller and its Hub Devices should use the generic MS USB drivers.
@Fernando To answer the questions: 1) Clean install of Win10 using the 1703 build 15063 iso modified with NTLite to insert the optimal RAID driver for my configuration (v11.2.0.1006 with Intel RAID ROM 11.2.0.1527 with credits to you and your hard work!) 2) I have never used any of the mod+signed Intel USB 3.0 drivers before. This was my first time trying. Prior to installing these drivers, it was running on the default out of the box Win10 USB 3.0 drivers. As an aside, I did not use the mod+signed drivers either for the RAID driver as you mentioned that it is not necessary for my 7-Series chipset as that is officially supported. 3) I did not use any “pure” USB 3.0 drivers as you said those are only for Win7 and I am on Win10.
I have been able to roll back to the original Win10 drivers but I refuse to believe I can’t install this when I’m sure many others have managed to do so successfully. I just don’t understand why Windows keeps blocking it despite having imported the certificate. Now I’m inserting the drivers into the ISO using NTLite and might try a clean install with the modded drivers. Not sure if that would work. Thoughts?
EDIT: Looks like I am unable to remove the original components using NTLite unless I purchase a license. Hmm… I might use an older Win10 iso and follow the older procedure to get modded+signed drivers on.
Fernando - with the latest DPInst I am getting an issue with the certificate authority once the drivers are installed, it is saying in devmgmt that the driver signature is unable to be verified - did something change? I am on Windows 10 Creators build, the last driver package worked perfectly fine.
EDIT by Fernando: Unneeded fully quoted post removed (to save space)
If you should mean the latest mod+signed Intel USB 3.0+3.1 drivers v5.0.4.43, I have no problems with their signature and I am running Win10 v1703 as well: [[File:Intel USB 3.0 mod+signed Pic1.png|none|auto]][[File:Intel USB 3.0 mod+signed Pic2.png|none|auto]][[File:Intel USB 3.0 mod+signed Pic3.png|none|auto]]
Please post the related screenshots from your system (>here< is a guide about how to do it).
