ManuelG over on GeForce forums said that they'll be releasing a new driver soon due to all the issues with 353.50.
As for forced installs, I haven't had that issue in a while, but it was a real PITA when I did. I think there's a tutorial here on TenForums that shows how to make sure that doesn't happen.
Edit: Here's a solution for blocking driver updates directly from Microsoft: https://support.microsoft.com/en-us/kb/3073930
Thanks for the link to the blocking utility.
Unfortunately, I haven't been able to get it to work. Windows update, so far, always restores 353.30.
UPDATE:
There's an internal setting in 10240 to block Windows Update for drivers. I set it, and no over-write of 353.49 for a half hour or so. Fingers crossed that it holds.
Last edited by bobkn; 17 Jul 2015 at 11:10.
Windows Update just pulled down a new driver. R353.54 (r352_00-220) / 10.18.13.5354 (7-13-2015)
Windows Update downloaded and installed new Nvidia Driver 353.54.
NVIDIA Graphics Driver 353.54 (WHQL) for Windows 10 from Windows Update Website:
Desktop Driver for Win 10 x64:
http://download.windowsupdate.com/d/...ac7f1c4154.cab
Notebook Driver for Win 10 x64:
http://download.windowsupdate.com/d/...412f5d41f9.cab
They seemed to have fixed the mouse cursor issues.
However my original install from the Nvidia site was custom installed without 3d drivers as I don't need, want or have a 3d capable monitor. This update has given me 3d back.
I hope when W10 is final they don't keep sending out these updates for every driver released by Nvidia as often the only changes are to support new cards or new games, which I am very unlikely to own.
I think we need a "Latest Intel Graphics Driver for Windows 10" thread since the majority of laptop users have either an Intel IGP as their main GPU or Intel Switchable Graphics with an NVIDIA/AMD GPU.
Intel is usually good working with Microsoft to bring the latest drivers to Windows Update but there's always going to be newer ones via external sources that may fix bugs working on Windows 10.
Nemix, I think you are right. The problem it seems is, as long as they keep coming out with new builds, the code keeps changing and the drivers that worked before don't work now. I've talked to a couple of places where the developers have just thrown up their hands and quit trying. I believe when Microsoft says this is the 'final' release, you will see a lot of new drivers come out.
Microsoft has not even released the codes on the latest new builds. If you will look at the top f the BSOD section, you will see we cannot even work BSODs because the codes are not compatible. Hopefully things will begin to change fairly quickly in the next week.
