How to install nvidia driver for rtx3080 on windows 1709?

[StefanM]

Are there any INFs in the folder that are unrelated and should not be deleted?

Folder display.driver contains only INFs for display
The other INFs are stored in corresponding folders - HDAUDIO/nvhda.inf etc.

An exception would be a driver downloaded from Windows update where almost everything is in the same folder. But that's another and more complex story...

 

[hans_glans]

Great, thanks!

 

[W1zzard]

But, seriously - how does this differ from the "Add hardware support" expert tweak?

Add hardware takes an existing section for a specific device, changes the device id and name and adds it as new, additional section. What you want here is to remove the OS requirement of an existing section

 

[hans_glans]

Ok, I did it via Teamviewer on a friend's 3060. I installed 1709.

Default driver:

Stock installation attempt:

Edited INFs:
(please check attached INF files (default and edited) @StefanM - it was different numbers (14310, 16299, 17134) and I removed them all according to your instructions. I also deleted all other INF files):
There was a driver signing warning, I proceeded with "Continue anyway". Success?

BUT - I can't open nvidia control panel, no additional display driver functionality is added and device manager reports error code 43:

and reports this when trying to install the driver directly through device manager:

So, it seems like it doesn't work.
Any further help is appreciated.

@W1zzard @StefanM Do you have any further ideas?

 

[W1zzard]

Just to make sure you didn't install any older driver version, make sure to select "clean install" in the installer options

There was a driver signing warning, I proceeded with "Continue anyway".

This is expected and due to the way NVCleanstall self-signs the driver files, so they don't lead back to Microsoft's signing authority

 

[hans_glans]

I did select "clean install".

It seems like error 43 is expected at first and the additional block can be solved, too.
It should be equivalent to getting a GTX 1080 working on Windows 10 TH1 (10240).
Unfortunately I don't know the specifics, only that it works.

Any ideas?

 

[StefanM]

I did select "clean install".

It seems like error 43 is expected at first and the additional block can be solved, too.
It should be equivalent to getting a GTX 1080 working on Windows 10 TH1 (10240).
Unfortunately I don't know the specifics, only that it works.

Any ideas?

The most comprehensive guide for code 43 is here:

Fix Error NVIDIA Code 43: Windows has stopped this device because it has reported problems

Are you also getting the error NVIDIA Code 43? Is your graphics card causing problems with your computer? You are not the only one. This error has been

thegeekpage.com

 

[hans_glans]

@StefanM How would I debug the nvlddmkm.sys to find a specific offset and what it corresponds to?

@W1zzard Can I just unpack nvlddmkm.sys from nvlddmkm.sy_ , modify it and rename it to nvlddmkm.sy_ and then have Nvcleanstall resign the modified driver?
Or do I have to repack nvlddmkm.sys to nvlddmkm.sy_ some other way?

Is is required at any time to disable integrity checks or use testsigning mode with this methodology?

By the way, the other expert tweaks (disable HDCP) don't seem to trigger resigning. And because the Disable Telemetry expert tweak is still experimental, I would generally prefer the option to resign without any further tweaks. Is that possible?

@W1zzard apparently only nv_disp.cat gets resigned. Can you also let nvlddmkm.sy_ (or the nvlddmkm.sys it includes) resign. Or how about an expert tweak that directly lets you replace nvlddmkm.sys

 

[W1zzard]

Can I just unpack nvlddmkm.sys from nvlddmkm.sy_

Yes, using expand

modify it and rename it to nvlddmkm.sy_

I vaguely remember you can just replace it with the .sys file and the installer will still find it. Delete the .sy_ of course

Nvcleanstall resign the modified driver?

NVCleanstall won't resign the .sys, so you might run into driver signature enforcement problems.
The problem is that as far as I know kernel mode driver signing requires a real EV signature and MS's counter-signing, a self-signed cert won't work, like it does for the .cat file signing

 

[hans_glans]

Thanks for the great replies!

Yes, using expand

Nice, even seems to work with 7zip.

I vaguely remember you can just replace it with the .sys file and the installer will still find it. Delete the .sy_ of course

Can't fully confirm but both bare .sys and just renaming it to .sy_ seems to work.

Regarding priority of error reporting:
If the .sys file modification is not working AND the driver is unsigned, will device manager just still report error 52 or would it fail before that because of the broken modification?
Or in other words, can I know from error 52 that it's JUST a signing issue or could the modification be broken, too?

