GWX cleared away as example develops in Windows redesigns

his hornet's home of rollup patches, .Net offal, and variety looks surprisingly like the wreckage we're hoping to find in October.

Microsoft has discharged 12 discretionary patches for Win7 and 8.1. No, this isn't the customary Patch Tuesday, nor the assigned nonsecurity antecedent First Week Patch Tuesday. It's a muddled Third Week Tuesday, which we used to get Out of Band. Bah, sham.

We're expecting enormous changes in fixing come this October, and this chaos - non-security rollups, subjective .Net patches, adjusting stack redesign, loads of variety - resembles a tragic review of the Ghost of Windows Patching Yet to Come.

However, there is some uplifting news.

Most Win 7 and 8.1 clients will be charmed to see the most captivating patch:

Promoting

KB 3184143 - Win 7, 8.1 - Removes the highly censured GWX framework (characterized as KB 3035583, KB 3064683, KB 3072318, KB 3090045, KB 3123862, KB 3173040, KB 3146449).

There are three major nonsecurity rollup patches (apparently like what we're going to find in October):

KB 3185278 - Win 7 and Server 2008 R2 - Nonsecurity overhaul rollup, which incorporates the EMET bug in MS16-111/KB 3175024. There's a protracted manual workaround and a Group Policy change to settle the bug portrayed in KB 3175024.

Yes, you read that accurately: Microsoft's Sept. 20 Win7 nonsecurity rollup incorporates a known bug in a before security patch. It additionally incorporates a patch for a bug in the accommodation rollup ("Win7 SP 2") KB 3125574. It would appear that you can't get one without the other.

KB 3185279 - Win 8.1 and Server 2012 R2 - comparably, a nonsecurity rollup patch for Win 8.1.

KB 3185280 - Server 2012 - likewise, a nonsecurity rollup patch for Server 2012.

At that point there's a mass of .Net patches. Obviously we're going to keep on getting these here and there, even in October:

KB 3179930 - Vista, Win 7 - .Net Framework 4.5.2 unwavering quality rollup

KB 3179949 - Vista, Win 7 - .Net Framework 4.6 and 4.6.1 unwavering quality rollup

KB 3184951 - Win 8 and Server 2012 just - .Net Framework 4.6, 4.6.1, and 4.5.2 unwavering quality rollup

KB 3186208 - Win 8.1 and Server 2012 R2 - comparative .Net Framework 4.6, 4.6.1, and 4.5.2 unwavering quality rollup

The compulsory overhaul to Windows Update:

KB 3177467 - Win 7 - Servicing stack upgrade

Another fix to a Microsoft-made bug:

KB 3181988 - Win 7 - Fixed bug in SFC checks brought about by the comfort rollup ("Win 7 SP2") KB 3125574

What's more, a few, uh, different patches:

KB 3063109 - Win 10 - "Hyper-V combination parts redesign for Windows virtual machines that are running on a Windows 10-based host." Revision 7. The official Windows Update list demonstrates this as a patch for Win 7 and 8.1. It doesn't have all the earmarks of being a piece of a Win10 aggregate redesign.

KB 3182203 - Win 7, 8.1 (and POSReady/XP) - Time zone change for Novosibirsk

The greater part of the patches are discretionary and will hence show up in Windows Update as unchecked - aside from the time zone change. Regardless it astounds me that Microsoft hasn't actualized a more rich approach to change time zones. Surmise they've been excessively occupied with GWX.

There's an example rising ... a harbinger, maybe. KB 3185278 and KB 3185279 - the two September redesign rollups - take after the example that I expect we'll see beginning in October. Microsoft has discharged the September overhaul rollups this month as Optional/unchecked, so they won't be consequently introduced. My speculation is we'll see those patches changed to Recommended in October.

For Win7, we saw a comparable example with KB 3172605 (July rollup) discharged as Optional on July 21, then changed to Recommended on Sept 20. KB 3179573 (August rollup) was discharged as Optional on Aug. 16, then changed to Recommended on Sept. 20. I'm speculating that 3172605 was kept down a month due to reported issues with Bluetooth (the KB article is presently up to Revision 10, never a decent sign).

On the off chance that that experience demonstrates commendable, the general example is to have a total overhaul (er, patch rollup) discharged as Optional, hold up a month to check whether anything detonates, and if not, then change it to Recommended the following month.

Regardless we're going to see a wide range of debris in the fixing cycle. Nathan Mercer's portrayal of the new post-October patchopalypse leaves a colossal number of subtle elements hanging, yet we realize that IE fixes won't fall into the month to month rollup, .Net patches will be united in an up 'til now unclear way, and time zone changes aren't leaving at any point in the near future.

Trust y'all appreciate the trek to Novosibirsk.