Nah, the UI is exactly the same - hasn’t been moved to the “Modern” settings yet.

What’s weird to me about all y’all having this issue with driver updates is: I never turned it off, and yet I’m still on August nVidia drivers… Only automatic updates I can recall seeing are on my work desktop, and it needed them. Dell’s Intel integrated driver (the stock Intel ones refuse to install, because Dell) were lagging waaaay behind and had, um, issues with dual DisplayPort monitors and waking from sleep.

Otherwise, I guess I’m failing to meaningfully contribute by pretty much saying

Heh.

Right. Nobody had problems with Windows updating MS drivers over nvidia’s in Windows 7 or 8.

Thanks Denny! All is well. Wow it is good to have all my hard drives again :)

Now if I can fix this last issue I’ll be golden. My Sound is pretty messed up. I get sound out of left front and left right speakers, no center channel nor base, and only one rear speaker. I have Creative Labs SoundBlaster Zx. I can’t find a single post on the Internet saying whether I should stick with default Windows drivers or install Creative’s version. My install is so nice I hate to mess it up. I have my motherboard’s onboard chipset disabled in BIOS settings.

you know about that ‘shutup10’ utility right?

http://www.oo-software.com/en/shutup10

Yes, yes that’s what will help him and solve all the world’s problems at the same time.

Well, not all the World’s problems, but it may make Windows 10 do what he wants it to (rather than what MS wants), at least until the next major update resets all those settings to the default MS approved spyware configuration.

What spyware? You mean the basic telemetry data?

So this is crazy. If you read my last post I had no subwoofer or center channel sounds. I installed the soundblaster drivers and now I DO have subwoofer and center channel, but now the front channel sounds don’t work! Arghh!

Ohhhh. So I hit the “A Speaker” button on my receiver and I now have front, center, and rear channel working but no subwoofer. Weird. So originally it was a driver issue and receiver setup issue, but now it’s just a receiver configuration issue.

And as I talk to myself lol, I now have subwoofer working too! Everything fixed :). Problem is I have no clue which series of things I clicked made it work. Chances are next to we lose power everything will go to hades again.

This may sound dumb, but at least now you know that it’s possible to have everything working. I find that at least knowing success is possible takes a lot of frustration out of fiddling with things.

Yes that is absolutely true! For a while I couldn’t determine if my sound card had gone bad, or my receiver. I’d hardly used my computer over the last year so the possibilities were endless. I am a super happy camper to have all my sound!

One lesson I learned for sure - Windows 10 default drivers for Creative Labs hardware are terrible but I’m guessing they provided them to Microsoft so it’s on them.

Yeah, the default creative drivers in Win10 are absolutely terrible. They actually make things sound worse. The crazy thing is that they’re Creative’s own drivers, but they’re seriously fucked up. You have to download the full driver package from Creative to get your speakers to work properly.

Fucking blue screening in Age of Wonders 3 since the 1511 update. Huzzah.

When was the last time we had this much driver/update fuckery? Vista? Christ.

Poking around, looks like this is a common problem in 1511 across several games. Hooray. May just roll back to previous Win10 build.

Yeah, for a bit I was tempted to update but I keep hearing many places and from friends about annoying stuff like that and I keep putting it off.

I suppose 8.1 is still working like a champ and I just don’t want to risk the waste of time running into any of that nonsense.

I like a lot of stuff about Win10. All this driver fuckery is pushing my buttons in a huge way though.

NVidia drivers? I had to roll mine back to 358.91, with the clean installation option, then the blue screens stopped.

I’m still not having that issue in 10, so that leads to me to the idea that perhaps the folks that are may have tweaked an option/registry setting/local policy somewhere.

coughShutup10cough

Just yanking chains :-)

Although, seriously. I’m 100% confident that utility is doing some things in undocumented/unsupported ways so I’d expect strange behavior eventually on any system its pointed at.

Eventually updated to 361.43 last night and played a couple hours with no bluescreen, hopeful that fixed it. I’ll start trying older versions with whatever that third-party driver-removal program is if I’m still boned.