Further simplifying servicing models for Windows 7 and Windows 8.1

[Brink]

In our announcement earlier in May, we introduced a Convenience Rollup update for Windows 7 SP1 and a shift to monthly rollups of non-security updates for Windows 7 SP1 and Windows 8.1. Based on your feedback, today we’re announcing some new changes for servicing Windows 7 SP1 and Windows 8.1. These changes also apply to Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. (Note: A rollup is multiple patches rolled together into a single update.)

Why we’re introducing Windows servicing changes

Historically, we have released individual patches for these platforms, which allowed you to be selective with the updates you deployed. This resulted in fragmentation where different PCs could have a different set of updates installed leading to multiple potential problems:

• Various combinations caused sync and dependency errors and lower update quality
• Testing complexity increased for enterprises
• Scan times increased
• Finding and applying the right patches became challenging
• Customers encountered issues where a patch was already released, but because it was in limited distribution it was hard to find and apply proactively

By moving to a rollup model, we bring a more consistent and simplified servicing experience to Windows 7 SP1 and 8.1, so that all supported versions of Windows follow a similar update servicing model. The new rollup model gives you fewer updates to manage, greater predictability, and higher quality updates. The outcome increases Windows operating system reliability, by eliminating update fragmentation and providing more proactive patches for known issues. Getting and staying current will also be easier with only one rollup update required. Rollups enable you to bring your systems up to date with fewer updates, and will minimize administrative overhead to install a large number of updates. (Note: Several update types aren’t included in a rollup, such as those for Servicing Stack and Adobe Flash.)

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.

Over time, Windows will also proactively add patches to the Monthly Rollup that have been released in the past. Our goal is eventually to include all of the patches we have shipped in the past since the last baseline, so that the Monthly Rollup becomes fully cumulative and you need only to install the latest single rollup to be up to date. We encourage you to move to the Monthly Rollup model to improve reliability and quality of updating all versions of Windows.

We are planning to add these previously shipped patches over the next year and will document each addition so IT admins know which KBs have been included each month.

Security-only updates

Also from October 2016 onwards, Windows will release a single Security-only update. This update collects all of the security patches for that month into a single update. Unlike the Monthly Rollup, the Security-only update will only include new security patches that are released for that month. Individual patches will no longer be available. The Security-only update will be available to download and deploy from WSUS, SCCM, and the Microsoft Update Catalog. Windows Update will publish only the Monthly Rollup – the Security-only update will not be published to Windows Update. The security-only update will allow enterprises to download as small of an update as possible while still maintaining more secure devices.

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.

Microsoft Update Catalog

The Microsoft Update Catalog website is being updated to remove the ActiveX requirement so it can work with any browser. Currently, Microsoft Update Catalog still requires that you use Internet Explorer. We are working to remove the ActiveX control requirement, and expect to launch the updated site soon.

.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. Additionally, the .NET Framework team will also release a security-only update on Microsoft Update Catalog and Windows Server Update Services every month.

We hope these changes further simply your patching of Windows 7 & 8.1 systems.

Read more: Further simplifying servicing models for Windows 7 and Windows 8.1

 

[Seffrid]

Unfortunately this means that there will be no choice any more as to which updates you install, so if one bricks users' machines you're also stuck with it unless you opt out altogether - which some may do. You won't simply be able to miss the offending month's update as it will be included in the next month's one.

It isn't quite as simple as it sounds, it is more than one single update each month as there will be a separate one for the combined .Net Framework updates as well as one for any e.g. Windows Updates upgrade.

Much in my view will depend not only on whether the combined updates do cause problems but also on whether we are still able long-term to choose whether and when to install each update (as opposed to the forced updating of Windows 10).

The full announcement is here:-

https://blogs.technet.microsoft.com...ervicing-model-for-windows-7-and-windows-8-1/

 

[groze]

Seffrid It does give you a choice if I am reading the site correctly. In October or later. You can choose to take the normal monthly roll-up or download just the security roll up updates and install them.

 

[Seffrid]

Yes but that security-only roll-up won't be offered under the basic WU service, you'll have to go looking for it and you still won't have more control over which elements of it you can install.

 

[ThrashZone]

Hi,
I don't believe I've had any issues with only important updates and is about all I install

If issues happen that is what system images are for

 

[Brds7t7]

It's going to be fun finding out what's causing an issue with an update now.
So, for people getting all their updates from WU, who then have an issue with that update, they then have to uninstall all that months security updates too?

 

[Seffrid]

It's going to be fun finding out what's causing an issue with an update now.
So, for people getting all their updates from WU, who then have an issue with that update, they then have to uninstall all that months security updates too?

Well, there will only be the one main update to uninstall so you will lose everything, but the component parts will all be installed again the following month as part of that month's cumulative/combined update so uninstalling it will only be a short-term solution until MS fix any issues.

As long as we have a choice over whether and when to install the updates there shouldn't be a problem, as from October it will be even more sensible than it already is to hold off on the updates until the dust has settled and it's clear whether there are any issues.

