Wednesday, August 21st 2019

NVIDIA Fixes GeForce 436.02 Installer, No Longer Forces GeForce Experience Onto You

NVIDIA yesterday posted its much publicized GeForce 436.02 WHQL Gamescom Special graphics drivers that brought about performance improvements across a spectrum of games, and added new features such as low-latency input (akin to AMD Radeon Anti-Lag), and beat Intel to Integer Upscaling. The installer that brought all these goodies to you, however, was buggy, as NVIDIA admitted. It originally installed GeForce Experience regardless of obtaining GDPR-mandated user-consent, and made deselecting the application in the "Custom Install" components list impossible.

Later in the evening, NVIDIA temporarily pulled the driver from the Downloads section of its website, and hours later, re-uploaded the drivers with an installer that fixes this bug. The driver version number remains the same, all that's changed is an "-rp" suffix in the installer binary's file-name (eg: "436.02-desktop-win10-64bit-international-whql-rp.exe"). We've added the updated files to our downloads section.

DOWNLOAD: NVIDIA GeForce 436.02 WHQL (Fixed)
Add your own comment

24 Comments on NVIDIA Fixes GeForce 436.02 Installer, No Longer Forces GeForce Experience Onto You

#1
Prima.Vera
The testing department for the drivers must be made from monkeys....
Posted on Reply
#2
lynx29
Prima.Vera, post: 4101855, member: 98685"
The testing department for the drivers must be made from monkeys....
Complacency most likely. It gets all of us eventually.
Posted on Reply
#3
GoldenX
Or maybe they were testing the user base, see their reactions.
It's very easy to call it a "bug".
Posted on Reply
#4
Vayra86
GoldenX, post: 4101871, member: 160319"
Or maybe they were testing the user base, see their reactions.
It's very easy to call it a "bug".
Yep I wouldn't discount this one. Fix was faster than usual and this was the "Gamescom special". A perfect moment to tell everyone they should really get GFE. Telling, the Nvidia way, that is.
Posted on Reply
#5
cellar door
"Nvidia has found a bug' ....you mean after 10+ websites and probably hundreds of other kinds of reports, they realized they screwed up.
Posted on Reply
#6
ShurikN
Meh, Nvidia can go suck on a lemon. Got NVCleanstall, installed it without all of their junk.
Posted on Reply
#7
PanicLake
The fact that they kept the same version number (436.02) it really bugs me!
Posted on Reply
#11
EarthDog
Fluffmeister, post: 4101914, member: 101373"
Drama over, we can all sleep well now.
Yep... stuff happens.
nemesis.ie, post: 4101922, member: 22637"
... until the next time.
I hope to see this sentiment when AMD drivers have issues (oh wait...) and do the same thing...
Posted on Reply
#12
Vya Domus
Prima.Vera, post: 4101855, member: 98685"
The testing department for the drivers must be made from monkeys....
Doubt it, Nvidia probably has more employees dedicated for drivers/support than AMD has for their entire GPU division.

"Mistakes" such as forcing the installation of GeForce Experience probably weren't mistakes at all and were actually well intended actions. There is no way things like these can slip through, they were simply hoping there wasn't going to be much fuss about but since that did happen they have now "fixed it".

Writing code that brakes some functionality, yeah I can pass that as a mistake. Going out of your way to not only manually enable something for installation as a default action but also disabling the user's input , a mistake ? I am not a moron, I don't buy that.
Posted on Reply
#14
catulitechup
Prima.Vera, post: 4101855, member: 98685"
The testing department for the drivers must be made from monkeys....
Yeah more cheap and leave more money for leather jackets

:)
Posted on Reply
#15
xorbe
PanicLake, post: 4101910, member: 188909"
The fact that they kept the same version number (436.02) it really bugs me!
Undoubtedly because only the installer was fixed, and the driver remained identical. (Just sayin'.) They'd likely actually have to change something in the driver files to spin a new number.
Posted on Reply
#16
W1zzard
xorbe, post: 4102202, member: 102945"
Undoubtedly because only the installer was fixed, and the driver remained identical. (Just sayin'.) They'd likely actually have to change something in the driver files to spin a new number.
and getting WHQL for a new driver version takes some time
Posted on Reply
#17
Das Capitolin
For whatever it's worth: After hitting 404 errors attempting to download version 436.02 for most of Tuesday (8/20), I returned this morning and downloaded 436.02-desktop-win10-64bit-international-whql-rp.exe at around 9am PST. Even after they took it down on 8/20, it seems that NVIDIA re-enabled the same release that forced the installation GeForce experience. Not wanting anything more than the graphics driver, I waited a few hours and downloaded 436.02-desktop-win10-64bit-international-whql-rp.exe again at 1pm PST. It's the same file name, same release version, and GeForce.com displays the same release date - but the two files have different behaviors. Good times.
Posted on Reply
#18
lexluthermiester
Prima.Vera, post: 4101855, member: 98685"
The testing department for the drivers must be made from monkeys....
Or, and I might be going out on a limb here, it was just an honest mistake. Very likely a single error in the install scripting..
Posted on Reply
#19
Gasaraki
ANyone have reviews for this driver release. I seemed to have lower performance in Remnant: From the Ashes after installing these drivers. It could be related to the just in time setting also. I turned that on.
Posted on Reply
#20
EarthDog
Gasaraki, post: 4102636, member: 168493"
ANyone have reviews for this driver release. I seemed to have lower performance in Remnant: From the Ashes after installing these drivers. It could be related to the just in time setting also. I turned that on.
Disable it and check. ;)
Posted on Reply
#21
R-T-B
lexluthermiester, post: 4102341, member: 134537"
Or, and I might be going out on a limb here, it was just an honest mistake. Very likely a single error in the install scripting..
Likely both could be true, as I DO believe this is an honest mistake. But likewise, how the heck do you miss it in testing?
Posted on Reply
#22
lexluthermiester
R-T-B, post: 4102818, member: 41983"
how the heck do you miss it in testing?
When you're under pressure to make a deadline, a small mistake can get away from you..
Posted on Reply
#23
R-T-B
lexluthermiester, post: 4102945, member: 134537"
When you're under pressure to make a deadline, a small mistake can get away from you..
True. An organization can apply pressure that way and affect the end product sadly
Posted on Reply
#24
lexluthermiester
R-T-B, post: 4102958, member: 41983"
True. An organization can apply pressure that way and affect the end product sadly
Right. People sometimes forget that big companies have people working for them and those people make mistakes sometimes. What I find interesting is that NVidia, like AMD with their last driver issue, got right on this problem addressing it and fixing it swiftly.
Posted on Reply
Add your own comment