New Windows 7 and 8.1 patches usher later on of rollup updatingIt

Stays to be seen whether Microsoft's new try different things with nonsecurity patch rollups will work.

Recently Microsoft discharged an enormous arrangement of upgrades for Windows 7. Strip away the governmental issues, and KB 3125574 stands in as Windows 7 Service Pack 2. (On the off chance that Microsoft discharged a "genuine" Service Pack, one would anticipate that an augmentation will the Windows 7 end of bolster date.)

As a major aspect of that declaration, Microsoft engineer Nathan Mercer guaranteed us an adjustment in the way nonsecurity patches for Win7 and Win8.1 would be discharged:

Non-security upgrades for Windows 7 SP1 and Windows 8.1 (and also Windows Server 2008 R2 SP1, Windows Server 2012 and Windows Server 2012 R2) will be accessible as a month to month rollup (repairs moved together into a solitary overhaul). Every month, we will discharge a solitary redesign containing the majority of the non-security fixes for that month. We are rolling out this improvement - moving to rollup redesigns, to enhance the unwavering quality and nature of our overhauls. These fixes will be accessible through Windows Update, WSUS, and SCCM and in addition the Microsoft Update list. We trust this month to month rollup upgrade improves your procedure of keeping Windows 7, and 8.1 up and coming.

Right on prompt, the previous evening Microsoft discharged its first month to month rollup of patches for Windows 7 and Windows 8.1. You most likely woke up to another arrangement of patches in Windows Update. On your Windows 7 frameworks, you ought to see these discretionary, unchecked, patches:

KB 3123862: Updated abilities to overhaul Win7 and 8.

This is the third form of the same patch discharged on Feb. 3 and again on Feb. 9. As I clarified in February, it's a riddle fix that "ties into Windows 10 updates through means obscure." A long Reddit denunciation reveals much warmth however no insight into the patch, and I couldn't locate any official subtle elements. KB 3123862 initially showed up on Feb. 3 as a discretionary, unchecked patch. After a week it transformed into a "prescribed" checked patch, which means it introduced itself on PCs with Automatic Update empowered. No thought if the same destiny anticipates clients with this variant.

It's significant that prior incarnations of this patch complied with Microsoft's GWX-blocking registry settings. My tests demonstrate that this form takes after Microsoft's guidelines of engagement too. Running GWX Control Panel kills pushy Get Windows X conduct. In the event that you choose to introduce this discretionary fix however don't expect to move up to Windows 10 at any point in the near future, good sense should direct you to run GWX Control Panel and stop any Win10 yearnings from developing in any way.

              KB 3125574: Convenience rollup upgrade for Windows 7 SP1 and Windows Server 2008 R2 SP1.

Microsoft let us know yesterday that this "comfort overhaul" wouldn't take off through Windows Update. ("[It] is totally discretionary; it doesn't need to be introduced and won't be offered by means of Windows Update - you can pick regardless of whether you need to utilize it.") toward the beginning of today there gives off an impression of being a change of heart.

I've introduced KB 3125574 on a few test machines and can check that the GWX Control Panel blocking registry settings are respected. There's no GWX symbol in the framework plate, no GWX booked projects, no bloated concealed envelopes. KB 3125574 shows up as a solitary passage in my redesign history, in spite of the fact that I haven't yet taken the dive to uninstall it.

What concerns me most about KB 3125574 is that we don't have a complete rundown of which KB patches are incorporated into the uber-patch.

As portrayed in Mercer's TechNet blog entry, KB 3125574:

Contains all the security and non-security fixes discharged subsequent to the arrival of Windows 7 SP1 that are appropriate for general dispersion, up through April 2016. Introduce this one overhaul, and afterward you just need new redesigns discharged after April 2016.

              Which conveys me to the accompanying:

             KB 3156417: May 2016 overhaul rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1.

This is the first of the new type of nonsecurity patches. As per the KB article, it incorporates just two fixes, KB 3155039 and KB 3155218, both moderately considerate. Starting early Wednesday morning, the KB articles for those two fixes aren't accessible.

I introduced KB 3156417 on a test machine and found that lone the rollup envelope patch, KB 3156417, shows up in the rundown of introduced redesigns. That may exhibit an issue, in light of the fact that neither KB 3155039 nor KB 3155218 can be uninstalled independently. You either expel the entire rollup - both individual patches - or abandon it in place.

                There's additionally a tag-along patch:

         KB 3139923: MSI repair doesn't work when MSI source is introduced on a HTTP offer in Windows.

It would seem that this one was discharged independently - outside of KB 3156417 - in light of the fact that it applies to both Win7 and Win8.1. I figure the upgrade rollup idea still has a couple of characteristics.

The Windows 8.1 patches discharged incorporate KB 3123862 and 3139923, depicted prior, and also the accompanying:

         KB 3156418: May 2016 redesign rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2.

This patch is odd on the grounds that there was no past enormous rollup, and it isn't clear in the event that you need to introduce all past Win 8.1 patches before this one. KB 3156418 contains three patches "for Home clients" and 19 "for IT experts," all of which are recorded separately in the KB article.

This new way to deal with nonsecurity patches will most likely demonstrate divisive. Consider the possibility that one of the segment bits of an overhaul rollup crashes a few frameworks. Imagine a scenario in which one of the segments incorporates suspected "snooping" or "Win10 overhaul" parts that some Win 7 or 8.1 clients don't need.

Now, we don't have the foggiest idea.

Quality will be critical. In the event that the moved up patches all work immaculately, those with tinfoil caps (counting me) can make sense of how to adapt to the aftermath. Be that as it may, if there's an awful fix in a rollup, life's going to get extremely confused, rapidly.

Crunch the numbers. On the off chance that there's a 0.01 percent shot of any individual patch going haywire, and you stick 10 or 20 fixes together in a rollup, what are the odds the entire rollup moves over and plays dead?