.NET Framework November 2021 Cumulative Update
Today, we are releasing the November 2021 Cumulative Update for .NET Framework.
Security
The November Security and Quality Rollup Update does not contain any new security fixes. See February 2021 Security and Quality Rollup for the latest security updates.
Quality and Reliability
This release contains the following quality and reliability improvements.
CLR1
- Addresses a change to how event providers are unregistered with ETW on disposal.
- Addresses a crash that could occur if a program exits while a ManagementEventWatcher is active.
Container Improvement
- Updates .NET Framework 4.8 to better support containers with the November 2021 update.
1 Common Language Runtime (CLR)
Getting the Update
The Cumulative Update Preview is available via Windows Update, Windows Server Update Services, and Microsoft Update Catalog.
Microsoft Update Catalog
You can get the update via Windows Update and Microsoft Update Catalog.
Customers that rely on Windows Update will automatically receive the .NET Framework version-specific updates. Advanced system administrators can also take use of the below direct Microsoft Update Catalog download links to .NET Framework-specific updates. Before applying these updates, please ensure that you carefully review the .NET Framework version applicability, to ensure that you only install updates on systems where they apply.
The following table is for Windows 10 and Windows Server 2016+ versions.
| Product Version | Cumulative Update | |
|---|---|---|
| Windows 11 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006363 |
| Microsoft server operating systems version 21H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006364 |
| Windows 10 21H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006365 |
| Windows 10 21H1 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006365 |
| Windows 10, version 20H2 and Windows Server, version 20H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006365 |
| Windows 10 2004 and Windows Server, version 2004 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5006365 |
| Windows 10 1809 (October 2018 Update) and Windows Server 2019 | 5007298 | |
| .NET Framework 3.5, 4.7.2 | Catalog | 5006368 |
| .NET Framework 3.5, 4.8 | Catalog | 5006366 |
| Windows 10 1607 and Windows Server 2016 | ||
| .NET Framework 3.5, 4.7.2 | Catalog | 5007192 |
| .NET Framework 3.5, 4.8 | Catalog | 5007152 |
The following table is for earlier Windows and Windows Server versions.
| Product Version | Security and Quality Rollup | |
|---|---|---|
| Windows 8.1, Windows RT 8.1 and Windows Server 2012 R2 | 5007301 | |
| .NET Framework 3.5 | Catalog | 4578953 |
| .NET Framework 4.5.2 | Catalog | 4578956 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | Catalog | 5007157 |
| .NET Framework 4.8 | Catalog | 5007154 |
| Windows Server 2012 | 5007300 | |
| .NET Framework 3.5 | Catalog | 4578950 |
| .NET Framework 4.5.2 | Catalog | 4578954 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | Catalog | 5007156 |
| .NET Framework 4.8 | Catalog | 5007153 |
| Windows 7 SP1 and Windows Server 2008 R2 SP1 | 5007299 | |
| .NET Framework 3.5.1 | Catalog | 4578952 |
| .NET Framework 4.5.2 | Catalog | 4578955 |
| .NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 | Catalog | 5007150 |
| .NET Framework 4.8 | Catalog | 5007149 |
| Windows Server 2008 | 5007302 | |
| .NET Framework 2.0, 3.0 | Catalog | 4578951 |
| .NET Framework 4.5.2 | Catalog | 4578955 |
| .NET Framework 4.6, 4.6.2 | Catalog | 5007150 |
Previous Monthly Rollups
The last few .NET Framework Monthly updates are listed below for your convenience:
- .NET Framework October 2021 Security and Quality Rollup
- .NET Framework August 2021 Security and Quality Rollup
- .NET Framework July 2021 Cumulative Update Preview
- .NET Framework July 2021 Security and Quality Rollup
Light
Dark
5 comments
The .NET Framework 4.8 update number for Windows 8.1 is wrong
5007152 is for Windows 10 version 1607
5007154 is for Windows 8.1
Thanks for calling this out, I’ve corrected the blog post in reference to these KB numbers.
It’s has not yet been rectified, nor Version 1607 been added to the table 🙂
This terminology seems new and not consistent:
Can we just say Windows Server 2022? It seems microsoft worked really hard to get rid of “server 21h2” terminology, so it seems unwise to call it that here.
This isn’t the place to give this kind of feedback. If my work experience is any indication, such name changes usually mean a change in the management structure. The new senior person made this change under significant internal political pressure. Hence, his or her decision is not open to discussion.
For us, it is always bad news.