Re-enabling secure boot after trying out non-WHQL USB 3.1 drivers

kevindd992002 said:

I never do a repair install on my own system as I never trust Windows doing things to itself without my consent. If I would need to do any installation to fix this, I would be reinstalling it. But like I said, it would be my last resort.

I see my suggestion don't suit your needs. Good luck.

Out.

Basically, in addition to reverting to the MS WHQL drivers using device manager, you need to also use the included DPInst64.exe to remove the driver packages. It's like the command-line version of uninstalling a software from Programs and Features (similar to msiexec if you will):

1. DPInst64.exe /u {path to iusb3xhc.inf} /d -> in my case I uninstalled this driver using device manager and making sure to check the "uninstall" checkbox; this will remove all binaries and registry entries too
2. DPInst64.exe /u {path to iusb3hub.inf} /d -> in my case, this driver was not used at all but was still installed
3. DPInst64.exe /u {path to iusb3hcs.inf} /d -> in my case, this removed the driver from being boot-critical

Reboot, re-enable secure boot in BIOS and enjoy :) To really clean it up, delete number 2 and number 3 entries in Autoruns and delete the sys files in C:\windows\system32\drivers

@Pejole2165, thanks very much for your help, I really appreciate it.

- - - Updated - - -

sygnus21 said:

I see my suggestion don't suit your needs. Good luck.

Out.

I appreciate your suggestions but I just needed more technical tinkering instead of resorting to the easy way out. I mean no offense but I was in IT support in the past and learned the hard way. In case you're interested in the solution, see above.

Pejole2165 said:

Well I commend your tenacious nature. Glad you got it sorted eventually...whoopee.
Solution was in the end easy....getting there took a bit of work and thinking, that part was harder.
I think my warnings to others to not try these sort of custom drivers still stands...even in a forum where the majority of users are tinkerers.
Hopefully your system is back to the way you want it.
NOW DO A BACKUP!!!

Yes. In the end the solution is always an easy one :) That Export-WindowsDriver cmdlet led the way.

I agree. Trying custom drivers is not for the faint of heart, especially when the modder of those drivers don't fully understands the possible effects to your system.

I was actually about to configure my backup system before all these happened. I just finished setting up my Linux NAS and that will be the storage for my backups. But yeah, thanks again for the help.