.NET Framework May 2022 Cumulative Update
We are releasing the May 2022 Cumulative Update Preview Updates for .NET Framework.
Quality and Reliability
This release contains the following quality and reliability improvements.
WPF 1
- Addresses an issue where DWM failures can cause WPF’s render thread to fail. An app can opt-in to the behavior of ignoring all DwmFlush errors by setting a regkey in HKCUSoftwareMicrosoftAvalon.GraphicsIgnoreDwmFlushErrors or HKLMSoftwareMicrosoftAvalon.GraphicsIgnoreDwmFlushErrors whose name is the full path to the .exe that wants to opt-in, and whose DWORD value is 1.
- Addresses an issue of WPF apps not working with “Text Cursor Indicator” enabled when using RichTextBox.
Winforms
- Improved the hardened rendering of ComboBox controls on 64 bit architectures.
- Improved the reliability of data-bound ComboBox controls under assistive technology.
.NET Runtime
- Addresses several issues that would cause too many garbage collections under high memory load. The part of the change that reduces the number of blocking generation 2 collections under high memory load is considered a tuning change and is only active if the GCConserveMemory setting is set to a non-zero value. The part of the change that reduces needless generation 0 collections is considered an improvement and is always active.
- Adjusted GC Heap Hard Limit configuration, as well as processor interpretation for .NET Framework container scenarios.
Workflow
- Addresses an issue when users interact with the Workflow Designer they might encounter incorrectly disabled context menu items when right clicking on a variable in the component variables list.
1 Windows Presentation Foundation (WPF)
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 the Microsoft Update Catalog. For Windows 10, NET Framework 4.8 updates are available via Windows Update, Windows Server Update Services, Microsoft Update Catalog. Updates for other versions of .NET Framework are part of the Windows 10 Monthly Cumulative Update.
Note: Customers that rely on Windows Update and Windows Server Update Services 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 | 5013889 |
| Microsoft server operating systems version 21H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5013890 |
| Windows 10 21H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5013887 |
| Windows 10 21H1 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5013887 |
| Windows 10, version 20H2 and Windows Server, version 20H2 | ||
| .NET Framework 3.5, 4.8 | Catalog | 5013887 |
| Windows 10 1809 (October 2018 Update) and Windows Server 2019 | 5014090 | |
| .NET Framework 3.5, 4.7.2 | Catalog | 5013892 |
| .NET Framework 3.5, 4.8 | Catalog | 5013888 |
Previous Monthly Rollups
The last few .NET Framework Monthly updates are listed below for your convenience:
- .NET Framework May 2022 Security and Quality Rollup
- .NET Framework April 2022 Cumulative Update
- .NET Framework April 2022 Security and Quality Rollup Updates
- .NET Framework February 2022 Cumulative Update Preview
Light
Dark
4 comments
Why is it called “Preview” ?
We use “preview” because we release this only to RS5 and above in this release. It followed by release to all other supported OSs the following month Security and Quality Rollup release
Thanks for finally explaining it. I understand now, but I highly recommend not using the word Preview in the title of the update as it shows in Windows Updates, because experienced users and administrators might think it’s “beta”, and that the “real” release will be installed on that computer soon. I use the latest version of Windows 10, and it shows in Windows Update as “Preview”, which is misleading.
Thank you Dean for the feedback. I agree that the term “preview” is not perfect, but the intent here is to give customer an early view of the content that is going to be shipped broadly in the following month’s broad releases.