@iWARR:
I don't know the reason why the Controller driver was detected by the OS as "unsigned".
To find it out I just have re-signed all drivers of the "pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 mod+signed by Fernando with DPInst option", which additionally do support the DEV_1E31 Controllers of Intel 7-Series Chipset systems.
This package is attached.
Can you check, whether the installation of all 3 components works and all 3 drivers are detected as being correctly signed?

@iWARR:
Thanks for having tested my freshly signed attached Intel USB 3.0 drivers.
Your test result confirms your previous find, that the Controller driver is not shown by your system as being digitally signed (although it definitively is digitally signed).
In a few minutes we will know, whether this is caused by the fact, that your Intel 7-Series Chipset is natively not supported by the driver or not.
As a second test I will install now the exact same mod+signed Intel USB 3.0 drivers onto my new Xiaomi Air 13,3 notebook, which has a KabyLake CPU and is running Win10 x64 as well.
Then we will see, what happens to my system.

Zitat von iWARR im Beitrag #1338

---

I've tried to reinstall your cert also from your new updated pack. But script says that cert was already found in my system...

---

The installation of the Intel USB 3.0 drivers went flawlessly.
Here are the pictures:

@iWARR:
After having seen our different test results I can imagine only 2 possible explanations:

1. 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.
2. 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.

Zitat von Jhawk55 im Beitrag #1344

---

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?

---

@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)

@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.