I was unable to solve the Certificate Issue with the USB Drivers , but it seems specific to the USB Drivers as I Installed the Modded IRST Drivers (14.8.18.1066) and the Certificate for them as a Test with no issues.

I tried replacing the PCI Bus Driver only with the PCI Bus (Intel) and PCI Bus (Microsoft) and the computer still wouldn't boot due to Driver Signing so I tried the PCI Express Root Complex Driver instead and the Computer Booted but USB was disabled in DM due to a Driver Signature Error on the xHCI Controller and Hub ( not sure why a boot was allowed as it is still a driver signature error) so I had to switch the XHCI Controller back to the Intel 3.0 extensible Host Controller (Microsoft) to get it working again.

I am still playing with it , but it maybe another X99 issue like my Raid0 Array seen as SSD's , nobody can solve.

KB

Hi @Fernando ,

which ones should I use for

PCI\VEN_8086&DEV_A12F&SUBSYS_36C117AA&REV_31
PCI\VEN_8086&DEV_A12F&SUBSYS_36C117AA
PCI\VEN_8086&DEV_A12F&CC_0C0330
PCI\VEN_8086&DEV_A12F&CC_0C03

The system is Windows 10 Home.

Many Thanks!

Just to update you Fernando on my Intel USB3 Certificate Issue , I found I had previously download your 5.0.0.32 Drivers but never tried them , so I installed the included Cert. from that Zipfile and then manually Installed the Drivers (no dpinst. option) and Win10 has accepted the Certificate from that download and everything is working Fine.

I retried installing the 5.0.4.43 Drivers on the Controller and had the Driver signature error again in Windows ( not at boot ) , so I rolled back to 5.0.0.32

Any chance this is somehow a Certificate Error in the 5.0.4.43 Download?

KB

Fernando,
I have applied your procedure to replace my current MS USB3.x drivers with Intel modded drivers.
I do succeed and fine.
However I observe a mismatch info on Windows Panel (not signed indication and signed Win-RAID CA):

What is your opinion ?

Hi Deiter , thanks for taking the time to try and figure out the Issue on my X99 system with the Cert. not being accepted on the PCI Bus at Boot and the Controller in Device Manager ( the Root Hub does work with 5.0.4.43 ) but unfortunately I am back to the same problem....

this is very strange since 5.0.0.32 is accepted and so is the Cert. for the latest Series 14. Intel RST Modded Drivers I am also using now.

I have once again Rolled Back to 5.0.0.32 on the PCI Bus , Controller and Root Hub and everything seems to be working fine .

***Attached is the Output from the Import Cert Command from the Admin Prompt.

KB.

Zitat von Fernando im Beitrag #1580

---

@Kbird:
Thanks for your interesting report.
Since the Win-RAID CA Certificate itself (named Win-RAID CA.cer) hasn't been changed by me since 10/25/2015, different Certificates cannot explain your different results while using different driver versions.
Although I am currently not at home and have to use my Xiaomi Air Notebook (with a KabyLake CPU) running a freshly installed Win10 x64 v1803 with the in-box MS USB 3.0 drivers, I tried to find out the real reason for your issue.
This is what I did:

1. As first step I rebuilt the package named "pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando with DPInst option" from scratch, deleted all *.cat files and gave all 3 included drivers a new Win-RAID CA signature dated 05/01/2018.
2. After having successfully imported the Certificate, I ran the DPInst64.exe of the freshly built driverpack as Admin, waited until the installation had been completed and restarted the notebook (required for the final function of the new "System device" named "PCI bus").
3. After having rebooted everything was fine (all 3 Intel USB 3.0 devices worked properly and all their drivers were shown as being correctly digitally signed). Here are the related pictures:
   

To give you the opportunity to test the freshly re-signed latest Intel USB 3.0 drivers yourself, I attach the related 64bit driverpack.
Please give me your feedback.

---

Hi, motherboard Asus Prime B360. Original and modified versions from this topic are not installed (Error Code 10).
ID
PCI\VEN_8086&DEV_A36D&SUBSYS_86941043&REV_10
PCI\VEN_8086&DEV_A36D&SUBSYS_86941043
PCI\VEN_8086&DEV_A36D&CC_0C0330
PCI\VEN_8086&DEV_A36D&CC_0C03

Forgot to mention, Windows 7 x64. And of course, it will be great to add my deviceID to the modified drivers. Is it really going to work?

Hi Fernando, the driver has installed the instructions. The installation was no errors, but USB still does not work. In the device manager, a yellow exclamation point on the USB 3.0 controller. On the motherboard, the device is specified as 3.1 gen 2.
Here's more info:
Compatible IDs
PCI\VEN_8086&DEV_A36D&REV_10
PCI\VEN_8086&DEV_A36D
PCI\VEN_8086&CC_0C0330
PCI\VEN_8086&CC_0C03
PCI\VEN_8086
PCI\CC_0C0330
PCI\CC_0C03