[INFO] About "modded" drivers and how to get them installed

It works even with the currently latest Win10 Build 16179, which I am running now.
I suspect, that it is the upgrade, which may be responsable for your "problem", which is not really one, because you obviously were able to successfully update the Intel Chipset Device INF files by using my mod+signed variants.
Remember: There is no difference regarding the functionality and stability between a modded and a digitally signed driver!

" There is no difference regarding the functionality and stability between a modded and a digitally signed driver! "…very good to know !!

@Pete12 :
That the digital signature of my modded INF files is accepted by Windows, can be easily verified by
a) doing a right-click onto any of the *.CAT files, which are associated to the *.INF files,
b) choosing the option "Properties",
c) choosing the tab "Digital Signatures",
d) clicking onto "Win-RAID CA" and
e) hitting the button "Details".
It should look like this:

Win-RAID CA Signature is ok.png

Yes, you are right indeed, just checked the folder with the driver-files,they are all “digital signed” , remains the question why we can not see this in the device-manager, all these drivers are " not signed" , and on other tab of the properties they are signed by Microsoft !

signed by Microsoft.jpg

Do we see this only when using Powershell for inserting the certificate ?

No, this has nothing to do with the procedure of the Certficate import.
Since the same mod+signed drivers are shown on my system (OS freshly installed) as digitally signed, I suspect, that it has something to do with the fact, that you had updated your Win10 v1607, which had already used my mod+signed drivers, to v1703 with the consequence, that the Intel Chipset Device INF files were overwritten by the older, but “better” WHQL certified files.
As I already have written: It doesn’t matter whether a “driver” (in this case it is just a text file) is shown for the user as being digitally signed or not. The only important thing is, that the “driver” has been successfully installed and works properly.


I am aware the driver didn’t install and updated the installer accordingly - please re download to get the fixed copy.

EDIT by Fernando: Added link removed, because it is not topic related

To whom did you address this tip?

Thanks for the detailed tutorial.

As far as I know Windows 8+ versions already contain USB 3.0 drivers for Intel’s hardware and you don’t need to install anything else to get your devices working.

Do you know any specific advantages of this method, or do you perhaps have some interesting benchmark results? I didn’t test it myself, I’m just curious.

@adsvoo :
Yes, Win8 and Win10 do contain generic MS USB 3.0/3.1 drivers, which do support Intel USB 3.0/3.1 Controllers and Hub devices as well, but according to the report of many users the Intel USB 3.0/3.1 drivers have a much better performance.
That is why I offer mod+signed variants of the latest Intel USB 3.0/3.1 drivers, which natively only do support Win7, by adding the compatibility with Win8/8.1/10.
You can test it yourself, which drivers are the best for your specific system.
Dieter (alias Fernando)