any way to force install rtx cards on win10 1607 build? (or any pre 1709 win10 build)

one solution is download quadro driver for windows server 2016 (is same build win10 LTSB) build 14393

and mod this driver add your strings rtx 2060 and install likely works

don't forget to enable driver mode using this command administrative dos prompt first


bcdedit /set testsigning on

(appears written test mode below right)

restart computer, and install modded driver


let us know if this worked out

 

install won't work.

 

Hi, man, I have Windows 10 LTSB 2016 and a RTX 2070, can you explain me how to add "the strings" to the driver or how to mod it? Thanks in advance!

 

No he can't, because it doesn't work.

 

test this

1- type dos (administrative)
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS

bcdedit -set TESTSIGNING ON


2- restart computer

verify if work if show test mode show in desktop (if ok) install modift driver




3- download driver modded (decompress and install normaly using setup)
https://www98.zippyshare.com/v/BKrVu26c/file.html

 

You cannot modify the driver to work on Windows below the supported build.

 

quadro RTX support windows server 2016 and 2019 i modify this driver for install on LTSB is same build for server 2016 build 14393
in theory should work this way, I didn't test because I don't have an geforce rtx here

 

The update is FREE.
WHY NOT UPDATE TO WINDOWS 10 build 1909?

 

because he loses badly in games that use dx12

 

want to grow carrots with bean seeds?

Have you ever seen an RTX 2080 physically and have tested it on both windows 10 build (1607 and 1903) or googling around only....... ....
in my opinion, when buying a computer component..... ALWAYS do check minimum requirements....
-------------------------
here's the specs of RTX 2080 : https://www.nvidia.com/content/geforce-gtx/GEFORCE_RTX_2080_User_Guide.pdf
-------------------------
well, i estimate you will not open the link, so check this:

APRIL 2018 Update = build 1803
​

https://i.**********/25T2rSP1/GEFORCE-RTX-2080-User-Guide.jpg

 

explain this? because nvidia quadro RTX is basically same thing as geforce rtx and it supports windows 1607?




all gpus using same graphics processor TU102

 

You're also aware it is quite trivial to add firmware or hardware that makes the fact they may use the same die, irrelevant and drivers incompatible. Just as Quadro hardware features exist on the consumer cards but cannot be enabled via driver hack due to checks. I'm not denigrating your efforts. Merely pointing out your argument doesn't mean it 'should work' or will work.

 

Good Question!

@maur0 Windows Server, version 1803 (based on Windows 10 April 2018 Update) is the second Semi-Annual Channel release of Windows Server. It is also the final version to be branched off the Server 2016 codebase. Windows Server 2016 had two Semi-Annual Channel releases. 1709 and 1803.

Regarding Windows Server 2016 & support on Quadro RTX 8000/6000/5000/4000 products,
USB-C support requires Windows 10 April 2018 Update (Version 1803, “Redstone 4”) or later. Driver R410 U5 (412.16)

Finally and most importantly - the underpinning of the card's themselves the DXR hardware acceleration will not function in a pre-1803 environment. Here's a screenshot of the release notes for NVIDIA's earliest RTX Quadro Server 2016 driver.



Note: There's also a lot of confusion between the distinction of LTSC and SAC
If I got this right by the mind um... LTSC 2016 / 2019 and so on
SAC - Server 1607, 1709? and 1803 1809 etc

 

relax

I'm using 1909 at the moment and its working fine, just wanted to test 1607 when I made this post, because from what I understood, it always runs games in exclusive fullscreen mode as there is no support for "fullscreen optimizations" or the new presentation mode in newer builds,


but after a lot of testing 1709/1809/1903/1909 etc is working fine and the new presentation mode is not the same as borderless windowed, so even in those games where I can't force exclusive fullscreen mode in the newer windows builds, it doesn't have any negative effect for me atleast in terms of performance or input delay.. from what I can tell atleast!


so 1909 is alright and that is what i'm using currently, i'm also not playing any DX12 games so can't say anything about that on 1909 vs 1607 in dx12 games, mostly playing Fortnite in dx11 and fifa 20 in dx11 mode, cheers

 

I'd like to install Windows 10 vers. 1607 as well, with the RTX 2080 Ti, for one single reason :
https://hub.displaycal.net/forums/topic/how-to-enable-dithering-on-nvidia-geforce-with-windows-os/
Is not working with newer Windows 10 versions

 

dithering works just fine on 2004 and 451.22

 

1809 seems to be as good or "fast" at 1607 or if not, a bit faster. Without a doubt, the best Windows versions seem to be 1607, 1709 and 1809 so far. And 1809 is great because it does support RTX.

 

Install Windows 10 1809 Pro or LTSC and forget about any problems; it combines the stability of old Windows versions with RTX support. Newer versions of Windows seem a big scuffed (1903 at least, no idea about 1909) but at this point, I'd recommend to you 1809.

As for FSO, you can disable them via the Registry, so I wouldn't worry about that, good luck!

 

Yes and folks please recall if you are on Ryzen you negate CPPC(2) and or Intel's later implementation for it if you move back to 1607. Just ... lunacy

 

Intel's SpeedShift (hardware P states) has been around since SkyLake (2015). I am not aware if the OS driver/governor requirements of it changed since then. (Unless you mean the new TurboBoost version with the "favored core" concept on later >8core server and HEDT platforms). SpeedShif is clearly superior to SpeedStep and should not cause any problems.
PCI-E power saving (L states) can cause a lot more issues (incredible how that could still be enabled by default on so many platforms and in most OS drivers).

Back to the topic: testsigning still requires a (test) signature. There was a tool floating around on the web which makes it fairly easy to generate test signatures locally and sign your modded inf files for yourself before forced-install (after you used bcdedit). But I didn't use it for something like 5+ years, so I am not sure if it still works. And obviously there is no guarantee the driver will work once installed (and some explained it earlier, the driver has hard-coded compiled-in checks for whitelisted and/or blacklisted functionality on certain hardware). SecureBoot might needs to be disabled as well (depending on your UEFI version and how Win10 was istalled) which might not be possible without disabling EFI boot alltogether (depending on what your UEFI Setup allows).

BTW, I am very skeptic about that 1609-1903 comparison above. But now you can also jump to 20H1 or even 20H2 (same base install and same CU update packages as 20H1 + a simple "feature enablement package", so same as 1903 and 1909, a very minor update which brings hidden beta features into light).