NVCleanstall won't resign the .sys, so you might run into driver signature enforcement problems.
The problem is that as far as I know kernel mode driver signing requires a real EV signature and MS's counter-signing, a self-signed cert won't work, like it does for the .cat file signing

Yes, so far it results in error 52. This is so unfortunate. Any way around it?
I found these hints but don't know how viable they are on 1709:
A method to self-sign https://www.techpowerup.com/forums/threads/how-to-sign-your-own-modded-drivers.279469/
A tool to self-sign https://www.majorgeeks.com/files/details/driver_signature_enforcement_overrider.html
I assume these should fail because it's a kernel driver?
Disabling driver signature enforcement https://www.majorgeeks.com/content/page/how_to_disable_driver_signature_enforcement.html
Signing custom kernel drivers https://github.com/HyperSine/Windows10-CustomKernelSigners and https://www.geoffchappell.com/notes/windows/license/customkernelsigners.htm
Would this work at all and if so, be compatible with anti-cheat?

 

[bruhmoment1]

Harika cevaplar için teşekkürler!


Güzel, hatta 7zip ile çalışıyor gibi görünüyor.


Tam olarak onaylayamıyorum, ancak hem çıplak .sys hem de sadece .sy_ olarak yeniden adlandırmak işe yarıyor gibi görünüyor.

Hata raporlamanın önceliği ile ilgili olarak:
.sys dosyası değişikliği çalışmıyorsa VE sürücü imzasızsa, aygıt yöneticisi yine de 52 numaralı hatayı bildirecek mi yoksa bozuk değişiklik nedeniyle bundan önce başarısız mı olacak?
Veya başka bir deyişle, 52 numaralı hatadan SADECE bir imzalama sorunu olduğunu veya değişikliğin de bozulabileceğini bilebilir miyim?


Evet, şimdiye kadar 52 hatasıyla sonuçlanıyor. Bu çok talihsiz bir durum. Etrafında herhangi bir yol var mı?
Bu ipuçlarını buldum ama 1709'da ne kadar uygun olduklarını bilmiyorum:
Kendi kendine imzalama yöntemi https://www.techpowerup.com/forums/threads/how-to-sign-your-own-modded-drivers.279469/
https://www.majorgeeks.com/files/details/driver_signature_enforcement_overrider.html kendi kendine imza atmak için bir araç
Bunların bir çekirdek sürücüsü olduğu için başarısız olması gerektiğini varsayıyorum?
Sürücü imza zorunluluğunu devre dışı bırakma https://www.majorgeeks.com/content/page/how_to_disable_driver_signature_enforcement.html
Özel çekirdek sürücülerini imzalama https://github.com/HyperSineWindows10-CustomKernelSigners ve https://www.geoffchappell.com/notes/windows/license/customkernelsigners.htm
Bu hiç işe yarar mı ve eğer öyleyse, hile karşıtı ile uyumlu olabilir mi?

Did u solve it? Also memory size 0 mb its a some big problem ı think its hardware problem because me to have same error code 43

 

[hans_glans]

I did but it needs some more testing and answers from @W1zzard regarding the signing.

 

[dbut3]

thanks for this thread, driver install completed. looks like exactly the hack i needed to put off finally repairing this copy of windows just a little while longer (it blue screens when i try to update from 1709)

 

[W1zzard]

.sys file modification

What did you change in the .sys ?

 

[hans_glans]

What did you change in the .sys ?

Replaced the hex value of the corresponding winver with another one.

 

[W1zzard]

Nice idea. You basically searched for 17098 and replaced it with a different version?

 

[oobymach]

Control panel won't open because earlier versions of 10 are Not DCH friendly, I just went through this myself. Either you use a Non DCH version of the driver (472.84 is the latest non dch driver) or you upgrade to the latest version of windows and use the latest DCH drivers.

You can get Non DCH drivers from here.

Advanced Driver Search official NVIDIA drivers

Advanced Driver Search official NVIDIA drivers

www.nvidia.com

And you can get the latest version of win 10 from microsoft by following method 2 here.

How to download the latest Windows 10 ISO from Microsoft

When a new version of Windows 10 is released, Microsoft also releases new ISO disk images of the operating system to perform clean installs or create a bootable recovery environment. This article provides two ways you can download the latest Windows 10 ISO images from Microsoft.

