Hacker News Reader

Comment by Piskvorrr | Hacker News Reader

Shitty meme for a shitty forced upgrade, very fitting. Where do you want to go today? Eh never mind, we get to decide that.

No, that's explicitly not how MS updates worked: up to now, they were updates to existing OS, not automatic reinstall.

If I don't want it, I don't get asked if I want it: 19:00 there was a working Win7 box, 07:00 next day, there was a broken steaming pile of something, apparently Windows 10. No prompts, full auto.

Program files: deleted. Users folder: moved into some other location (both). I don't give a flying fork if that was intentional, it should not have happened, full stop.

In other words, FU, astroturfer. Take your piece of crap and shove it. (Yes, your wonderful Windows Nein has given us about a man-year of unplanned maintenance so far, so you see how happy I'm about it)

View on HN

>No, that's explicitly not how MS updates worked: up to now, they were updates to existing OS, not automatic reinstall.

A semantical difference really, previous windows updates just didn't include major UX revamps.

>If I don't want it, I don't get asked if I want it: 19:00 there was a working Win7 box, 07:00 next day, there was a broken steaming pile of something, apparently Windows 10. No prompts, full auto.

surely you got an EULA prompt, no?

>Program files: deleted. Users folder: moved into some other location (both).

I certainly agree that microsofts QA has failed horribly here.

>In other words, FU, astroturfer.

One could easily accuse you of the same.

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

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.

>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?

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").

Did ryanlol/l0l switch to a special arguing account, or is that a different user?

Seems very meta :D

Haha, that's a good idea. But no, the "ryanlol" account has rather restrictive ratelimiting in place.

Reply on news.ycombinator.com