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

Pejole2165 said:

The apology still stands, I could have worded my entry reply better, that's on me.
There is obviously something going on at the Windows pre boot stage where it initialises all the hardware, at that point it is loading a "driver" that is incompatible with secure boot. I say "driver" because it could be a related setting in the registry and I tend to lump everything that affects hardware into the "driver" category.
The remove software part I am talking about is when you use device manager to uninstall a driver there is usually a check box on the confirmation dialog to remove driver software, this deletes the driver files from the Windows backup it keeps of installed drivers in case you want to re install a device.
If you uninstall a device then restart Windows, it will sometimes re detect the removed hardware and install the drivers automatically from the backup.
Autoruns would definitely show you all the services/ programs etc loading at start up and may show you the problem device if you know what to look for, if you see something odd, write it down then find the file and choose properties and hope there is a recognisable description.
You may have to bite the bullet and re install Windows or try an in place repair upgrade, but an upgrade may not remove the problem item.
The folks at Winraid should be able to tell you what to do, keep asking. You might want to see if there is a file list in the install package so you can see what was installed, or an .INF you can look through.

Apology accepted then :)

Yeah, I see what you're saying and I know that checkbox you're talking about.

Thanks for the tips. I don't have access to my system now but I'll see what I can do when I get home later.

sygnus21 said:

Not to state the obvious but that's not really a safe practice - disabling Secure Boot to install questionable 3rd party drivers. Yes, I know of Win-RAID, but still.... And with Windows 10, I'm not sure why you'd need a tweaked USB driver.

Anyway I've no idea why you can't simply reverse the disablement of Secure Boot and have the system work as normal unless something got hosed (or worse) during the driver trial.

Edit: Try this when you get the screen where you enable Secure Boot there should be a setting with something akin to RSA keys. In the area there should be a setting to load the default keys. Try that and go from there. Be aware you wont get that screen until you get to the Secure Boot screen.

Outside of that, my best suggestion at this time would to try a repair install to try and fix the boot problems. You might also try resetting the BIOS by doing a Clear CMOS. In fact, I might try the BIOS reset first.

Good luck.

I agree that it's not safe but I don't mind the risk. I just did a trial and realized then that the Win10 drivers are enough and that I didn't want to lose being able to boot securely.

In post #3, I already tried clearing and loading the default keys for secure boot and that didn't help.

Well than might I suggest you post this issue in Win-RAID since they suggested you do what you probably shouldn't have done. They probably have more experience in dealing with this type issue.

Sorry I can't be of any further help.

Pejole2165 said:

Un check the entries in Autoruns, this will stop the .sys files being loaded from the registry. All Autorun does is put a "Disabled by Autorun" key with the values so you can easily reverse the change if needed. Make sure you run Autorun as admin (right click, run as admin) in case the entries are protected by permission's. Then re boot for changes to take effect.
Hopefully that will solve your issue, fingers crossed. :)

That didn't do it It got me into a BSOD loop with an "INACCESSIBLE_BOOT_DEVICE" boot loop. I'm not sure how usb drivers are related to the boot device? Now how can I bring them back if I can't access Windows anymore?

Pejole2165 said:

I Really don't see how USB drivers can cause the boot device to be inaccessible unless the custom drivers made the boot drive a USB device itself, which I can't see happening, it makes no sense.
Do you have a Macrium boot disk or any custom boot disk for troubleshooting?
If you have a Macrium disk you could try the Fix Boot option, this may bring the disk back online.
If not I think at this point your best bet would be a re install, there is obviously something those drivers have done that they really shouldn't have.
Regardless of how you get the system back I would try to condense all these posts and your steps taken into a post on WinRaid forums and hope someone can explain exactly what these drivers do, that is if you are still interested at this point.
I'm sorry this has turned into a nightmare, the steps taken to remove these custom drivers should in theory work, however they obviously do something we can't pin down.
If you have a Win10 setup disk there is a trick involving Notepad to open a file explorer to copy any files to a backup if you need to, there is a tutorial on it in these forums somewhere, a search should find it.

Right. But based on my google fu, that stop code is a generic code for corrupted drivers. So I think the system is still looking for those drivers even though we disabled them in autoruns.

You said all autoruns does, when you uncheck the box, is to add a registry entry, right? Do you know where that exact entry is so that I can revert the changes?

Pejole2165 said:

One sec, ill test on my system and see what changes are made.
Took longer than I thought, search the registry for AutorunsDisabled don't match whole string. Just delete the AutorunsDisabled Reg_DWord value, the complete line not just the value, this should re enable the disabled service/ driver. Keep doing the search using F3 to find all of those entries.

You beat me to it, I did the same. I'm trying to boot off of a WinPE environment with a registry editor now and will do that. I'm sure this will revert the changes. I'll post back in a few.

EDIT: Question though. If autoruns lists those drivers with a check, does that mean the system loads then during boot time? Or does it mean that the drivers are simply installed but not necessarily being used?