When Microsoft released Win10 Pro Creators Update, version 1703, it included the ability to control updates. Some would argue (and i still do) where the ability to readily block updates is an essential feature of 1703 - as well single reason individual Window 10 customers should spring for Win10 Pro, compared to Win10 Home.

Now, relating to the third time since its release in April 2017, Microsoft has simply ignored those blocks and moved machines to the Fall Creators Update, version 1709, all of the sudden or explanation.

Confirmation belonging to the latest fiasco arrived last Friday evening, with regard to a note appended to end with the Knowledge Base article, KB 4023814. There isn't an patch for KB 4023814. It's an "explainer" KB article titled, Some versions of Windows 10 display a notification to put on the latest version. It says:

If you're currently running Windows 10 Version 1507, Version 1511, Version 1607 or Version 1703, you can receive a notification that states that your device ought to have the latest security updates installed. Windows Update then will try to enhance your device?-

Windows 10 version 1607 and version 1703 commonly are not yet at "end and services information." However, they should be updated around the latest versions of Windows 10 to make certain that protection from the most recent security threats.

It was modified within the Friday night news dump period to connect:

Important

Microsoft realises that this notification was incorrectly mailed to some Windows 10 Version 1703 devices which in fact had a user-defined feature update deferral period configured. Microsoft mitigated this on March 8, 2018.

Which matches in with the KB update history logs, which show the patch KB 4023057, Update to Windows 10 Versions 1507, 1511, 1607, and 1703 for update reliability premiered on March 8.

Microsoft's convalescing at the not so great news game. Bad bug hits on Tuesday. Fixed on Thursday. On the other hand notice didn't fail until Friday evening. Making you wonder if the patching group presenting its own PR department.

To find out why Windows 10 consumers are so upset, this to look at the Windows Update advanced options in Win10 Creators Update, version 1703 (screenshot below).

Folks who want to take over version variations in Windows 10 set those advanced alternatives to (1) force Microsoft to hang about until a new version is said "Current Branch for Business," then (2) following the version has hit CBB, to visit an additional Twelve months before upgrading toward the new version, (3) hesitate on cumulative updates until A calendar month after they're sent out the Windows Update chute, and (4) overriding so much, hold off on all updates - cumulative updates and version changes - for 35 days.

Except, golly, Microsoft hasn't followed any sexual settings.
3 accidental Windows updates in 4 months

In mid-November 2017, all of a sudden, Windows Update started upgrading 1703 machines set to visit for CBB. That came as something of a shock to the telltale who figured Microsoft probably has warned them upfront. Microsoft finally fessed about the mistake, modifying KB 4048954 - for November 14 cumulative update - to state that, "Windows Pro devices over the Current Branch for Business (CBB) will upgrade unexpectedly." Microsoft didn't bother to correct the problem just before December 12 cumulative update. Gawrsh.

In mid-January 2018, Microsoft pushed many Win10 1703 customers onto 1709, even though had "feature update" deferrals set to 365 days. Microsoft decided which it would a lot more use the "Current Branch for Business" nomenclature, replacing it together with the nearly-identical "Semi-Annual Channel" terminology (Gregg Keizer has details). Somehow, in the midst of charging ahead to CBB, er, SAC, Windows Update forgot to fork out heed at the feature update deferral setting. Gawrsh two.

This month, Microsoft started rolling out a totally new feature, called "Update Assistant," that bypasses the Windows Update routines. One little problem: This month, Update Assistant forgot to perceive the feature update deferral setting and starting rolling 1709 off to machines set to block 1709 - even machines that are fitted with Windows Update disabled. Gawrsh three.

As we say, "I'm altering the offer. Pray I don't alter it ever again."

Microsoft's penance for the three transgressions? A great amount of oft-repeated advice:

Users who were affected by the niche and who upgraded to Windows 10 Version 1709 can revert a strong earlier version within Ten days of the upgrade. To start this, open Settings > Update & Security > Recovery, and next select Start out under Retreat to the previous sort of windows 10.

That's, if the rollback works properly.

While you're reading about Win10 Fall Creators Update's rapid acceptance rate - how it's been connected to more machines, faster, than any prior version of Win10 - keep the Gawrsh take into account mind. Three "accidental" upgrades in times past four month. Sure looks good along the version adoption graphs, eh?