I have the same, but it’s not signed in some case (Win8.1, x64). And it’s is fully operational (I don’t expect any troubles for now…)
@iWARR :
After having seen our different test results I can imagine only 2 possible explanations:
- The Device Management of the OS does not only check the content of the associated *.CAT file, but the content of the real driver (= *.SYS file) as well. It may realize, whether the installed driver has been designed for the related system (here: chipset) at all.
- You have previously installed the same driver, but without correct digital signature, and the Device Management doesn’t change it, when you install later on the same driver with a correct digital signature.
By the way: According to my own experiences this happens definitively, if you integrate a mod+signed driver into an OS image. It will be accepted, but as an unsigned driver, and this decision will not be changed, if you import the Certificate after having completed the OS installation. Even a later re-install of the mod+signed driver doesn’t make it listed within the Device Manager as being correctly signed.
I don’t want reinstall Win8.1 in the future 
Ha-ha. I can’t still deside when the time for Win10 (LTSB) will come for me.
Windows is a poor OS, but we don’t have strong alternatives, sadly.
Windows have a lot of troubles within driver signing/installations, including Group Policies and other system settings that won’t work as expected.
I have driver signing turned off in GP, but anyway I have to reboot into special mode in many other sutuations (all people have to…).
So, we can live with it.
Well, lot of people will be thankful to you for the continuation of the 7-Series support. That’s it
I clearly understand, that first of all, driver support depends on manufacturer.
Previous versions were probably more compatible and flawlessly signed with your Cert, v5.0.4.43 is not (for older chipsets), but it can still work with some tricks.
Hi Fernando,
Firstly I want to say thanks for your new "pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando with DPInst option" for 7-series chipset, it works perfectly.
But 1 thing I discovered is that when we connect the USB 3.0 devices to the ports they no longer show "Connected to USB 3.0". So is there a way to bring back this useful feature? Thanks again…
Possibly not with these Intel USB 3.0 drivers from the v5 platform.
Hi,
Same here for me. Version 5.0.4.43 complain that driver is not signed. I’ve just install a fresh copy of Win10x64en. The last working is 5.0.3.42. Any idea ?
@marianob85 :
Welcome to the Win-RAID Forum!
Which DeviceID has your on-board Intel USB 3.0 Controller resp. which chipset has your mainboard?
Where did you find the download link (within the start post of this thread or attached to post #1336)?
Regards
Dieter (alias Fernando)
Dear Fernando,
I was doing a clean Windows 10 Ent 10.0.16299.64 Version 1709 (Updated Nov. 2017) install today and I have encountered the same problem after installing “pure” 64bit Intel USB 3.0/3.1 Drivers v5.0.4.43 mod+signed by me (with DPInst option) as cousinit99 (see USB 3.0/3.1 Drivers (original and modded) (82)). Until I have turned off the secure boot, I was not capable to boot the computer into windows (otherwise it was booting into Windows repair). I have tried both versions of the driver - from post 1 and 1336. During the installation I was warned that windows blocked the installation of Intel USB 3.0 Host Controller Switch driver and Intel USB 3.0 eXtensible Host Controller driver since they were unsigned.
I have ASUS Maximus VIII Extreme (Z170) MB. Any advices, please? Thanks a lot
GenDalf
@gendalf :
Thanks for your report.
I have an Intel Z170 system and use Win10 v1709 as well, but have no problems to get my mod+signed Intel USB 3.0 drivers v5.0.4.43 properly installed and shown by the Device Manager as being correctly digitally signed.
The big difference between our systems is the BIOS setting regarding the “Secure Boot” option. In my case this option is DISABLED.
If your specific BIOS setting (Secure Boot: ENABLED) in combination with my mod+signed drivers should be the reason, why you cannot boot into your OS, you will have to decide, what you want:
a) enhanced security by enabling the “Secure Boot” option or
b) usage of any modded drivers.
Dear Fernando,
thanks for your reply. I understand that I have to choose one of the two options. The secure boot is not an issue to me so I would prefer to have modded drivers.
I would also like to ask you how to use dpinst64.exe to uninstall the drivers.
Thanks a lot
Gendalf
Since
a) the DPInst method just installs the related driver(s) and no additional software and
b) the user can always install another driver on top of the previously running one,
it is not really necessary to uninstall the driver(s).
If you want to do it nevertheless, >here< you can find the way how to uninstall the driver(s) by using the DPinst method.
Thank you for your advice, Fernando. Which INF file should I use with dpinst64 command? There are 3 inf files in the driver pack.
I have also tried to install 5.0.4.42 driver pack, the installation process was absolutely smooth without any warnings and PC restarted directly into Windows without any complications from Secure boot.
The 3 INF files belong to 3 different drivers (1 Controller driver, 1 Hub driver and 1 Switch driver). Since it doesn’t make sense to install or uninstall just 1 of them, you should take them all.
@Fernando :
I am using your procedure and drivers with mixed results on 3 machines. On my laptop that is windows 10 (but used to be windows 7) it works 100%. On two laptops that are native windows 10, it works partially on one and not at all on the other. My theory is that the poor generic microsoft drivers that are still sitting underneath your good drivers are still being used on the windows 10 machine. I think the procedure works on the laptop that used to have windows 7 because the software using USB 3.0 connections will tap into those older good drivers. Is that possible? If so, what would be your recommended procedure to remove the EHCL 3.0 and 3.0 HUB generic drivers? Manually in the system32 folder and editing the registry? Or some piece of software?
@DoubleL :
Although I do not know the exact reason, why you are not able to get the mod+signed Intel USB 3.0 drivers properly installed onto all your laptops with an on-board Intel USB 3.0 Controller, but I do not recommend to totally remove the MS USB 3.0 drivers, which are part of the OS.
I don’t think so.
My suggestion: Use the mod+signed Intel USB 3.0 drivers with systems, where the installation works and you benefit from the installation, but avoid them with the others.
@Fernando
I apologize for not being more clear. I have been able to successfully install your mod+signed drivers on all machines without an issue. Let me give one laptop as an example:
This computer is partitioned with Windows 8.1 on one partition and Windows 10 on a separate partition, so hardware is the same. I am using the computer to control a high speed USB 3.0 camera. On windows 8.1, the camera runs at full frame capture with native drivers (as expected). On Windows 10, I only get about 60% of frame capture with native drivers. I installed your mod+signed drivers and operated the camera at full fps. I rebooted the computer and it continued to capture full fps. I plugged in a second USB device (USB 2.0) into that same computer and now the camera is back to capturing only 60% of frames. The 3 areas (controller, hub, and pci) all show your signed drivers with certificate as the driver they are using so they did not roll back to the old drivers. But it appears that the controller and/or hub and using the other driver in some way to slow down data transfer. That is why I want to try removing the old drivers on windows 10 for usb 3.0.
Does that make sense?
It would only make sense, if
a) you were right with your idea and
b) it will work as expected.
I am pretty sure, that the only result will be a lot of problems, which are bigger than your current ones.
My suggestion: Write a petition to Intel and ask for USB 3.0 drivers, which do fully support all MS Operating Systems from Win7 up to Win10 (like ASMedia does).
ASMedia_xHCI_Host_Controller_Driver_v1.16.45.1 works in XP SP2 to 100%
on Asus ROG Apex motherboard with z370 chipset.
But you have to copy all USB files from XP SP1 to the folder of XP SP2 Windows\system32\drivers.
I count 400 MByte/sec from this USB 3.1 port on that Asus board,
Dietmar
PS: HardwareID of the ASMEDIA chip is PCI\VEN_1B21&DEV_2142
@diderius6 :
Hello Dietmar,
thanks for your interesting find and report.
To make sure, that it will be found by users, who want to install Windows XP, your report should be copied or moved into >this< Sub-Forum. The best solution would be, that you start there a new thread with a title like “[Guide] How to get ASMedia USB 3.0/3.1 ports usable with XP SP3” (or similar) and to attach a RAR archive, which contains the XP SP1 USB drivers, which have to be copied into the the Windows\system32\drivers folder of XP SP3.
Thanks in advance!
Dieter (alias Fernando)
@ all:
Update of the Start Post
Changelog:
- new: “pure” 32/64bit AMD USB 3.1 Drivers v1.0.3.0 WHQL dated 04/07/2017
Good luck with these new AMD USB 3.1 drivers!
Dieter (alias Fernando)