|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
So I’ve seen several questions on the Patch Management list about the naming of the Feature releases and the confusion about what release is what. Cl
[See the full post at: Patch Lady – Semi annual naming is still confusing]
Susan Bradley Patch Lady/Prudent patcher
I don’t do Windows 10. Participated in the Insiders program for a while and then gave it up when MS made it clear as day it wouldn’t undo its mistakes with that OS. So I don’t give a hoot what they call each new release. They could adopt an infantile adjective+animal system like the Linux folks do, for all I care.
That said, even if I did do Windows 10, I would have long since given up trying to follow their ever-shifting release naming “convention” (such as there is). Evidently the geniuses at Redmond have made the naming procedure so d*mned complicated that they have managed to confuse even themselves.
Serves them right.
Pity the folks who are stuck with this sorry excuse for an operating system.
(signed) Kubuntooth
“MS made it clear as day it wouldn’t undo its mistakes with that OS”
The biggest problem with WaaS in a nutshell
I like the previous naming scheme. Was not too confusing and considering they wouldn’t use beta testing branch and acceptable branch, it was at least a bit easier to remember than targeted or not. Well, I guess when you are forced to be a beta user, we could say you are targeted.
I think it’s documentation mistake, not change
it the same even with Office:
Targeted = FirstReleaseDeferred = Semi-Annual Channel (Targeted)
Broad = Deferred = Semi-Annual Channel
Definitely just a documentation mistake – but if even Microsoft can’t get it right, how can normal people figure it out?
Per Susan in Semi Annual Naming–
Clearly they are confusing even for Microsoft. Clearly they are confusing to the Admin crowd. Clearly they are confusing even for end users trying to figure out where they should be on what feature release.
Clearly not clear…
Carnak patching, and now this… Are we sure somebody at Microsoft isn’t supporting comedy writers on the down-low?
Non-techy Win 10 Pro and Linux Mint experimenter
I’m seeing Windows Update for Business clients which are not in the Targeted channel getting 1803 so it’s looking like it’s not just a typo on the release information web page.
Edit to remove HTML
They fixed it today. It’s back to Targeted.
Since this topic bubbled up, I observe what a difference a week makes.
What is the difference between an innocent typo, and a pre-announcement that can latter be pointed to as proof that Microsoft does communicate in advance of changes to routine?
It is not without reason that we have been trained to be hypercritical of all communications from Redmond.
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
