Windows 10: Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

CHK-CIT · Nov 6, 2021

Hi there,We are running Windows 10 Enterprise 1903. We wants to upgrade all Windows 10 to version 21H2. We configured our Windows 2012 R2 WSUS 6.3.9600 to select Product Windows 10 1903 and Category Upgrade. We found Feature update for Windows 10 cosumer but no Feature Update to Windows 10 Enterprise, version 21H2 is available for upgrade.May any of your experts give me any advice?Thx.AP

:)

MichaelC_WSN · Nov 6, 2021

Windows 10 Creators Update (version 1703) Failing from Windows 2012 R2 WSUS server with error 0x8024001e

The majority of my Windows 10 Enterprise workstation did get the version 1703 Creators Updates without any issues though.

I did have to make the change in my Windows 2012 R2 WSUS server's IIS Manager and add in the .esd MIME type for it to work.

However there are some Windows 10 Enterprise workstations are getting the following error when attempting to install the Windows 10 Creators Update, version 1703:

"Installation Failure: Windows failed to install the following update with

error 0x8024001e: Feature update to Windows 10 Enterprise, version 1703, en-us"

I've deleted the C:\$WINDOWS.~BT folder as some others have suggested to no avail.

What else can be done?

***Post moved by the moderator to the appropriate forum category.***

stinger608 · Nov 6, 2021

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?

Ken Ashmore · Nov 6, 2021

Error Code 800f0922 when applying patch KB4507448 on Windows 2012 R2

Windows Server 2012 R2 version 6.3 (build 9600)

Windows 10: Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2 - Similar Threads - 2012 WSUS 9600

Networking Issue from KB5015874 on Server 2012 R2 Version 6.3, Build 9600

Networking Issue from KB5015874 on Server 2012 R2 Version 6.3, Build 9600

KB2919442 will not install on Windows Server 2012 R2 Built 9600

KB2919442 will not install on Windows Server 2012 R2 Built 9600

feature update to windows 10 version 21H2

feature update to windows 10 version 21H2

feature update to windows 10 version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2

Windows 2012 R2 WSUS 6.3.9600 No Feature Update to Windows 10 Enterprise, version 21H2