You can't have both no updates and avoid random exploits that are randomly discovered with time. Maybe experienced users know what's going on, but an average user would mindlessly click ignore until the machine is owned by ransomware.
But it's Microsoft's ass that gets dragged through the mud for decades when unpatched Windows machines cause problems for others.
They learned their lesson. Users can't be trusted.
At least now you ARE prompted to reboot if you have used the machine at all in the past 3 days or something. And if you haven't, it will still wait a week.
No one in this thread seems to be up to date on that. Everyone is complaining about the Windows 10 of 3-5 years ago, completely unaware that things have changed a lot.
So yeah I see why Microsoft does what it does, sometimes. The internet won't cut them any slack no matter what happens, so Microsoft do what's best for the user, whether they like it or not. And, again, they don't just surprise reboot anymore if you're on a recent release.
But it's Microsoft's ass that gets dragged through the mud for decades when unpatched Windows machines cause problems for others.
I'm not sure that's entirely fair. But in any case, Microsoft's reputation is certainly being damaged by the long series of failures caused by bad updates to Windows 10.
No one in this thread seems to be up to date on that. Everyone is complaining about the Windows 10 of 3-5 years ago, completely unaware that things have changed a lot.
The important facts haven't really changed. There might be some small quantitative improvements, but qualitative changes are required to fix this problem, and Microsoft is still stubbornly refusing to make them because they don't fit the business model under Nadella's leadership.
Sadly, until there are viable alternatives so a large proportion of Windows users can jump ship, they'll probably continue to get away with it too. The only other potential way out I can see is if governments step in and start regulating because the damage is becoming sufficiently painful that voters/businesses are starting to send a significant number of complaints. I'm not sure we're there yet, even though plenty of people have been stung by a bad update at least once already.
This is exactly why I don't run Microsoft software, even after their rabid tendencies mellowed a bit - providing software the user wants is not their priority.
But neither commercial consumer platform is producing an OS that respects their users - it is one-size-fits-all, you must be an idiot-ware. I don't serve my operating system, it's the other way around. So I'm done with both of them.
>No one in this thread seems to be up to date on that. Everyone is complaining about the Windows 10 of 3-5 years ago, completely unaware that things have changed a lot.
Because when you have wide ranging issues like that it takes a lot of time for people's opinion to change. All it takes is for a user to be burned once by this system and they might end up remembering and anticipating these issues for decades. MS reaps what they sowed.
>so Microsoft do what's best for the user, whether they like it or not.
And over the years this builds up an anti-MS/Windows sentiment that will be very difficult to get rid of.
I tried running a weaker machine on Windows for my parents. They ended up not using the computer at all, because every time they started the machine it would do something update related. Even just the things in the background made the computer unusable. There aren't prompts for things like that. They would rather go and pay their bills in person than use the computer because of the updates. I didn't know it was that bad, but actually trying to use it myself I understood.
That is simply not true. My up-to-date Windows 10 machines frequently reboot without me telling them to do so. I'll be working on some project, leave the project windows open and put the computer to sleep over night, only to find the computer rebooted next morning. Presumably the computer woke up in the middle of the night, showed the update prompt to the empty room, and since nobody intervened, killed my programs and rebooted.
Then you've done something somehow, or I have, because none of my 5 Windows machines have rebooted without a week's notice in about three years.
If it helps, you can use "powercfg /lastwake" at a command prompt to find out why the computer last woke from sleep. With that info you should be able to put an end to those unrequested wakes.
You have probably adjusted something, though Microsoft are very good at undoing anything you do to disable automatic updates. The update system by default wakes the PC up in the middle of the night to reboot it. In my experience it more reliably wakes the PC up than rebooting it, so what happens is you just have a PC which turns on in the middle of the night and sits there idling, which is extremely irritating if you happen to sleep in the same room, and accomplishes nothing.
> when unpatched Windows machines cause problems for others
Charitably that's only half of the story. Their security model was ... not great in the past.
If as you claim their security PR problems were all due to poor decisions by users then where are all the people slamming Apple for all the vulnerable systems caused by postponement of updates? What about Ubuntu, Fedora, etc?
