Over the weekend, I heard many complaints from people who were unceremoniously upgraded from Windows 10 Fall Update (version 1511) to the Anniversary Update (version 1607). The upgrade took place even though they had explicitly instructed Windows 10 to defer upgrades.
Win10’s proclivity for unexpected updates and restarts has long been a source of frustration, and the settings that surround upgrades and updates confuse many – including me. But there’s a reason why so many were upgraded over the weekend while trying hard to stem the tide.
To make some sense of this, let’s start with the basics.
So far Windows 10 has :
, but the basic idea is that Win10 users bang around on the CB until Microsoft feels comfortable to CBB. Once a version is CBB-worthy, it’s been thoroughly tested. Before that, well, you can draw your own conclusions.
The “for Business” bit is a red herring as any Windows user who’s sufficiently wily can hold off on installing upgrades until a CB version has been awarded CBB status. (LTSB is a different animal entirely, suitable for “Specialized systems – such as PCs that control medical equipment, point-of-sale systems, and ATMs.”)
last Friday, Jan. 19, or 62 days after it hit CBB. Microsoft’s intentionally vague about how long they’ll take to go from CBB to fully published.
When Microsoft publishes the official CBB version:
- Windows Update unhides the upgrade, if it was . This is the way “hide” has functioned in Windows Update for many years: If there’s a new version of a patch released (in this case, “Feature update to Windows 10, version 1607”), previous attempts to hide the patch get overridden.
For many years, Microsoft documented new versions of old patches on the . This time, we weren’t so lucky.
- Those who have “Defer Upgrades” checked in Windows Update (Start > Settings > Update & security > Windows Update) get upgraded to the next version, unless there’s an update server such as WSUS or SCCM in the middle, or a Group Policy has been set to even more. By using GPEdit on Win10 Pro v 1511 machines, you can tell Windows to avoid 1607 for eight more months – until Sept. 19, 2017, presumably – using the in Computerworld.
The upshot is that most folks who were holding off 1607 by either using wushowhide or by checking the “Defer Upgrades” box in version 1511 had their choice overridden over the weekend. That came as quite a shock, with many people complaining about how their machines went down for the count.
There’s no way to predict how long a version will take to go from CB to CBB. There’s no way to predict how long a version will take to go from CBB to fully published. We had no advance warning when 1511 was published on the VLSC servers. We had no advance warning when 1607 was published on the VLSC servers.
For those of you who were upgraded and didn’t want to be – sorry about the hour or two takeover of your machine – your best bet is to , then use either (for those of you with Win10 Pro) or to hide “Feature update to Windows 10, version 1607.”
There’s another wrinkle you should know about.
Microsoft has another complex formula for determining when a release of Windows 10 will reach “end of life” – the point at which no more cumulative updates are offered. EOL occurs the later of either of the following:
- Eighteen months after the version is released (which is to say, when it becomes Current Branch)
- Sixty days after the next version is published to the VLSC server
In this case, that means version 1507 – the original, RTM version of Win10 – will no longer be supported after March 20, 2017, the “60 days after next version is published” limit.
The definitions, descriptions, settings, and durations are all evolving, and it looks like we’ll have yet another bunch of changes for version 1704. If you got fooled this time, don’t feel too bad about it, but watch out for next time.
The discussion continues on .