Cannot install GeForce driver for GTX 780 Ti ["The data is invalid."]?

Oxonsi

Honorable
Feb 1, 2014
27
0
10,530
When I downloaded and tried to install GeForce driver 347.52, I saw the files self-extract as usual, but before the installer started, an NVIDIA INSTALL windows opened and stated, "The data is invalid." and quit. This is the first time I have seen this.

I re-downloaded the file just to make sure it wasn't corrupted, but the result was the same. In fact, I downloaded several prior versions of the driver to see if it was something to do with 347.52, but it isn't. It seems now, no matter what GeForce driver I download, if I try to install it directly, it will self-extract as expected, and then promptly give me the message, "The data is invalid." and quit.

I found a work around by going into the Device Manager control panel, right clicking on one of the display adapters, selecting, "Update Driver Software...", and then pointing it to the path where the driver software was extracted. The driver update then installed.

While the above workaround method worked for me, I'd like to fix the problem with the normal installer, or at least understand what the problem is. Under the workaround, I don't have any options for updating PhysX, etc.

Any info / advice on this? Thanks!
 
Solution
Have a look at the path where the update is extracted and then work your way back looking for anything that shouldn't be there.
A good example is a file named "C:\Program" that prevents files without paths that are properly specified from being found in "C:\Program Files".
Have a look at the path where the update is extracted and then work your way back looking for anything that shouldn't be there.
A good example is a file named "C:\Program" that prevents files without paths that are properly specified from being found in "C:\Program Files".
 
Solution

Oxonsi

Honorable
Feb 1, 2014
27
0
10,530
Thanks for your reply.

I submitted my question to nVidia, and they suggested I use Display Driver Uninstaller (DDU) to completely uninstall my current driver. This method worked for me. Apparently there was some Windows registry corruption related to the display driver.

Your suggestion also makes sense, and I am making a note of it for future reference. Thanks again!