Microsoft’s support runs all over a place, though yesterday an announcement from ‘Softie John Cable is widely interpreted as observant that Windows 10 Fall Creators Update, chronicle 1709, is now prepared for business use. Gregg Keizer has details.
Fall Creators Update (version 1709) is entirely accessible for all concordant inclination using Windows 10 worldwide! Full accessibility is a final proviso of a rollout process. … Enterprise business following this same targeted proceed for the Semi-Annual Channel can also entirely muster when ready.
While that isn’t, literally, a “Current Branch for Business” imprimatur that we’ve had in a past, as Keizer explains, it’s a closest we’re going to get.
Tellingly, Microsoft’s central Windows 10 recover information page (see screenshot) is all over a map. While Cable’s proclamation seems to appropriate 1709 as a “Semi-Annual Channel” recover (formerly Current Branch for Business), in fact Microsoft’s page still shows it as “Semi-Annual Channel (Targeted)” that corresponds to a aged “Current Branch.”
Old vernacular and new vernacular are sparse willy-nilly on a site. Michael Niehaus explained a difference in mumbo-jumbo realignment, behind in July.
Whether 1709 is Current Branch, Current Branch for Business, or Entirely Revised New Semi-Annual Uncharted Territory Branch (Targeted), those of us using Win10 1703 who don’t wish to pierce to 1709 are faced with a discouraging prospect: how to tell Windows Update to keep a mitts off, until we’re good and prepared to pierce to 1709?
The Win10 Pro (and Enterprise) 1703 Update Advanced Options choices, as shown in a screenshot, includes 4 settings.
Microsoft has altered a definitions twice, though during this indicate it appears as if:
- The Current Branch for Business environment has no meaning, as of yesterday.
- The feature refurbish deferral setting is ostensible to strengthen we from forced chronicle changes for a indicated series of days.
- The quality refurbish deferral setting is ostensible to strengthen we from forced Automatic Updates by a indicated series of days.
- The Pause Updates environment turns off all updates for 35 days.
As we might recall, Microsoft completely abandoned a Current Branch for Business setting in November. Ultimately, Microsoft acknowledged a “known issue” and bound it in December. Meanwhile, many who told 1703 to reason off on updating were pushed forward to 1709 anyway. At that point, it became apparent that we had to run a underline refurbish deferral adult to 365, to equivocate removing pushed.
Susan Bradley, in Windows Secrets Newsletter, reported in Nov that a problem might have been with a user interface (as in a screenshot above) not being rightly picked adult by a installer:
Some tiny business admins had 1709 commissioned on systems where they suspicion they had pushed off a refurbish for several months. Microsoft concurred that a 1703 chronicle might accept a 1709 underline refurbish when we are not awaiting it. They betrothed to repair a emanate in an arriving update. we privately consider a emanate is selecting to defer a underline refurbish in a GUI is not “sticking.” If we use a internal organisation process to pull off a underline refurbish that seems to be sticking.
Now, I’m observant complaints that those with a feature update deferral set during 365 are removing pushed onto 1709 anyway. Is it probable that Bradley’s “sticking” problem has returned?
I’m not observant that Fall Creators Update is bad. I’m observant that it’s still too early to tell. For example, final month’s 1709 accumulative update, KB 4054517 was a disaster. Microsoft itself says that a Dec accumulative refurbish had two famous issues:
- Update designation might stop during 99% and might uncover towering CPU or hoop utilization
- Windows Update History reports that KB4054517 unsuccessful to implement since of Error 0x80070643
And we all know about a many problems with this month’s Win10 accumulative updates in general, and 1709’s in particular.
In addition, there are well-documented problems with Asus and Lenovo Wi-Fi chipsets. Homegroups get hosed (Microsoft’s deprecating Homegroups in 1803 anyway), there are reported problems with behind printing, and a garland of nitpicking anomalies.
All in all, a Fall Creators Update has been remarkably fast — though many folks wish to confirm for themselves when a ascent gets installed. With “Current Branch for Business” deferral now, apparently, rolled over, it’s an open doubt how to best keep 1709 during bay.
Questions? Comments? Observations? We’re all ears on the AskWoody Lounge.