New
#10
I did and it worked fine, thanks.
Hopefully we can pause more than 7 days in future though.
Perhaps at the same time we can figure out what the "Enabling this policy..." box is for.
It looks to do something remarkably similar to the slider above it although it isn't clear what policy it is talking about :)
If you have an Insider build installed, you wouldn't have the defer updates feature available.
Windows Update - Defer Feature and Quality Updates in Windows 10 Windows Update Activation Tutorials
Hi,
That's why 1703 is more straight forward than 1709 to me branch for business is where i was always set
I just added the 365 option since fall creators was pushing out
Mostly for good measure I switched it
I have one install on fall creator and uefi install it's just flakier than 1703 :/
Now @ThrashZone's screenshot is clearly 1703, so why does it say 'Temporarily pause updates for up to 35 days'?
Hi,
Pause is just another option that 1703 offered :)
Bad because it stops updates entirely after 35 days and one must update.
The 365 delay does not stop security updates just other newer builds from downloading and installing
After my recent disaster with Windows Update, I'm paying closer attention to the various ways (including gpedit or Services, if need be) to delay the installation and/or downloading of updates. So, I have the following question, which my research (including here) has failed to make completely clear to me: If a user has chosen (1) to defer feature updates for 365 days and quality updates for 30 days (the current maximums) *and* (2) to "pause" updates from being installed for 35 days, do these things (that is, choice #1 and choice #2 above) interact with or influence one another and, if so, how?
Thank you!
Hello devnull, :)
Pausing updates will pause all updates until you un-pause for up to seven days.
Deferring updates doesn't include all updates, but would be more long term. Think deferring Cumulative Updates.
Windows Update - Defer Feature and Quality Updates in Windows 10 Windows 10 Tutorials
Feature updates
With Windows 10, Microsoft will package new features into feature updates that can be deployed using existing management tools. Because feature updates are delivered more frequently than with previous Windows releases — two to three times per year rather than every 3–5 years — changes will be in bite-sized chunks rather than all at once and end user readiness time much shorter.
Quality updates
Monthly updates in previous Windows versions were often overwhelming because of the sheer number of updates available each month. Many organizations selectively chose which updates they wanted to install and which they didn’t, and this created countless scenarios in which organizations deployed essential security updates but picked only a subset of nonsecurity fixes.
In Windows 10, rather than receiving several updates each month and trying to figure out which the organization needs, which ultimately causes platform fragmentation, administrators will see one cumulative monthly update that supersedes the previous month’s update, containing both security and nonsecurity fixes. This approach makes patching simpler and ensures that customers’ devices are more closely aligned with the testing done at Microsoft, reducing unexpected issues resulting from patching. The left side of Figure 1 provides an example of Windows 7 devices in an enterprise and what their current patch level might look like. On the right is what Microsoft’s test environment PCs contain. This drastic difference is the basis for many compatibility issues and system anomalies related to Windows updates.
Last edited by Brink; 24 Feb 2018 at 12:32.
Shawn, thank you, but what if you have all three of the settings configured in the way I described---that is, (1) defer feature updates for 365 days and quality updates for 30 days (the current maximums) *and* (2) "pause" updates from being installed for 35 days---isn't there an inherent contradiction there?