System images are fine for fixing systems broken by updates, but they're not for everyone. Best really to sit tight on updates for a couple of weeks, there's rarely any urgency about them.

 

[Brds7t7]

Yep, definitely a good idea to hold out for a few days before installing. I do that anyway, but even more reason to do it now.

I'm considering just manually installing those Security Update rollups instead, as I've skipped a lot of recommended updates anyway.

 

[ThrashZone]

Hi,
Imaging is for everyone or at least should be it's so freaking easy to do now days

 

[HammerHead]

Updates Smupdates

The fact you can't choose what to install, tells me they now can add the win 10 updates and you have no say. It is getting closer to rejecting all updates.

 

[Seffrid]

Hi,
Imaging is for everyone or at least should be it's so freaking easy to do now days

I've looked at various guides here and elsewhere over the last year or two and have found it incomprehensible really. If I recall correctly they started by saying I had to have a certain type of format and I don't have a clue whether I do or don't! I have two home computers with nothing that needs backing up other than the system files which aren't separately partitioned. At least being retired I have sufficient time available but a lot of ordinary computer users don't simply share my lack of knowledge, they don't have the time to make it a priority either.

 

[Lady Fitzgerald]

It's no wonder I refer to MS' CEO (Crazy Exasperating Officer) as Sadist Nutella. I'm so fed up with MS screwing around with Win 7. It's like if MS can't make us want Win 10, it will try to sneak it onto us. Since that failed, now the misbegotten lowlifes are trying to screw up Win 7 to make it more like Win 10. A pox on the control freaks of questionable parentage running the show (this post is the cleaned up version of my true feelings).

 

[Brds7t7]

Exactly what I was thinking Lady F.

Seems like they couldn't get enough users on to Windows 10 during the free year, so now they're bringing "Windows as a service" to users of 7 & 8.1 too.

I'm not feeling overly excited about this!

What I don't understand is the part where it says: "Based on your feedback".

Who are they getting this feedback from? Windows 10 insiders? :sarc:

 

[Lady Fitzgerald]

...What I don't understand is the part where it says: "Based on your feedback".

Who are they getting this feedback from? Windows 10 insiders? :sarc:

I suspect they may be referring to the lack of feed back due to people blocking telemetry updates, thus the lack of feedback occurring and they are putting spin on it to make it look like we requested through feedback the combined updates.

 

[Brds7t7]

I wonder if Windows Update will look like this in 6 months time:

 

[Seffrid]

Exactly what I was thinking Lady F.

Seems like they couldn't get enough users on to Windows 10 during the free year, so now they're bringing "Windows as a service" to users of 7 & 8.1 too.

I'm not feeling overly excited about this!

What I don't understand is the part where it says: "Based on your feedback".

Who are they getting this feedback from? Windows 10 insiders? :sarc:

The trouble is that if a lot of people post on forums that they hate the update system that requires them to vet every single update before installing it because malware from MS has become a bigger threat than malware from any other source, so why do they have to go through this monthly rigmarole, MS can legitimately say that simplifying the update system so we only need to install one update each month is merely responding to the feedback they've received !

 

[Brds7t7]

Depends on the user, personally, I like to pick and choose what goes on each of my systems. But then again, I'm not running in a huge enterprise environment.

I just don't like the idea of all updates being lumped into one. And even less so when it's both Security and Recommended updates.

The one upside is that at least we're not having to endure the forced automatic updates. That's one of the big reasons a lot of people chose not to move to 10. Forcing that on people might lead to a few shaky fists in MS direction!

In all honesty though, I can live without the recommended updates anyway and my systems all run fine with a lot of them skipped. I can happily just stick to installing Security Update rollups, after a delay of a week or two.

 

[groze]

​

Brds7t7

I really cant see Microsoft making windows 7 sp1 & 8.x forced automatic update the reason extended supports ends for both windows 7 & 8.x in a few years.

 

[Brds7t7]

No, I know the forced updates won't happen. I was being sarcastic about that.

I don't think it would be possible anyway, as they would have to make significant changes to the update system within the OS.

 

[Holmes177]

It's no wonder I refer to MS' CEO (Crazy Exasperating Officer) as Sadist Nutella. I'm so fed up with MS screwing around with Win 7. It's like if MS can't make us want Win 10, it will try to sneak it onto us. Since that failed, now the misbegotten lowlifes are trying to screw up Win 7 to make it more like Win 10. A pox on the control freaks of questionable parentage running the show (this post is the cleaned up version of my true feelings).

Agree 100% I have turned off automatic updates on all three of my computers running W7, and telling all my friends to do the same. MS is just screwing with W7 users. Why give W10 for free? Must be a lot more $ in it for MS. I seriously believe that there is intent on the part of MS to make W7 users' life pure Hell, in hopes that they will jump on W10. Thank you, NO, not now, not ever!