Windows 10: error KB5026415 Monthly Rollup - Windows 2012 R2

GAVRN · Jun 9, 2023

Dear Last month, I installed the update "security monthly rollup for windows server 2012 r2 - KB5025285" on my windows 2012 r2 servers with no problems. However, this month, I tried to install the update "KB5026415 Monthly Rollup" and on all my servers it tells me that it does not apply. Does anyone know what could be causing this? thank you

:)

Arjun_2017 · Jun 9, 2023

Restart loop after installation of Windows Update for Server 2012 R2 - January 11, 2022—KB5009624 (Monthly Rollup)

Just posting here to advise Microsoft that one of our servers (hosted in AWS) went into a restart loop after installation of:

2022-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012 R2 for x64 (KB5009721)

2022-01 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5009624)

It would not boot until we ran the following from a rescue instance:

dism.exe /image:E:\ /cleanup-image /revertpendingactions

I know there have been similar issues reported with Domain Controllers, but this Server 2012 R2 instance was not a domain controller.

We're planning to hold off any further Windows Update installation on this server until the February patch Tuesday where we hope this issue will be resolved and the cumulative update will include anything we missed in January.
Click to expand...

Yes..You are right. This issue only started on Server 2012 .. My others servers 2016 & 2019 don't have any issues. But after installing the 2022-01 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5009624) latest security patch my Domain Server 2012 starts rebooting in a loop. Current fix is to uninstall the updates.

stinger608 · Jun 9, 2023

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?

Evin.Kaless · Jun 9, 2023

Security Monthly Quality Rollups previous to applied Rollup shown as needed

I've searched high and low and haven't been able to find an explainantion for this . . .

Why are Security Monthly Quality Rollups from previous months shown as needed when I have applied a more recent rollup? I'm seeing this in Windows 10 and 7, and Windows Server 2012/R2 and 2008 R2. And I'm seeing this in WSUS and Windows Update.

Windows 10: error KB5026415 Monthly Rollup - Windows 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2 - Similar Threads - error KB5026415 Monthly

Patch installation error on server 2012 R2

error KB5026415 Monthly Rollup - Windows 2012 R2

Re: Security Monthly Quality Rollup for Windows 2012 for x64-Based System

Re: Security Monthly Quality Rollup for Windows 2012 for x64-Based System

error update windows on Window Server 2012 R2

error update windows on Window Server 2012 R2

Windows Server 2012 R2

Windows Server 2012 R2

Windows Server 2012 R2 Error code 80072EFE