Are you referring to my post? Apologies if I got it wrong. If you do, I use the latest NVIDIA drivers (and my rig is fully shown in my system's specs).
PS: I always prefer a clean installation of the OS instead of an update but there is no official ISO and I do not wish to download a torrent or use other methods to create it myself. I will clean install the latest NVIDIA driver right now though.
Thought the bug in setting a folder for slide show was still there but a reboot solved it. Appears to be a very good build and nothing negative of note so far.
Which driver version did you install? I tried 353.30 after doing a clean install of 10158 and got an error, so I installed 350.12 and it's working fine. The thing is that 353.30 was working good on the previous build. I may try it again.
I have a 500 series Nvidia card so I can't get the Nvidia Windows 10 beta drivers.
Jim
352.84 is installed by default... Why not leave it at that?
Seems like the taskbar not moving easily is something to do with a setting inside another piece of software I use. "WindowSpace" snaps windows to one another when moving or resizing them, for easy re-arranging if you do a lot of multiple-window workflow like I do. When I untick "snap child windows inside MDI parent", the taskbar seems to move via drag and drop (at least so far).
Kind of annoying, since like how FlashWheel-VistaFix is the only software of it's type that achieves the effect I need, WindowsSpace replaces the no-longer working allSnap by Ivan Heckman that I used to use on Vista and Win7.
So it seems many of your problems are related to incompatible apps. Don't blame the OS for that.
When a new OS comes out, things change, and apps have to be rewritten to adjust for the changes, especially apps that are invasive into trying to override things the OS does. You will probably have to find new apps, or wait for the authors to update them. This is nothing new, and these kinds of apps have broken every time there has been large updates to Windows.
Part of problem is that these apps often rely on undocumented functionality. They observe that if they do this or that, then something happens. Then they write their app to use that undocumented behavior. When a new version of the OS comes along and changes how that behavior works (after all, they never documented it, so they could change it if they wanted to), then the apps that relied on this break.
The app authors are either not using API's they should be, or they just have to live with the undocumented changes if what they're trying to do isn't officially supported. It's the cost of doing undocumented things.
Quote
