• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

[Feature Request] Add option to switch between 1.7.0 and 1.8.0 driver signing and add background checking for driver updates with Hotfix included.

Joined
Feb 7, 2021
Messages
13 (0.01/day)
Hello
Like in topic.
Version 1.7.0 signed drivers with proper signature, 1.8.0 signs drivers, but Windows outputs dialog about untrusted driver vendor (Screenshot below).

win10-install-unsigned-drivers-featured-800x400.jpg

Also can you add checking for drivers update both WHQL and Hotfix?
 
but Windows outputs dialog about untrusted driver vendor
does this cause any problems?

Also can you add checking for drivers update both WHQL and Hotfix?
for now no plans to add hotfixes, nvidia releases whqls pretty quickly, so shouldnt be a big deal, you can always install the manually (3rd option on start screen)
 
does this cause any problems?


for now no plans to add hotfixes, nvidia releases whqls pretty quickly, so shouldnt be a big deal, you can always install the manually (3rd option on start screen)
1. It doesn't, just my personal preference to install property signed driver.
2. That's how I am doing this now; notification on desktop would be nice however.
 
I've also wondered why it's no longer able to sign properly. Not a huge deal, but it has interrupted installs I've left running, only to come back and find it halted because of the non-signature.

Out of curiosity, how come NVcleanstall isn't able to sign the drivers now with 1.8.0? What changed?
 
  • Like
Reactions: vgm
What changed?
I changed the signing method to be MUCH faster, but apparently lost some signing magic on the way. Will look into this some more, once I have more time

Besides the "unsigned driver" alert box during installation, is anything else affected?
 
I think I found the problem, will do more testing after 6700 XT reviews
 
So the new code gives you:
jflgu9wmui.jpg


The old code gives:
o4jw1pgmsg.jpg


Other than the color, why bother?

Edit: yay, I think I figured it out, please test this build. there should be no popups or warnings and the signing process should complete in a few seconds
 

Attachments

Last edited:
yay, I think I figured it out, please test this build. there should be no popups or warnings and the signing process should complete in a few seconds
I can't test this now, but I will try this when I leave hospital
 
Edit: yay, I think I figured it out, please test this build. there should be no popups or warnings and the signing process should complete in a few seconds

Works fine here.
I found another bug, i open a new topic for that...
 
Back
Top