www.bleepingcomputer.com

And then use RUFUS to turn it into bootable media. All you need is a 16gb usb memory stick. Install with upgrade option and it should keep all your files and settings.

 

[hans_glans]

@oobymach Your reply doesn't have to do much with the topic because it's about getting any driver installed with Ampere on 1709. There are plenty of non DCH drivers supported by Ampere in general.
There's also an easy workaround that allows using legacy nvcp on DCH: https://www.techpowerup.com/forums/...-dch-microsoft-store-only.288731/post-4710210

Nice idea. You basically searched for 17098 and replaced it with a different version?

This works for example:

So does this:

 

[oobymach]

@oobymach Your reply doesn't have to do much with the topic because it's about getting any driver installed with Ampere on 1709. There are plenty of non DCH drivers supported by Ampere in general.
There's also an easy workaround that allows using legacy nvcp on DCH: https://www.techpowerup.com/forums/...-dch-microsoft-store-only.288731/post-4710210

You were having issue loading Nvidia Control Panel,

BUT - I can't open nvidia control panel, no additional display driver functionality is added and device manager reports error code 43:

and this guy

thanks for this thread, driver install completed. looks like exactly the hack i needed to put off finally repairing this copy of windows just a little while longer (it blue screens when i try to update from 1709)

had the issue with upgrading windows which it seems like the topic is also about so I provided a way to upgrade windows and an explanation that you can't use Nvidia Control Panel using a DCH version of the driver on an old version of the OS. So yes, I am on topic, and killing it.

 

[hans_glans]

It's both me , but in this matter nvcp not loading was solely because of the driver not being successfully installed (error 43).
For 1709, I believe that even the newest DCH driver works and nvcp is usable with the link I shared.

@W1zzard I noticed that signing also alters the "hex content" of the .sys
Does this mean in return that simply changing hex values of the file could make it signed?

Do you have any idea how to self-sign it (the method I used is not sustainable)?

Automating the hex tweaking and somehow signing the sys (or achieving the same outcome differently) would be the cherry on top for NVCleanstall!

 

[oobymach]

Can only speak for me, but in this matter nvcp not loading was solely because of the driver not being successfully installed (error 43).
For 1709, I believe that even the newest DCH driver works and nvcp is usable with the link I shared.

I had 1903 previously and was unable to update to latest version via the windows update and also ran into the issue after installing the DCH driver I couldn't open Nvidia Control Panel either. The only workaround was to install the newest version of windows from a usb key.

 

[W1zzard]

I noticed that signing also alters the "hex content" of the .sys

yeah the signature is appended near the end of the file

Does this mean in return that simply changing hex values of the file could make it signed?

In theory yes, in practice no. look up hash collision

Do you have any idea how to self-sign it (the method I used is not sustainable)?

How did you sign it?

Automating the hex tweaking and somehow signing the sys (or achieving the same outcome differently) would be the cherry on top for NVCleanstall!

Somehow I think there's not a lot of people on older Win 10, most people were already forced to upgrade by the various nag mechanisms everywhere

 

[hans_glans]

yeah the signature is appended near the end of the file

I also saw differences right at the start. But doesn't really matter because of hash collision then, I guess.

How did you sign it?

Testsigning mode and some other methods.
Like this, it's not viable at all for gaming unfortunately. (Testsigning mode not tolerated by anti-cheat et cetera, workarounds for that too but I'd rather treat the cause).
How would you do it?

Somehow I think there's not a lot of people on older Win 10, most people were already forced to upgrade by the various nag mechanisms everywhere

While I looked into this, I encountered many with the same issue. Of course it's relatively few but I'd imagine such a workaround would only turn out to be more useful over time, with Lovelace and W11 and who knows what dawns.

In theory yes, in practice no. look up hash collision

So definitely no chance to restore an original signature from hex?

 

[W1zzard]

So definitely no chance to restore an original signature from hex?

Not in our lifetimes

How would you do it?

NVCleanstall generates and installs a signing certificate into the trusted store of the machine and uses that to sign the CAT file. As mentioned before I'm not sure if that will work for a .sys driver to load

 

[hans_glans]

NVCleanstall generates and installs a signing certificate into the trusted store of the machine and uses that to sign the CAT file. As mentioned before I'm not sure if that will work for a .sys driver to load

How can I try?