ah yes, I remember that too now. they had to backtrack fast on that mistakeSpeaking from personal experience, this forced upgrade was a thing. Microsoft pushed the Windows 10 upgrade into the "recommended" update cycle, and people who had accepted standard default update settings ended up waking up one day to a Windows 10 welcome screen. Happened to the media center PC I built, which the wife uses as her primary - she always hit the little "X" to tell the constant harassing reminder about upgrading to Windows 10 to go away, never once clicked to accept, yet it magically updated one evening. Wiped most of her settings, she lost her email (how the hell they managed to screw up a basic function like native email in upgrade from Windows 8.1 to Windows 10 still baffles me), and was generally confused as could be until we got things figured out. On the work front, we have a remote facility that had 2 Windows 7 computers end up in the shop because they couldn't boot up, turned out it was a failed unrequested Windows 10 upgrade attempt that managed to completely botch them up. That was fun to figure out.
It was a widely reported issue earlier this year, covered on many tech sites, and lawsuits were imposed against Microsoft over the whole debacle. Windows 10 was worth upgrading to for free for many people, they didn't have to try to ninja force-feed the thing into people while they were sleeping. But, Microsoft isn't exactly famous for having continuously good judgement.
No you shouldn't load win 10 give it a couple of years until it's ready for prime time. I've been using on different hardware since the very first not to public beta and it's still really beta software, the last major update borked all kinds of hardware.
it's already been out for over a year. it's not like you are an early adopter if you upgrade now. if an issue does appear you can always just go back to win 7. with hundreds of installations, you are bound to find people that have a bug or 2.
on the other hand, if you are on the latest beta builds you'll notice that they removed the dreaded svchost. you can finally see separate service processes and which one is causing you problems (like 100% CPU usage)
I think the next big update will be the one you might like since it also overhauls how updates work.
Last edited: