Thanks a lot, I will give it a try tonight.

Just one quick question : I read many things about following a precise order when reinstalling USB drivers (starting from the chipset). That's what I always do for new windows 10 installs of course.

But in my situation, would you install your new modded drivers right away or uninstall and reinstall the chipset before (and restart the computer in between ?).

Laurent

Zitat von Fernando im Beitrag #2203

---

@gienos324:
If you want help from my side, you should give me the following information:
1. Which OS are you running?
2. Which are the HardwareIDs of the on-board USB 3.0/3.1 Controller (right-click onto it > "Properties" > "Details" > "Property" > "HardwareIDs").

---

Hi @Fernando

Still no luck, the transfer rate is stuck at USB 2.0 speeds... its really strange! Like before Aidai64 sees the ports as 3.0... but the connexion with the drive is 2.0...

I tried Dell support, but still no luck.
I think im running out of options :)

Best,
Laurent

Zitat von Fernando im Beitrag #2210

---

My advice: You should either switch to Win10 as OS (its generic in-box MS USB 3.0/3.1 drivers will work) or use a third party USB PCIe adapter card.

---

Anyone here knows how to re-enable Secure Boot when deciding to revert back to the default MS driver in Windows 10 provided that I did not create a restore point?

@Fernando, if you still remember from a few weeks ago I already tried this. All my USB controller devices are now using the MS default WHQL-signed drivers but when I re-enable Secure Boot in the BIOS, Win 10 still doesn't boot.

@Fernando

I don't understand. This definitely has something to do with this topic. The problem of not being able to boot with secure boot enabled only happened AFTER installing your modded drivers and reverting backcto the MS drivers. This has happened to me twice on the same system already. I can easily recreate the issue by reinstalling Windows in secure boot, installing your modded drivers, reverting back to the Win10 drivers, and then reenabling secure boot.

I'm simply asking help from people here. I'm sure that even after updating the usb drivers back to the MS WHQL drivers, there are still remnants of the modded drivers and secure boot is detecting those and not letting Windows 10 boot as it's supposed to. Secure boot defends the system from rootkit attacks so thisnis expected behavior for non-Windows signed drivers.

I'm really confused as to why you don't consider this on-topic when it's obvious that the modded drivers were the ones causing the conflict with secure boot. I mean it's even clearly stated in the first post that secure boot will not work with these drivers. What gives?

@Fernando

No problem, I'm glad we're on the same page now. Before you add this info in the post, I want to be 100% sure first. I'm still troubleshooting now but I have high hopes that removing any trace of the modded drivers will allow secure boot to work again. Secure boot isn't like a one-time thing, you should be able to revert back to using it. As a first troubleshooting step, I've used Autoruns to see which drivers are being used by the system and here's what I saw:



So even though I updated the drivers I see in device manager, I still see that the system is using them somehow. Those three sys driver files are the exact driver files included in your "pure 64bit Intel USB 3.0+3.1 Drivers v5.0.4.43 re-mod+signed by Fernando" driver package. The problem is that when I go to device manager and double-check all USB controller devices there (even the hidden ones), I see that they all use the MS default drivers (other sys files). So how do I make the system NOT use these modded drivers anymore?