Unsolved
This post is more than 5 years old
3 Apprentice
•
15.3K Posts
0
1715
Cumulative Roll-Up Updates coming to Win7/8.1 starting October
The following information was excerpted from several sources, cited at the end of the post:
From October 2016 onwards, Microsoft will release a single CUMULATIVE Monthly Rollup Update for (each version of) Windows, that addresses both security issues and reliability issues... each update will supersede [and include] the previous month’s release, [so] you'll only need to install the latest single rollup to be up to date. Indeed, Microsoft says that over time, they will gradually add-on prior patches too, so that these monthly updates will eventually become fully cumulative; but it may take a year or more for the process of previous-patch-inclusion to be completed.
What this means is that individual patches will no longer be available --- to patch your system, you must accept ALL the releases for the month in a single patch... This change is rather significant... and considering that Microsoft has released a few bad patches in the past couple of years that have broken fundamental features of Windows, this change may not sit well with IT Pros [nor consumers].
Hardware drivers are the one potential exception; see How to stop Windows 7 automatically installing drivers https://support.microsoft.com/en-us/kb/2500967
Likewise, the .NET Framework will also follow the Monthly Rollup model [which will] deliver both security and reliability updates to all versions of the .NET Framework as a single monthly release. 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.
Sources:
http://securitygarden.blogspot.com/2016/08/icymi-major-windows-update-change.html?
==============================
Remarks: The one good thing to come out of this is that scanning/searching time for Windows Updates should be significantly reduced, as now, Windows only needs to access the one cumulative monthly update for your system.
It's also possible that a particular update may have failed in the past, because the user had previously opted-out of installing a necessary pre-requisite. This won't happen under the new system.
But yes, it's very scary to think that there may be a "rotten egg" update mixed-in among a large cumulative update... and users will have no choice but to swallow the entire batch, or repel it entirely.
RoHe
10 Elder
10 Elder
•
44.4K Posts
0
August 17th, 2016 18:00
Not good news because it means MS will be able to force-feed us with things we don't want, like the GWX nonsense they were constantly dishing out.
And I guess it means we should set Windows Update to Notify Only, and then wait a few days to see if any guinea pigs (ummm....users ) report a "rotten egg(s)" in the roll-up before we install them (with no guarantees they won't mess up any individual system).
joe53
2 Intern
2 Intern
•
5.8K Posts
0
August 17th, 2016 19:00
I have set WU settings to "Never check for for updates" for Win 7 for many years now, preferring to do it manually. This latest news just confirms that I will continue this practice.
RoHe
10 Elder
10 Elder
•
44.4K Posts
1
August 18th, 2016 11:00
Except now you won't be able to pick/choose which updates you want. It'll be all or none. So if there's one rotten egg, you'll have to delay the entire roll-up until MacroStupid fixes it, leaving you vulnerable to any exploits the other updates in the roll-up were designed to block. And who knows how long it may take MS to fix the one rotten egg..?
joe53
2 Intern
2 Intern
•
5.8K Posts
0
August 18th, 2016 14:00
Points well taken.
But it has been my habit for many years to avoid installing all updates (including security ones) from the WU website for between one and three weeks after their Patch Tuesday release. AFAIK, this has caused me no problems. After all, if a patch can wait for up to one month before it is released, it can wait a few weeks longer. The only updates I install immediately are the critical out-of-band security patches which fortunately are few and far between - and only after researching them.
You might recall the WGA Validation and WGA Notifications fiasco for XP users in 2005. They were foisted on unsuspecting users as high-priority security updates. Their only purpose was to detect pirated copies of Windows. Thousands of legitimate owners had their systems flagged due to false positives. I avoided that grief.
Under the new roll-ups, I have no faith that MS will avoid slipping in patches that benefit only MS.
My practice is a calculated risk. But better an unpatched system that works, than a patched rotten egg.
RoHe
10 Elder
10 Elder
•
44.4K Posts
0
August 18th, 2016 16:00
And even if it's not totally rotten, it can still cause problems. Every time MS updates the Win 10 Intel WiFi driver on one of my laptops, the connection speed drops and WiFi becomes almost unusable until I revert to the previously installed driver.
But when the identical laptop running Win 8.1 gets offered that same WiFi update, I avoid the problem by simply rejecting that one update while accepting the others.
Now, with roll-ups for Win 7 and 8.1, something may/will be rotten, but it won't be in Denmark... :emotion-4:
ky331
3 Apprentice
3 Apprentice
•
15.3K Posts
0
August 18th, 2016 17:00
Ron,
Have you tried the suggestions listed here; the first article claims it works for Windows 10 / 8 / 7 :
http://www.thewindowsclub.com/stop-windows-7-from-installing-drivers-automatically
http://winsupersite.com/windows-10/stop-automatic-driver-updates-windows-10
RoHe
10 Elder
10 Elder
•
44.4K Posts
0
August 22nd, 2016 18:00
Tried the suggestion in the post about Win 10, but I don't have the same options. All I have is Yes or No on that screen, with no choices under "No". This may be a change in the Anniv. Update from the prior build.
Anyway, it was already set to "No". So we'll see if that WiFi driver gets updated again... :emotion-41: