Slashdot Mirror
Microsoft is Making It Easy To Stop Windows 10 Rebooting Your PC Randomly For Updates (theverge.com)
Tom Warren, writing for The Verge: Microsoft is unveiling some changes to the way Windows Updates are applied to Windows 10 PCs with the upcoming Creators Update. The software giant has long been criticized by Windows 10 users for its aggressive approach to applying updates, and it's introducing some new options to prevent annoying reboots. "What we heard back most explicitly was that you want more control over when Windows 10 installs updates," admits John Cable, Microsoft's Windows director of program management. "We also heard that unexpected reboots are disruptive if they happen at the wrong time." To stop these random reboots, Microsoft is adding a new snooze option that appears in a new prompt to let you know there's a Windows 10 update available. Snooze will stop an update installing for three days, and give you time to save any crucial work.
Oh it exisits, it's called Windows 7, which market share increased this month. Even Windows XP is still at 8% market share three years after end of support. This all shows the failure of Microsoft.
And what would happen if the Snooze button is hidden by some other service or if it disrupts another service at an unexpected moment? How many of us has been accidentally selecting "OK" on something just because we were typing some text in a word processing or something and don't know what we did click "OK" for?
If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
Which is why serious work doesn't get done on Windows.
Unfortunately, some software is only available on Windows. People who don't program for a living tend to program to the style of the system they have at hand, and because Microsoft has so polluted the programming environment with system specific things, those programs become system-locked until someone with programming skills can convert it. If the source is available. If there is money to pay someone to do the programming.
This applies alot in the scientific community. Really smart scientists, or their graduate students, program something in Visual Basic or C# or whatever, and this becomes a distributed executable shared with others. They don't know better.
Or worse, it is a small company that has picked up the program and doesn't have the money to support multiple OSs, so they pick the one that everyone has. Windows. They don't make enough from your license to pay someone to port the code to Linux to run on your system, so sorry.
I have users who have models that run for a week. The "three day delay" in rebooting is really nice, Microsoft. Thanks so much. It does make for a wonderful morning when one of those users comes in to find the system rebooted after a five day run on a six day model. And all I can say is, umm, well, start over? And pull your system off the net. Yes, copy all the boundary condition data off the fileservers before you start.
only an idiot would bring along a system to do a big presentation that is subject to frequent uncommanded reboots and brick periods.
Unfortunately, in the scientific community, such presentations are often not under the control of the user, depending on the "IT department" of a hotel or convention center. And by "IT department" I mean the low paid people who have to deal with 1000 issues and problems all going on at the same time. The same people who make sure there are tables and water and the signs are correct for each of 100 meeting rooms...