Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2019

Usage and Config Patch
1

Take a look at these 4 fixlets in MS catalog site.

https://www.catalog.update.microsoft.com/home.aspx

MS21-FEB: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 - Windows Server 2019 - .NET Framework 3.5/4.8 - KB4601055 (x64)
MS22-MAY: Cumulative Update for .NET Framework 3.5/4.8 for Windows Server 2019 - Windows Server 2019 - .NET Framework 3.5/4.8 - KB5013626 (x64)
MS22-NOV: Cumulative Update for .NET Framework 3.5/4.8 for Windows Server 2019 - Windows Server 2019 - .NET Framework 3.5/4.8 - KB5020615 (x64)
MS22-DEC: Cumulative Update for .NET Framework 3.5 and 4.8 for Windows Server 2019 - Windows Server 2019 - .NET Framework 3.5/4.8 - KB5020874 (x64)

None of them supersede any of the rest yet we have names that say “cumulative”. Makes zero sense.

2

I opened an advisory case with MS to get their take and will update with their response.

3

There is a known issue with some applications with the December .NET updates
See KB5022083

https://support.microsoft.com/en-us/topic/kb5022083-change-in-how-wpf-based-applications-render-xps-documents-a4ae4fa4-bc58-4c37-acdd-5eebc4e34556

4

The supersede issue has been present for years apparently.

5

This is being escalated up to QFE team at MS to see if they will update the supersede chains for .NET fixes like these.

If Bigfix continues to use the MS Catalog, then we are subjected to weaknesses when the QFE team will not update the MS Catalog for supersede chains.

If Bigfix would use the Windows Update API, we would not be in this situation.