Windows 10: Windows 10 monthly rollup naming scheme?

ClaytonDM · Sep 20, 2018

Are the monthly windows 10 rollups now called "Cumulative Update for Windows 10 version ***" instead of "Security Monthly Quality Rollup for Windows 10?"

I'm really confused about this. I thought all the OS's received one big rollup each month with "Security Monthly Quality Rollup" in the title, and was classified as a security update. But I'm looking at available patches and only see quality rollups available for Windows 7/8 and the server OS's. For windows 10 all I can find is the cumulative updates and they are categorized as "updates."

In my origination we only approve security, critical, and definition patches, so this could be a big problem for us. I thought for sure in the past the Window's 10 monthly's used the same naming scheme and classification. Was this changed in the past few months?

:)

stinger608 · Sep 20, 2018

Microsoft is moving to a rollup model for Windows 7 SP1, Windows 8.1, Windows Server 2008 R2 ETC...

It was bound to happen!
However, this may indeed cure the Windows 7 slow update issue finally.

Here is a quick blurb on this subject:

As we previously announced, we are moving to a rollup model for Windows 7 SP1, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2 updates. These changes will take effect with the next Update Tuesday release, on October 11.

All supported versions of Windows will now follow a similar update servicing model, bringing a more consistent and simplified servicing experience. For those of you who manage Windows updates within your organization, it’s important that you understand the choices that will be available.

First, let’s review what we will release each month:

A security-only quality update

A single update containing all new security fixes for that month

This will be published only to Windows Server Update Services (WSUS), where it can be consumed by other tools like ConfigMgr, and the Windows Update Catalog, where it can be downloaded for use with other tools or processes. You won’t see this package offered to PCs that talk to Windows Update.

This will be published to WSUS using the “Security Updates” classification, with the severity set to the highest level of any of the security fixes included in the update.

This (like all updates) will have a unique KB number.

This security-only update will be released on Update Tuesday (commonly referred to as “Patch Tuesday”), the second Tuesday of the month. (This is also referred to as a “B week” update.)

A security monthly quality rollup

A single update containing all new security fixes for that month (the same ones included in the security-only update released at the same time), as well as fixes from all previous monthly rollups. This can also be called the “monthly rollup.”

This will be published to Windows Update (where all consumer PCs will install it), WSUS, and the Windows Update Catalog. The initial monthly rollup released in October will only have new security updates from October, as well as the non-security updates from September.

This will be published to WSUS using the “Security Updates” classification. Since this monthly rollup will contain the same new security fixes as the security-only update, it will have the same severity as the security-only update for that month.

With WSUS, you can enable support for “express installation files” to ensure that client PCs only download the pieces of a particular monthly rollup that they haven’t already installed, to minimize the network impact.

This (like all updates) will have a unique KB number.

This monthly rollup will be released on Update Tuesday (also known as “Patch Tuesday), the second Tuesday of the month. (This is also referred to as a “B week” update.)

A preview of the monthly quality rollup

An additional monthly rollup containing a preview of new non-security fixes that will be included in the next monthly rollup, as well as fixes from all previous monthly rollup. This can also be called the “preview rollup.”

This preview rollup will be released on the third Tuesday of the month (also referred to as the “C week”).

This will be published to WSUS using the “Updates” classification as an optional update. It will also be available via Windows Update (where all consumer PCs will install it) and on the Windows Update Catalog.

With WSUS, you can enable support for “express installation files” to ensure that client PCs only download the pieces of a particular monthly rollup that they haven’t already installed, to minimize the network impact.

Starting in early 2017 and continuing for several months, older fixes will also be added to the preview rollup, so it will eventually become fully cumulative; installing the latest monthly rollup will then get your PC completely up to date.

This (like all updates) will have a unique KB number.

Click to expand...

To read more on this specific subject and get links to other insights regarding this upcoming change:

https://blogs.technet.microsoft.com...-windows-7-and-windows-8-1-servicing-changes/

I'm not sure if this is a good move on Microsoft's side or not.

What does everyone think?

PA Bear - MS MVP · Sep 20, 2018

Have the monthly security update iso's been discontinued?

I'm the one who said Microsoft is months behind on Security Release iso Images.
Click to expand...

I'm afraid that's not what you said.

Cite:

Monthly rollups for Win8.1 and Win7 beginning October 2016

https://answers.microsoft.com/en-us...eginning/407000d2-bf3b-4a87-baab-9c5dc6a50fcb

Long story, short version:

Most updates for Win10 are cumulative so you don't need an ISO, just make sure the most recent Cumulative Update for Win10 (e.g., KB3200970) is installed.

The monthly security and quality rollups (AKA Security Monthly Quality Rollups) for Win8.1 & Win7 which began in October 2016 are also cumulative so you don't need an ISO - just make sure the most recent Security Monthly Quality Rollup (e.g., KB3197874;
KB3197868) is installed.

Ditto for the Security and Quality Rollups for various flavors of .NET Framework.

Extended Support (and updates) for Vista SP2 ends on 11 April 2017 so (apparently) MS isn't bothering with Rollups for Vista (even though Vista-specific .NET Framework rollups will be offered).

