How to install nvidia driver for rtx3080 on windows 1709?

[W1zzard]

Google around how to generate a self-signed certificate, make sure you put it into Start -> Manage user certificates ->Trusted Root Certification Authorities -> Certificates

If you've been using NVCleanstall you'll see its certificates in that same location. For security, NVCleanstall throws away the private key once it's signed the CAT file during installation, so bad people can't use it to sign stuff that's valid on the current machine.

 

[leightonbmw]

Can anyone please do it for me on teamviewers ive been stuck for 2hours
My discord is: LL#0101
someone please help me please.

Remove the version check in INF of the NVIDIA driver:

[Manufacturer]
%NVIDIA_A% = NVIDIA_Devices,NTamd64.10.0...14393,NTamd64.10.0...17098

[NVIDIA_Devices.NTamd64.10.0...14393]

[NVIDIA_Devices.NTamd64.10.0...17098]

Then in NVCleanstall select any expert tweak to trigger rebuilding signature.

Bear in mind that DirectX12 Ultimate is not available in old Windows 10 versions.

can u please help me on teamviewer I have been stuck for hours man
my discord is: LL#0101

 

[hans_glans]

If you intend to game with that modified driver, self-signing methods without an EV certificate are not viable.
You should find everything else in here but I can recall the essential steps briefly:
1. Pick the driver in Nvcleanstall, proceed to the Optional tweaks section and keep it open
2. Go into the Nvcleanstall temp folder/display driver and delete all INFs except for nv_dispi and the other 2 essential ones
3. Remove the Windows version number from the nv_dispi file
4. Unpack the nvlddmkm.sy_ and modify the .sys in HxD or IDA or WinDbg by finding the hex value of your winver and replacing it (for Ampere on 1709 it's 00 7C 3F 00 replaced with 00 0F 3A 00 and 00 AD 42 00 with 00 AB 3F 00 (among other options))
5. Rename the file to nvlddmkm.sy_ (keeping it as .sys could work, too)
6. In Nvcleanstall tick the "second" Disable Telemetry to trigger resigning (should pop up ticked then) and build the package (Note that this does not resign the .sy_)
7. Run testsigning mode on and or DSE off or somehow sign the .sy_ if you want to game

____

@W1zzard I noticed that sometimes Nvcleanstall downloads are incredibly slow, stall or don't proceed at all.
I also sometimes have to activate the KeyIso service to resign or an error message pops up (which then quits Nvcleanstall and doesn't clear the temp folder).

 

[W1zzard]

Just tested to sign the .sys with NVCleanstall's signing certificate (which gets put intro Trusted Root). Not enough, it still won't load the driver.

KeyIso

There will be a warning in next version that will alert you if KeyIso isn't running + "Retry", "Cancel" buttons

 

[hans_glans]

Just tested to sign the .sys with NVCleanstall's signing certificate (which gets put intro Trusted Root). Not enough, it still won't load the driver.

If you make it work somehow (or can circumvent the OS restriction without losing the signature in a different way), I'd be eternally grateful

 

[W1zzard]

If you make it work somehow (or can circumvent the OS restriction without losing the signature in a different way), I'd be eternally grateful

Can't even think of a way how to approach this

 

[Minxie]

Just update your damn OS, why are you even on 1709 anymore

People who neglect updates are the anti-vaxxers of the IT world

 

[hans_glans]

I have nothing against newer Windows versions, I multiboot 2009 and 21H1 and whatever. But I have my reasons to partly maintain 1709. Question is why you would bother.

 

[qubit]

Why don't you just upgrade to 21H2? I can't see any benefit to staying with an old, unsupported version of Windows. Look at the trouble you're having just installing a simple driver.

 

[hans_glans]

Why don't you just upgrade to 21H2? I can't see any benefit to staying with an old, unsupported version of Windows. Look at the trouble you're having just installing a simple driver.

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.

 

[qubit]

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.

Apologies, my comment was intentended for the OP @Wasaki (I would still like to know ) but thanks for the clarification. I can see the confusion coming right after yours, which I hadn't seen. I should have perhaps tagged the OP.

I know what you mean about maintaining outdated systems - what a pita.

 

[leightonbmw]

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.

same..

The only reason I comment on useless contributions like this again is to hopefully make you see how useless they are.
This is about signing a modified kernel driver (1 hex string) to make it work on an outdated Windows version that I have to maintain - and not about my personal preference of Windows versions.
Again, I multiboot many Windows versions for different purposes and have no issue with the recent versions.
The driver works, the limitations is unnecessary and there are more scenarios where solving this is useful.

I am still stuck can u please add me on discord.
LL#0101
I need help via teamviewer please.

 

[ill]

@hans_glans why you stop

 

[hans_glans]

I stop because it works for me.
Still would love a way to legitimately sign the driver so you can play games with anti-cheat.
1709 is being less and less supported by games anyway but the method should be handy for future circumvention of nvidia architecture winver checks in general.

I'm also thinking about upgrading to Lovelace at some point and using newer DCH drivers on 1709 (or other outdated winvers).
So if someone wants to try my method for that, let me know.

 

[furameru]

4. Unpack the nvlddmkm.sy_ and modify the .sys in HxD or IDA or WinDbg by finding the hex value of your winver and replacing it (for Ampere on 1709 it's 00 7C 3F 00 replaced with 00 0F 3A 00 and 00 AD 42 00 with 00 AB 3F 00 (among other options))

hey @hans_glans , do you know by any chance what would be the corresponding hex values for Windows 10 build 10586 or build 14310? I've got a RTX 3060 Laptop GPU myself and would love to get one of these versions of Windows running on my laptop. sadly, I've never figured those hex values out, and the only guy which had (and successfully got RTX cards working under Windows 10 build 14310/14393 or older) just refuses to share it online (even when offered to get paid for it).
could you please help me with this? I'm currently struggling to find those hex values for 472.12-notebook-win10-win11-64bit-international-whql.exe.

 

[hans_glans]

If you intend to game with that modified driver, self-signing methods without an EV certificate are not viable.
You should find everything else in here but I can recall the essential steps briefly:
1. Pick the driver in Nvcleanstall, proceed to the Optional tweaks section and keep it open
2. Go into the Nvcleanstall temp folder/display driver and delete all INFs except for nv_dispi and the other 2 essential ones
3. Remove the Windows version number from the nv_dispi file
4. Unpack the nvlddmkm.sy_ and modify the .sys in HxD or IDA or WinDbg by finding the hex value of your winver and replacing it (for Ampere on 1709 it's 00 7C 3F 00 replaced with 00 0F 3A 00 and 00 AD 42 00 with 00 AB 3F 00 (among other options))
5. Rename the file to nvlddmkm.sy_ (keeping it as .sys could work, too)
6. In Nvcleanstall tick the "second" Disable Telemetry to trigger resigning (should pop up ticked then) and build the package (Note that this does not resign the .sy_)
7. Run testsigning mode on and or DSE off or somehow sign the .sy_ if you want to game

____

@W1zzard I noticed that sometimes Nvcleanstall downloads are incredibly slow, stall or don't proceed at all.
I also sometimes have to activate the KeyIso service to resign or an error message pops up (which then quits Nvcleanstall and doesn't clear the temp folder).

@W1zzard @StefanM
I'm retrying this with RTX 4070 instead of 3070 on 1709 but no success.

The earlierst driver supporting the 4070 is DCH only already (531.41). This seems to change some file structures. (the nv_desktop inf file is missing now etc.)

The same hex tweaks don't work anymore. This combination worked for the 3070 on 1709:
1. 00 7C 3F 00 (16252) replaced with 00 0F 3A 00 (14863) and
2. 00 AD 42 00 (17069) with 00 AB 3F 00 (16299))
and I'm not experienced with WinDbg to find the new hex values to modify via debugging.
This is especially difficult because "1803" being the minimum Ampere/Lovelace winver requirement could mean beta builds from 17069 to 17763. So this would be a lot of trial and error without proper debugging.

Any ideas what I'd have to adjust for the 4070 (trying it with 531.61)?
How would I debug the .sys file to nail down the winversions to change?

 

[hans_glans]

@Space Lynx If you'd have read the thread, maybe you wouldn't waste the time of those who are actually invested in the topic by reading your useless comment that contributes absolutely nothing.

 

[StefanM]

How would I debug the .sys file to nail down the winversions to change?

Try IDA freeware version
The main problem is that nobody provides driver symbols for kernel drivers - neither Microsoft nor AMD, Intel or NVIDIA

 

[StefanM]

One thing i forgot to mention: using a disassembler etc. is easier if you disable ASlR

Disable-ASLR/Aslr.bat at main · TheEyeOfCyber/Disable-ASLR

ASLR DISABLE FOR MICROSOFT WINDOWS. Contribute to TheEyeOfCyber/Disable-ASLR development by creating an account on GitHub.

github.com

Took me a while at the time to figure out that Microsoft had introduced that

 

[phipsi]

I would like to play the Gears of War Ultimate Edition with high framerates on my system:
MSI RTX 3060 Ti
MSI Pro Z690-A.

Windows 1709 gave me a massive improvement in FPS on my GTX 1060 6GB compared to 22H2 (55 fps vs 25 fps).

Followed all the steps in this thread and even selected Nvidia Driver 472.12 as someone mentioned to be working, but sometime the installer terminates with an error "Nvidia installer failed". I am past the error regarding "Not compatible with this version of Windows" though. Any hints?

 

[hans_glans]

While 1709's frametimes are superior to all following versions in my testing as well, at least in the games that still run on it, the improvement you're seeing is beyond any size that would be down to Windows version. Something is wrong with your 22H2 setup. 1709 is simply impractical to use now and the performance gain is not worth it over all its limitations.

 

[phipsi]

While 1709's frametimes are superior to all following versions in my testing as well, at least in the games that still run on it, the improvement you're seeing is beyond any size that would be down to Windows version. Something is wrong with your 22H2 setup. 1709 is simply impractical to use now and the performance gain is not worth it over all its limitations.

Don't think there is anything wrong with my setup, did a clean OS install.
With Gears Of War Ultimate Edition, I found out it is actually a specific update, namely KB4493440 that causes the issues. I can definitely reproduce it (still own my GTX 1060 System) by letting Windows install this update, starting the game, remove the update, start game again and the difference I see in FPS is huge. All of this on 1709, no 22H2 involved but it's basically the same as with 1709 and KB4493440 installed. I agree that it's unbelievable that a windows update results in such performance differences but I can prove it at least for this game (working on a video). So my idea is to run 1709 on my second NVMe to play it but unfortunately the driver doesn't install on Ampere.

 

[St1cky]

Still working. 566.36