Windows 11 Out-of-Band Non-Security Cumulative Update

Corrine

Administrator,
Microsoft MVP,
Security Analyst
Staff member
Joined
Feb 22, 2012
Posts
12,391
Location
Upstate, NY
Microsoft released an out-of-band non-security update with quality improvements for Windows 11.

The Key changes in KB5019311 (OS Build 22621.525) include:

  • Addresses localization issues for some setup files. These issues might stop you from creating installation media for non-English languages.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

Update: To get the update, go to Settings > Update & Security > Windows Update > Advanced Options > Optional Updates. The link to download and install the update can be found in the Optional updates available area. To get the standalone package for this update, go to the Microsoft Update Catalog website.
 
I don't understand why they released this "out-of-band". To me, "out-of-band" updates should be restricted to updates that address "critical" bug and/or "critical" zero-day type security exploits only. That is, to updates the need to be installed immediately.

This reminds me of back in the day when I was still in the military, everyone in maintenance started abusing the supply system by ordering replacement parts "Priority". They did this to get the parts delivered faster in order to avoid chalking up excessive "down time" statistics on their records - which they felt made them look bad. This was happening even when "the mission" was still being fully supported with secondary systems, and tertiary systems were still available.

Before long, the entire DoD supply chain was inundated with "Priority" parts which, in effect, slowed down and clogged up the whole system to where Priority became the new "Routine". If you really needed a part because the mission was "down" and no redundancy was available, the part either took excessively long to arrive, or you were forced to order the part "MICAP" - Mission Impaired Capability Awaiting Parts. This ordering status is meant to be used only for "critical", mission is down, outages. This is when folks in Supply drop everything, reach out across the globe to find a replacement part, rush it out to an awaiting plane that then flies it to where it needs to go NOW!

Once at the destination, the responsible technician, who is standing by, waiting for delivery, immediately installs the part and restores the mission back to full capability.

You can easily see how, when abused, this became a HUGE waste of resources (and taxpayers $$$).

Finally, the "big doggies" high up the Logistics ladder put a halt to that practice and everyone had to really justify ordering parts "Priority". If they couldn't, it went out Routine. And what happened? After just a few short weeks, the supply pipeline became unclogged. "Routine" parts started arriving in 3 - 5 days, a week at the most. And "Priority" parts often arrived in 48 hours or less - just like the system was supposed to work.

My point? I see nothing in that KB to indicate this is a "critical", let alone "priority" issue that needs immediate ("out-of-band") release.

What I see is potential "abuse" of the "out-of-band" release process that, if allowed to continue, will desensitize users to the point they will not take such releases seriously, and therefore will allow their systems to lag behind in updates. And sooner or later, truly critical updates that should be installed immediately, are not. :(

Has Microsoft forgotten what happened when the boy kept crying "wolf"?
 
Actually, I should have included that it is an optional update. Users of non-English language systems are affected in that there were issues for Windows setup files which was preventing the successful creation of installation media.
 
I saw that it was optional, I don't think that matters for what I was saying. And from the KB and that scenario, it really didn't affect that many people. That is, not all non-English systems were affected. I note it said "some" files and "might" stop some users from creating the media. That, to me, seems to affect only some of those users - unless they down-played the impact. And in that case, shame on Microsoft for not being totally honest.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top