In Case You Missed It: Major Windows Update Change Coming for Windows 7/8.1

[Corrine]

Further simplifying servicing models for Windows 7 and Windows 8.1 â€" Windows for IT Pros

Even though the information is provided by the Windows for IT Pros blog, the changes do, of course, apply to consumers.  Snippets quoted from the referenced article below:

Monthly Rollup

From October 2016 onwards, Windows will release a single Monthly Rollup that addresses both security issues and reliability issues in a single update. The Monthly Rollup will be published to Windows Update (WU), WSUS, SCCM, and the Microsoft Update Catalog. Each month’s rollup will supersede the previous month’s rollup, so there will always be only one update required for your Windows PCs to get current. i.e. a Monthly Rollup in October 2016 will include all updates for October, while November 2016 will include October and November updates, and so on. Devices that have this rollup installed from Windows Update or WSUS will utilize express packages, keeping the monthly download size small.

Update documentation changes

To bring consistency to the release notes model introduced with Windows 10, we will also be updating our down-level documentation to provide consolidated release notes with the Rollups for all supported versions of Windows. We’ll extend and provide release notes for monthly rollup updates and also the security-only updates that will be introduced from October 2016. 

.NET Framework Monthly Rollup

The .NET Framework will also follow the Monthly Rollup model with a monthly release known as the .NET Framework Monthly Rollup. The monthly .NET Framework Monthly Rollup will deliver both security and reliability updates to all versions of the .NET Framework as a single monthly release, targeting the same timing and cadence as Windows. It is important to note that the rollup for the .NET Framework will only deliver security and quality updates to the .NET Framework versions currently installed on your machine. It will not automatically upgrade the base version of the .NET Framework that is installed.

What does this mean to consumers with Windows 7 and/or Windows 8.1 devices?  Following is information I have gathered from various sources:

1.  All security and non-security fixes (reliability updates) will be in one cumulative update -- no choices!
2.  It won't be possible to uninstall one troublesome update, rather the entire cumulative update will need to be removed.
3.  Updates for the Microsoft Office, Servicing Stack and Adobe Flash won't be included in the rollups.
4.  Each monthly rollup will supersede the previous month's rollup.  (Thus a computer not powered on in October will get the October updates included in the November update.)
5.  As illustrated in the Windows 10 update history, documentation will be consolidated release notes with the rollups for all supported versions of Windows.

Comments:

1.  Without a doubt, be more proactive in maintaining system backups.
2.  Ensure you have a recent System Restore point.
3.  No, do NOT disable Windows Update as missing critical security updates could indeed have serious repercussions.  That said, at this point, it is unknown what changes may be made to WU options or whether the option to "Download updates, but let me choose whether or not to install them" option will be available if you wish to delay updates a couple of days beyond the first Tuesday of the month.
4.  I personally prefer to obtain device drivers directly from the manufacturer.  To change the driver update setting, see How to stop Windows 7 automatically installing drivers which also works on Windows 8.1.

[Digerati]

I think part of this change is brought on by Microsoft's confidence that, by an overwhelming majority, Windows Updates are installed without incident. Of course, there are exceptions but I believe the numbers are in the 1000s, not millions. And considering there are 1.5+ Windows users out there, that really is a phenomenal success. Of course that is no solace for those who do encounter problems. But odds are that person would have the problem if the update were in a monthly rollup, or released separately. Only a very tiny percentage of users have the technical expertise to actually determine if their specific system needs an update, or not. I note you can still delay installing them - at least for a few days - and listen for fallout. For sure Microsoft will be listening too, and [hopefully] be on top of any problems.

As for driver updates, I agree with Corrine and I prefer to get mine from the maker. That said, the driver updates Microsoft provides via WU are provided to MS from the makers. I am just not sure they are released in as timely a manner.

[Corrine]

via PA Bear:

FWIW Win8.1 & Win7 users will be able to avoid the non-security updates in the monthly rollup by manually installing the security-only update downloaded from Microsoft Update Catalog.

With Windows Update (AKA automatic updating) set to the "Notify Only" option, Win8.1 & Win7 users will be able to avoid the security/non-security rollup by hiding it.

[plodr]

The "bundle" concerns me as well as this

The monthly .NET Framework Monthly Rollup will deliver both security and reliability updates to all versions of the .NET Framework as a single monthly release,

I have chosen NOT to install above .NET 3.5 on three of the four Windows 7 computers in the house. I have all the .NET framework 4.5 and 4.6 upgrades hidden. I'm afraid if I have to install a bundle, MS will push the three computers to .NET 4, which I don't need for any programs.
My theory, if I don't need it, don't install it because it is one less thing that needs patching.

[ChuckRJr]

As mentioned in many discussions, These rollups stink.  I haven't been able to install since October.  I have looked into what is in the rollup and installed the security portion okay. I hope they address the issues.

[Corrine]

If you continue having problems, please get assistance from my friends at Sysnative who specialize in Windows Update problems.  Windows Update Forum Posting Instructions

[Digerati]

First, I second Corrine's suggested to let folks at Sysnative take a look. They really are Windows Updates experts.

Second, it is still vital to realize that the vast majority of users never have problems with Windows Updates. And even for most that do, they eventually work themselves out.

I have come to the conclusion, based on my experience with 5 computers here plus dozens more that I am responsible for, that if you just let Windows manage the updates, Windows Updates works. It is when we who are not Windows experts interfere Windows default settings that problems most often happen. I'm just saying... .

My theory, if I don't need it, don't install it because it is one less thing that needs patching.

And how do you determine if you need it or not?