(I thought about doing it, but honestly I can contribute better by coding.) This is most likely a Don Quixote quest, but I'd really like someone here to take this on and drive it. This is definitely breaking the contract for 'supported.'Īnyone feel like taking on a slow, long term task of getting some lawyers excited about this idea? Best place to start would be the lawyers that won the GTX 970 class action lawsuit.
We have yet to see any update to the driver from 425.31, and that includes zero updates for security fixes. (Not out of malice, most likely just clumsy, stupid, large corporation).īut I do feel like they need a class-action lawsuit for their "one year of support" of 3D Vision. I feel like NVidia is definitely abusing their monopoly position and breaking things without a care in the world.
If Nvidia is forcing a driver update that will make 3DVision completely obsolete (for your average user that doesn't know how to jump through hoops to make things otherwise), could that be possible grounds for a class-action lawsuit against them for rendering technology that people have paid them money for useless? This isn't usually my line of thinking, but if it is then maybe we should pursue that avenue, if nothing but to make an actual statement to Nvidia that they've officially gone too far this time and that their lack of respect and support for us, after all this time, will not go untolerated. It might be worth checking if the same naming is used for everyone else so that the above procedure to prevent this update would generally apply. Now the folder and file naming for this update so far always remained the same for me. So whenever Win10 now tries to apply this update, it actually fails to do so since it tries to execute/extract this purposely corrupted fake/dummy update file. Then I set that fake/dummy file's attributes to "read only". So to break this chain process, I simply replaced the already existing "581,714,058" bytes large file "C:\Windows\SoftwareDistribution\Download\857e4a5473a85c2623285311e25e1bc0644c5862" with a self-created fake/dummy "33" bytes large file, only containing a short text expression of what I think about this update. Once the update is being applied by Windows, that file generates a temporary installer folder at "C:\Windows\SoftwareDistribution\Download" from where the Geforce 432.00 driver is being installed.
On update download completion it is being placed at: "C:\Windows\SoftwareDistribution\Download\857e4a5473a85c2623285311e25e1bc0644c5862" Well here is what I did to prevent my version of Win10 from being able to actually apply this update and it ain't exactly "RocketScience":įrom observation I noticed that while this update is being downloaded it is being placed temporarily at the following file & folder location:
There is plenty of people complaining about this at various places.
It looks like this geforce 432.00 driver windows update started being pushed around November 2019. It seems that I have figured out a way to reliably prevent that "SLIP-IN" forced windows update on my machine but before giving a tutorial that could potentially brick your Win10 installation I thought I would first bring this matter to you guys' attention.Īpologies in advance in case this has been already posted/discussed on these forums. I don't know about you guys but with most 3D Vision enthusiasts having moved from to here, this pretty much looks like a declaration of war from where I stand. I guess MICROSOFT/NVIDIA finally figured that with users preventing geforce driver updates via their usual delivery pipelines (geforce experience & co) they would try a new approach by forcing the geforce driver update via the windows update system.
Last week I started to think I was tripping when suddenly out of nowhere I noticed that my beloved and meticulously tuned 3DS&VR Windows 10 setup would force update without message or warning from the 425.31 3D Vision compatible driver to the NON 3D Vision containing 432.00 geforce driver version. MICROSOFT/NVIDIA are FORCING Geforce Driver 432.00 via Windows 10 Update