I'm a tolerant person, but I switched from Windows to Mac because the forced Windows updates kept messing me up. One time I left a long simulation running overnight. In the morning, I was greeted by a computer that had automatically rebooted to install updates, killing my simulation. Another instance was my daughter's birthday party, where she wanted to show a movie. The computer decided to spend an hour doing updates instead. It seems like Windows has become an update engine that will sometimes also do computation for you.<p>My assumption is there's someone at Microsoft who gets a bonus as long as they keep presenting update graphs going up and to the right, and they don't care how much they mess up the user experience in the process. Microsoft should reassign that person.
> Microsoft has been continually tweaking the way the Windows 10 updating process works based on "user feedback"<p>I... what... where... when?<p>Seriously, how about just giving control to users? And btw, I still see machines were the telemetry service eats CPU. If you cannot get it to work, remove it. It shouldn't be part of an OS anyway. Don't tell me users like it, you could just offer an app in that case.<p>I don't get how neglected they have treated their flagship for desktop computers. Software as a service is good for my
tax declaration, but I really hate this trend.
Before Windows 10 I would just disable the Windows Update service and enable it on my own schedule when I wanted to do updates. I've had my machines stay undisruptive for months on end, sometimes up to a year without rebooting, and the reboots would be initiated by me (hardware changes, power outages, or updates that I actually wanted to install.)<p>Since Windows 10, Microsoft has caught onto this and added a new service that checks if you disabled the Windows Update service and re-enables it automatically, and sets permissions that initially deny you from tampering with it that then makes this a little more challenging to get around, but still possible to do manually. I later found Windows Update Blocker (WUB) which does all of this for you in one click. I have been using it ever since, and have never again been nagged by any update or experienced an unexpected reboot: <a href="https://www.sordum.org/9470/windows-update-blocker-v1-5/" rel="nofollow">https://www.sordum.org/9470/windows-update-blocker-v1-5/</a>
If it didn't require a reboot, an automatic update wouldn't bother me at all. I hate that my one remaining Windows machine is never in the same state I left it because it rebooted during the night.
I finally got pissed off enough at the forced update policy that I made a tool to disable updates for real: <a href="https://github.com/wheybags/win10bsfixer" rel="nofollow">https://github.com/wheybags/win10bsfixer</a><p>It works by killing and disabling the windows update service every 10 seconds, so it should be resilient to pretty much any aggressive changes ms makes. It does allow manually updating when you want to too. I want to have it handle some other nasty behaviours too eventually, but its enough for me to use for now.
As an outsider (someone who doesn't use any MS products) looking in... why would anyone build a production system around this platform? Why would anyone use this platform?<p>Windows 10 has, since it's inception, been a privacy nightmare, which simply does not respect the user or administrator. There might be some hacks to let you turn some of these behaviors off, but it seems like they aren't likely to survive an OS update.<p>I just cannot imagine owning a business and being OK with some other company having control over whether or not I am permitted to use my computer systems to get work done today.
There are a lot of comments on this thread which ignore one important point. Windows updates are totally centrally controllable to an enterprise user. They can be made silent, and force rebooting can be incredibly rare. On the other hand I get lots of calls about mac problems which are caused by not updating! That is not really the Unix stability that people argue for, is it? We answer Mac calls with a 'have you tried updating, then turn it off and on again'
Too many users were using options to hit the 'defer updates for 365 days' button.<p>Microsoft can't let them do that ("...Star Fox!"), they NEED the newest features, security updates, and telemetry.<p>Cynical: The stupid users don't know what's good for em, that's for MS to decide now, not the users.<p>However, there is an opt out via GPO for now. Of course if that gets used enough it will be ignored.<p>"If you wish to continue leveraging deferrals, you can use local Group Policy (Computer Configuration > Administrative Templates > Windows Components > Windows Update > Windows Update for Business > Select when Preview builds and Feature Updates are received or Select when Quality Updates are received)."
Want us to be more tolerant of updates? Set things up with much better support for shutting programs down cleanly and ideally restarting them as they were. Add a Windows message that says "shut down for restart" and don't do a forced restart until every program has honored it. (Obviously, older programs won't support it.)
I'm trying to see the benevolent aspect of these major updates that happen every 6 months, but I don't see it. Do they have to be so frequent? Do they have to be so massive (several GB downloads)?<p>And yet, 5 years after RTM, Windows 10 still has two control panels and an overall inconsistent UI and plenty of bugs. The whole OS is like a permanent work in progress.
All these never ending stories with Windows Update in W10 is like walking around the problem that is caused by lack of proper QA team that was pushed onto users and removal of previously perfectly working feature of selective updates installing - which was obviously great because in case of problems user could just skip the bugged patch and wait till a fixed version is released. The old way of delivering patches in Vista/7 style should return - even by a price of patches "weight".<p>I get it: they want people to stay up-to-date to avoid problems of zombie-machines but Windows isn't OSX that works on narrow set of hardware and software configurations - these differ much (duh) and that affects how updates work. Expecting that users will ditch their workflow to report all issues on forums (or these will come from the "<i>enthusiasts</i>" testing grounds), will want to play countless reinstallations, backups and restoring is just wrong. This leads powerusers who want to have more control over their machines to disable (temporarily or permanently) WU along with associated processes which by the way, seem behave in a very malicious way.
I am honstely surprised that businesses and other organisations have come to accept this constant 24/7 "updates" scenario from Microsoft without some intelligent business people calling them out on it.<p>Imagine if every month, every week, or even every day someone from an office supply company came around to your office and collected all your pens, pencils and other office supplies and replaced them with "updated" versions. Meanwhile you could detect no meaningful difference from the "old" ones. After a while, you would just tell them to go away: "The supplies I have are working just fine. Thanks."
A happy Ubuntu users here for the last 15 years, I guess I don't really understand what Microsoft is messing around anymore and I'm just glad that I do not need Microsoft at all for so long.
If you <i>must</i> run Windows 10 I strongly recommend the Enterprise LTSB (Long-Term Servicing Branch) version. You have much more control and can strip out most of the garbage.<p>I'll leave it as an exercise for the reader to figure out how to get a single copy of Enterprise LTSB. Hint: windows 10 enterprise ltsb gen2
What pisses me off is that a windows machinea spend so much time downloading and installing the OS and just a few Microsoft apps.<p>Linux machines update everything including hundreds of apps you may have installed (and some are updated very often) and you barely notice it happening because it's so damn efficient.
I genuinely don't understand why people buy the "New Microsoft" marketing line. They are adopting Linux because they have no other option. Where they're strong, the desktop, they're still the same old Microsoft.
This is just going to cause technically-inclined people to configure their networks to MITM all calls to the Windows update servers and block updates network-wide.
WINOS >> a work in progress since the 1980's
WINDEVS >> don't touch what is working unless your boss told you to do so.
WINUSERS >> don't update unless your boss tells you to do so if you have no boss don't update. REALITY >> you need two computers which can do the same work if one goes down.
And of course it's still possible to opt-out with some "pro" version?<p>I mean, there are always situations where you want to avoid to be interrupted by updates by all mean...<p>Oh wait, I get it... pro versions are called Arch, Gentoo, etc... ;)