Forum Discussion
Pausing Updates in Windows 10 version 1703...
- 8 years ago
I have the Creator Update on a few of my systems (it still wont work on my Laptop, which I am not happy about). On the systems that are running Creator Update, I never noticed an option to Pause either. I also have Home Edition.
I just did some searching and found that the Pause option is only available in Pro, Education, and Enterprise versions. Link below to other features if you'll want to read em.
I guess I should have searched a little more thoroughly. :smileyfrustrated:
With that said, and with the initial question asked, I doubt that I will ever use the ability to pause my updates. It was only a question of curiosity as to why one of my computers would show a different ability than the other when they have the exact same version of Windows 10. Well, not the EXACT same. My laptop (a Dell) originally had Windows 8 Pro OEM preloaded and was upgraded to Windows 8.1 Pro, then Windows 10 Pro and then to the present version of Windows 10 Pro. All of them were done with the free upgrades. My desktop (built by me), on the other hand, started with a retail version of Windows 7 Pro, then upgraded with a retail version of Windows 8 Pro, then the free upgrades from that. I wonder if the difference between the allowable days to pause is due to the one being OEM and the other being retail.
In the end, though, like I said, I'll probably never use that ability, anyway. I've never used the ability to set my laptop to a metered connection with WiFi, nor have I done so with the new ability to do the same with my desktop and a direct LAN connection. I've never been close enough in my data use and allotment to need to worry about it.
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. Maybe you should do a post on Microsoft's community to find why your one system is only 7 days. I know I would probably never use the feature either but dont sound right for it to be different. I would imagine it would count down the days if you pause the updates, but I dont believe you had them paused, plus you havent had 1703 installed 28 days.
- GabeU8 years agoDistinguished Professor IV
Actually, I did just that, and, oddly enough, someone from Microsoft said it was strange that my laptop was showing 35 days as they should all show 7 days. When I brought up the fact that just about every single article written on the ability to pause updates references the 35 day amount and that their 7 day claim was spurious, I never recevied a reply.
I think the idea of it being 35 days is because most data capped services have 30 day data allotments. One doesn't have to wait the 35 days, but can pause them and then choose to perform the updates at any time within that time period.
With this said, something just dawned on me. I haven't seen any distinction as to whether pausing updates pauses the download of the update, or just the installation of it. If the latter, then the ability to do so wouldn't make any difference for someone on a capped service as it would use the data by downloading the updates and parking them for installation at a later date. It would only be an advantage for people who want to wait to install an update for whatever reason, whether fear of the updates causing problems and they want to wait to see what they do for others, or wanting to wait so they can perform a full backup before installing the updates. Or some other reason.
- maratsade8 years agoDistinguished Professor IV
"someone from Microsoft said it was strange that my laptop was showing 35 days as they should all show 7 days. When I brought up the fact that just about every single article written on the ability to pause updates references the 35 day amount and that their 7 day claim was spurious, I never recevied a reply. "
You've baffled them, GabeU. LOL
What I don't understand is WHY they don't just give everyone the ability to pause. Why is it included in Pro and Enterprise and not in Home? It just seems silly.
It's also silly to not want to update the machine. These days you have to keep your computer up to date at all times, or disconnect it from the Internet.
- maratsade8 years agoDistinguished Professor IV
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 guess this shows how little trust we have on Microsoft's programming skills.
- GabeU8 years agoDistinguished Professor IV
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.
Related Content
- 5 years ago
- 5 years ago
- 8 years ago
- 5 years ago