maratsade wrote:
wildcats198308 wrote:
From what I have read the pauseing feature should be 35 days. It didnt say anything about anything less. It seams like a stupid feature to begin with, WHY would someone pause updates for 35 days!! From what it sounds after the set amount of days it will download the updates. Just sounds stupid. .
Exactly. What's the point of pausing? I wonder what Microsoft's reasoning was on this, and why they gave this only to some editions and not others. The whole thing makes little sense.
ETA: apparently, the point of pausing is to see how the update affects other people's machines. If no one's machine melts down, then the user can unpause the update and it will be installed**.
So it seems pausing just stops the installation of the update, but not its download.
I was thinking this was a possible reason, as well. In all of the articles I've read about the ability to pause the updates I couldn't find anything that specified whether it paused the actual download or just the installation, and, knowing Microsoft, the latter would probably be the case. And, with that, the only advantage I could see with pausing them was to see what the downloads do to other machines. Sort of as a failsafe, but a poor one, as you can't pick and choose what to pause. It's either all or none.
With forced updates being introduced with Windows 10, I'm sure there has been a higher instance of machines being somewhat messed up, or even bricked. At least with Windows 8.1 and prior you had the ability to safeguard your machine from that possibility.
Hopefully, with this pausing ability, it will cut down on the instance of bad things happening. Still, again, I won't use it.