Welcome to the brave new world of Windows as a Service!

Brink · Sep 20, 2018

.NET Framework May 2017 Monthly Rollup

Today, we are releasing a new Security and Quality Rollup and Security Only Update for the .NET Framework.

Please see .NET Core May 2017 Updates for the .NET Core updates being released today.

Security

Microsoft Common Vulnerabilities and Exposures CVE-2017-0248

A security feature bypass vulnerability exists when Microsoft .NET Framework (and .NET Core) components do not completely validate certificates.

An attacker could present a certificate that is marked invalid for a specific use, but the component uses it for that purpose. This action disregards the Enhanced Key Usage extensions.

The security update addresses the vulnerability by helping to ensure that .NET Framework (and .NET Core) components completely validate certificates.

To learn more about this vulnerability, see Microsoft Common Vulnerabilities and Exposures CVE-2017-0248.

This update also contains security-enhancing fixes to the Windows Presentation Framework PackageDigitalSignatureManager component’s ability to sign packages with the SHA256 hash algorithm.

Quality and Reliability

There are no quality and reliability changes this month.

Getting the Update

The Security and Quality Rollup is available via Windows Update, Windows Server Update Services and Microsoft Update Catalog. The Security Only Update is available via Windows Server Update Services and Microsoft Update Catalog. The Windows 10 updates are integrated with the Windows 10 Monthly Update.

Docker Images

The Windows ServerCore and .NET Framework Docker images have also been updated. Pulling the latest image will update your local Docker image cache.

Downloading KBs from Microsoft Update Catalog

You can learn more about the releases from the table below. See .NET Framework Monthly Rollups Explained for an explanation on how to use this table to download patches from Microsoft Update Catalog.

[table][tr]Product Version Security and Quality Rollup KB Security Rollup KB [/tr] [tr][td]Windows 8.1 Windows Server 2012 R2[/td] [td]Catalog 4019114[/td] [td]Catalog 4019111[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6.2[/td] [td]4014507[/td] [td]4014587[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1[/td] [td]4014510[/td] [td]4014590[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014512[/td] [td]4014595[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td][/td] [td]4014581[/td] [/tr] [tr][td]Windows Server 2012[/td] [td]Catalog 4019113[/td] [td]Catalog 4019110[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6.2[/td] [td]4014506[/td] [td]4014586[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1[/td] [td]4014509[/td] [td]4014589[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014513[/td] [td]4014597[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4014503[/td] [td]4014577[/td] [/tr] [tr][td]Windows 7 Windows Server 2008 R2[/td] [td]Catalog 4019112[/td] [td]Catalog 4019108[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6.2[/td] [td]4014508[/td] [td]4014588[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1[/td] [td]4014511[/td] [td]4014591[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014514[/td] [td]4014599[/td] [/tr] [tr][td].NET Framework 3.5.1[/td] [td]4014504[/td] [td]4014579[/td] [/tr] [tr][td]Windows Server 2008[/td] [td]Catalog 4019115[/td] [td]Catalog 4019109[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6[/td] [td]4014511[/td] [td]4014591[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014514[/td] [td]4014599[/td] [/tr] [tr][td].NET Framework 2.0[/td] [td]4014502[/td] [td]4014575[/td] [/tr] [/table]

Known Issue with the April 2017 Update

The April 2017 Monthly Update contained a bug that caused the PowerShell Stop-Computer command to stop correctly functioning. This bug has since been fixed. You can get the fix in the following ways:

Using Windows 10

Install the May 2017 Update for Windows 10 (see link in the table above).

Using an earlier version of Windows

Wait for the next .NET Framework monthly update, which will include this fix. This approach is recommended if you are not experiencing this problem.

Install the specific fix for this issue, which you can find in the April 2017 Monthly Update post.

Note that the .NET Framework 4.7 contains the fix. If you are using Windows 10 Creators Update, you will still need to install the May 2017 Update (see link in the table above) to get this fix.

Previous Monthly Rollups

The last few .NET Framework Monthly updates are listed below for your convenience:

April 2017

December 2016

October 2016

Note: Previously released security and quality updates are included in today’s release.

More Information

You can read the .NET Framework Monthly Rollups Explained to learn more about how the .NET Framework is updated.
Click to expand...

Source: .NET Framework May 2017 Monthly Rollup | .NET Blog

Windows 10: Windows 10 monthly rollup naming scheme?

Windows 10 monthly rollup naming scheme?

Windows 10 monthly rollup naming scheme?

Windows 10 monthly rollup naming scheme?

Windows 10 monthly rollup naming scheme? - Similar Threads - monthly rollup naming

what is the naming scheme for ms account on windows login ?

what is the naming scheme for ms account on windows login ?

error KB5026415 Monthly Rollup - Windows 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2

Security Monthly Quality Rollup for Win 8.1 x64

Security Monthly Quality Rollup for Win 8.1 x64

Difference between monthly rollup and cumulative update?

Security Monthly Quality Rollups previous to applied Rollup shown as needed

.NET Framework May 2017 Monthly Rollup

Users found this page by searching for:

Windows 10 Monthly Rollup

win10 monthly rollup

where are windows 10 monthly rollup