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

[Test Build] Fix for Driver Signing on Windows 11 24H2

W1zzard

W1zzard

Administrator
Staff member
Joined
May 14, 2004
Messages
28,775 (3.74/day)
System Specs
Processor Ryzen 7 5700X
Memory 48 GB
Video Card(s) RTX 4080
Storage 2x HDD RAID 1, 3x M.2 NVMe
Display(s) 30" 2560x1600 + 19" 1280x1024
Software Windows 10 64-bit
Last edited:
biel780 said:
Sadly it didn't work for me. I disabled telemetry, enable only HD audio via HDMI (disabled all the rest) and enabled experimental tweaks
Click to expand...
Same error? You did enable "rebuild driver signature", right?
 
Hello W1zzard. I'll bite!

Windows 11 24H2 26100.2161
Clean install using DDU safe mode
nVidia Driver v566.03

I selected Easy Anti-Cheat compatible and a few other options that required driver signing as well as auto-selecting the prompt to install the driver.

This worked fine, I restarted the computer using the shutdown option and when it restarted, then I fired up CyberPunk and played for a few minutes.

No problems and survived another reboot without issue.

This version works fine...

A quick aside... I notice that the new driver created with this version of NVCleanstall is 2MB smaller than the one created by the previous version of Cleanstall... The old driver was obviously not made with anything that made Cleanstall use driver signing, so that might be something to do with it.
 
Last edited:
Works great.
 
W1zzard said:
Same error? You did enable "rebuild driver signature", right?
Click to expand...
Yes, i did. I may pass DDU to see if it work
Here a image of my settings and error. I wonder is it the HD Audio Drivers?
 

Attachments

  • Untitled.png
    Untitled.png
    64.5 KB · Views: 326
  • Untitled2.png
    Untitled2.png
    62 KB · Views: 332
Last edited:
Actually forget my feedback. I pass DDU and tried to install the stock drivers. Same error.
I have no idea whats wrong with my system, but it's not the new nvcleaninstall

Edit:
I found the problem, for some reason my C:\ drive wasn't set as TrustedInstaller as it's owner, manage to restore and the Driver installed perfectly (the nvcleaninstall one).
Thanks for your work and sorry for my wrong previous feedback
 
Last edited:
I was able to use the test build successfully on my system to reinstall 566.03 (cleanly).

My options:

Screenshot 2024-11-07 005824.png
Screenshot 2024-11-07 005915.png
Screenshot 2024-11-07 005922.png


No issues thus far.

Windows 11 24H2 (Build 26100.2152)
 
Awesome, thanks everyone for the testing. Looks like it's working!

biel780 said:
I found the problem, for some reason my C:\ drive wasn't set as TrustedInstaller as it's owner, manage to restore and the Driver installed perfectly (the nvcleaninstall one).
Click to expand...
and the regular NVIDIA installer works with that configuration?
 
@W1zzard given that you are reluctant to open-source your utilities, ever consider doing technical writeups to explain the issues you come across and how you solved them?
 
Had a chance to test, no issues. Installed fine on my test system.

biel780 said:
I found the problem, for some reason my C:\ drive wasn't set as TrustedInstaller as it's owner
Click to expand...
W1zzard said:
and the regular NVIDIA installer works with that configuration?
Click to expand...
I can't see that causing a problem either way, but then again I haven't tried that. Never had a reason. It does make me wonder though..
 
Assimilator said:
@W1zzard given that you are reluctant to open-source your utilities, ever consider doing technical writeups to explain the issues you come across and how you solved them?
Click to expand...
24H2 will not work without a SHA256 sig in the cat file. I doubt this information is useful to anyone though and it's fairly trivial to figure out for anyone concerned with it.
 
W1zzard said:
24H2 will not work without a SHA256 sig in the cat file. I doubt this information is useful to anyone though and it's fairly trivial to figure out for anyone concerned with it.
Click to expand...
I can endorse that :) , since 24H2 dev insider came out months & months ago... all my modded drivers needed SHA256 sig in the cat file, so I came prepared way early [Since I'm using 24H2 dev insider] & once Windows RP Insider release got to the public and then the eventual actual general release of 24H2, everything was smooth sailing for me ;)

Congratulations for the new tool! Everything related to removal of telemetry & signing the driver works! :respect:
 
W1zzard said:
Awesome, thanks everyone for the testing. Looks like it's working!


and the regular NVIDIA installer works with that configuration?
Click to expand...
It didn't before i found the issue too, but after i set the right owner to C drive, i haven't test the original, came straight to the one with your tool

lexluthermiester​

Click to expand...
I don't understand either to be honest, but than again, i don't understand how the driver works in a lower level
 
biel780 said:
It didn't before i found the issue too, but after i set the right owner to C drive, i haven't test the original, came straight to the one with your tool
Click to expand...
Ok.. I was wondering if it's worth adding some kind of check for that to NVCleanstall, but if it affects the official installer, too, then I don't think this logic should be added
 
Works great!

- Windows: 11 Pro x64
- Version: 24H2
- OS Build: 26100.2161
- GPU: RTX 2070 Super 8GB
 

Attachments

  • Screenshot 2024-11-07 171917.png
    Screenshot 2024-11-07 171917.png
    38.1 KB · Views: 173
lexluthermiester said:
Better safe than sorry. A check for it would seem wise.
Click to expand...

Agree with this, better to know before the user even starts building the modified driver. Could also post a message to have them install the stock nVidia package to see if it even installs with that.

Could even link to a forum post (in here or another forum like 11F) with instruction on how to change the owner of the drive to allow driver installer.

After all, a (very few, admittedly) might try this utility specifically because they cannot install the stock package in the first place, and hope that this one may get them up to speed.
 
W1zzard said:
Ok.. I was wondering if it's worth adding some kind of check for that to NVCleanstall, but if it affects the official installer, too, then I don't think this logic should be added
Click to expand...
Yea, i think not as it's a "stock issue"
 
Thank You, that worked for me.
I could build a package for the latest 566.03 Notebook Driver and added the Hardware Id for my GTX 980m

After that I could install that Package under Widows 11 24H2 (Build 26100.2033) IoT Enterprise LTSC

(I already posted that in the other thread, but I think here is the better place)
 

Attachments

  • IoT.jpg
    IoT.jpg
    58.4 KB · Views: 111
  • nvidia.jpg
    nvidia.jpg
    69.1 KB · Views: 120
It worked perfectly here.

- Windows: 11 Pro x64
- Version: 24H2
- OS Build: 26100.2161
- GPU: RTX 3060 12GB
 
You must log in or register to reply here.
Back
Top