-
Patch Lady – Is 1803 really Semi-Annual?
So back on June 14, Microsoft said that 1803 was available to all and others (ZDnet/Mary Jo Foley for one) said that 1803 moved to the semi-annual channel. Yet this page (which to be fair hasn’t been the most up to date and accurate about the release info) still says 1803 is Semi-annual targeted and has this cryptic footnote:
(1) Windows 10, version 1803 designation has been updated to reflect the servicing option available in the operating system and to reflect existing deferral policies. We recommend organizations broadly deploy the latest version of Windows 10 when they are ready, and not wait until the “Targeted” designation has been removed.
Several folks on the patchmanagement.org list have indicated that they too haven’t seen 1803 come down on a computer that has (remember it still has the old wording) Current branch for Business(*) and 0 day deferral.
Historically the declaration of CB/the new Semi Annual would mean that it could be offered up not that it suddenly got shoved out to all machines. Also in the past I’ve often been told that Microsoft still “throttles” updates during this period and dials it up more as the success rate goes up. Often you’ll see a feature release suddenly get offered up right after a compat/dynamic update got released as they fixed some blocking “thing” in the background. Which would be nice to know ahead of time that your system was or was not ready for the upgrade.
In this day and age where my Doctor, my Dentist, and even Comcast texts me ahead of time when an appointment is coming up, it would be nice if there was some more positive process that let you know how well your machine was ready for feature releases. It still feels too arbitrary and not intelligent enough. My last 1709 experience, I had a small hard drive machine say to me that it would have no problem upgrading and then it barfed EVERY time until I attached an external USB hard drive. Which reminds me I need to do that again as it’s still on 1709 and hasn’t gotten it’s 1803 update.
So are you seeing 1803 on a Current Branch for Business(*) deferral machine?
(*) I did it again, I called Current Branch for Business, Current Branch, sorry about that!