[ryanl0l]

>Or major driver changes, huh? Never ever ever had I a working device driver turn nonfunctional overnight. Before this "upgrade," that is.

Blame your OEM, they're responsible for keeping their drivers functional. Microsoft didn't just go behind OEMs backs and do this.

>Who exactly got an EULA prompt on an unattended, locked workstation with nobody at the sear? As I say, the downgrade was full auto: evening W7, morning W10.

That's certainly strange, are you sure it wasn't just the W10 installer? Or did it really go straight to the login screen?

[Piskvorrr]

I would blame my OEM IFF I were planning an upgrade. Then I would test it out first, see that it broke stuff, and go looking for a solution.

Oh wait. That's what we did, found that the drivers weren't there, and FRIKKIN DECIDED NOT TO UPGRADE because of this. Acceptable risk of running a recently EOLed product and all that.

Nope, nope nope nope, Microsoft knows better: "here's your new nonfunctional box, not our problem anyway."

No, not an installer: a fully upgraded, but - sadly - significantly dysfunctional W10 (Note that other users around the thread offering similar experiences, so your insistence that it can't ever ever happen sounds very much like wishful thinking). As I said: we have repaved from backups, installed GWX Control Panel, and disabled Windows Update. Personally, I am pretty angry about that last thing, too - but I had no power over mgmt: thanks to your poisoned update, they don't trust it to actually bring security fixes any more, quite the contrary: you, in effect, have mounted a denial-of-service attack on us via WU and nobody cares if it was intentional - "Windows breaks by itself when you need it the least" is now firmly believed by everyone affected (we are considering a move from Win altogether, because for all we know, you might have some other control channel up your sleeve for pushing some more "upgrades").