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)
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)
24 Comments on NVIDIA Fixes GeForce 436.02 Installer, No Longer Forces GeForce Experience Onto You
It's very easy to call it a "bug".
"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.
:)