Windows 10: .NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

vapor.trails · Nov 16, 2021

Since .NET Framework 4.5.2, 4.6, 4.6.1 meets the End of Support on April 26, 2022 and they strongly recommend we migrate to at least .NET Framework 4.6.2 or higher, I would like to inquire a small point. If I update to .Net 4.8 will I need to install Security and Quality Rollup for .NET Framework from the past? I have a memo of prior rollup KB#s from 2020-01 on... Will Windows Update provide essential Security Rollups for 4.8 NET Framework, or do I search and install? - might the Quality Rollups for .NET Frameworks be Cumulative? My Win 8.1 .NET 4.8 installer is still hidden KB448610

:)

Brink · Nov 16, 2021

.NET Framework May 2017 Preview of Quality Rollup

We released the May Preview of Quality Rollup for the .NET Framework.Preview of Quality Rollup releases are recommended for businesses that want to use and/or preview quality improvements as soon as they become available. These same quality improvements will typically be included in the following Security and Quality Rollup. You can read the .NET Framework Monthly Rollups Explained to learn more about how the .NET Framework is updated.

Quality and Reliability

This release contains 40 fixes from across the following product areas (number of fixes per area included below):

ASP.NET (8)

BCL (2)

CLR (8)

Entity Framework (1)

Networking (1)

SQL Client (4)

Windows Forms (1)

WPF (15)

Updates were made in the following .NET Framework releases. Release notes have been updated (for versions that have release notes).

.NET Framework 4.6.2 (diff)

.NET Framework 4.6.1 (diff)

.NET Framework 4.6 (diff)

.NET Framework 4.5.2

.NET Framework 3.5

Note: This release does not apply to .NET Framework 4.7 and Windows 10. Please install the May 2017 Quality Rollup to get the same fixes if you are using .NET Framework 4.7 and/or Windows 10.

Security

This release does not contain any new security changes.

It contains previously released security changes, including the fixes in the NET Framework May 2017 Monthly Rollup.

Getting the Update

The Preview of Quality Rollup is available via Windows Update, Windows Server Update Services and Microsoft Update Catalog.

Docker Images

The Windows ServerCore and .NET Framework images have not been updated for this release.

Downloading KBs from Microsoft Update Catalog

You can download patches from the table below. See .NET Framework Monthly Rollups Explained for an explanation on how to use this table to download patches from Microsoft Update Catalog.

[table][tr]Product Version Preview of Quality Rollup KB [/tr] [tr][td]Windows 8.1 Windows Server 2012 R2[/td] [td]Catalog 4019290[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2[/td] [td]4014604[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014611[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4014598[/td] [/tr] [tr][td]Windows Server 2012[/td] [td]Catalog 4019289[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2[/td] [td]4014602[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014612[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4014594[/td] [/tr] [tr][td]Windows 7 Windows Server 2008 R2[/td] [td]Catalog 4019288[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2[/td] [td]4014606[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014613[/td] [/tr] [tr][td].NET Framework 3.5.1[/td] [td]4014596[/td] [/tr] [tr][td]Windows Server 2008[/td] [td]Catalog 4019291[/td] [/tr] [tr][/tr] [tr][td].NET Framework 4.6[/td] [td]4014606[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4014613[/td] [/tr] [tr][td].NET Framework 2.0[/td] [td]4014592[/td] [/tr] [/table]

Previous Monthly Rollups

The last few .NET Framework Monthly updates are listed below for your convenience:

May 2017

April 2017

December 2016

Note: Previously released security and quality updates are included in today’s release.
Click to expand...

Source: .NET Framework May 2017 Preview of Quality Rollup | .NET Blog

Brink · Nov 16, 2021

.NET Framework May 2018 Preview of Quality Rollup

Today, we are releasing the May 2018 Preview of Quality Rollup.

Quality and Reliability

This release contains the following quality and reliability improvements.

CLR

Resolves an issue in WindowsIdentity.Impersonate where handles were not being explicitly cleaned up. [581052]

Resolves an issue in deserialization when using a collection, for example, ConcurrentDictionary by ignoring casing. [524135]

Removes case where floating-point overflow occurs in the thread pool’s hill climbing algorithm. [568704]

Resolves instances of high CPU usage with background garbage collection. This can be observed with the following two functions on the stack: clr!*gc_heap::bgc_thread_function, ntoskrnl!KiPageFault. Most of the CPU time is spent in the ntoskrnl!ExpWaitForSpinLockExclusiveAndAcquire function. This change updates background garbage collection to use the CLR implementation of write watch instead of the one in Windows. [574027]

Networking

Fixed a problem with connection limit when using HttpClient to send requests to loopback addresses. [539851]

WPF

A crash can occur during shutdown of an application that hosts WPF content in a separate AppDomain. (A notable example of this is an Office application hosting a VSTO add-in that uses WPF.) [543980]

Addresses an issue that caused XAML Browser Applications (XBAP’s) targeting .NET 3.5 to sometimes be loaded using .NET 4.x runtime incorrectly. [555344]

A WPF application can crash due to a NullReferenceException if a Binding (or MultiBinding) used in a DataTrigger (or MultiDataTrigger) belonging to a Style (or Template, or ThemeStyle) reports a new value, but whose host element gets GC’d in a very narrow window of time during the reporting process. [562000]

A WPF application can crash due to a spurious ElementNotAvailableException. [555225]
This can arise if:

Change TreeView.IsEnabled

Remove an item X from the collection

Re-insert the same item X back into the collection

Remove one of X’s subitems Y from its collection
(Step 4 can happen any time relative to steps 2 and 3, as long as it’s after step 1. Steps 2-4 must occur before the asynchronous call to UpdatePeer, posted by step 1; this will happen if steps 1-4 all occur in the same button-click handler.)

Note: Additional information on these improvements is not available. The VSTS bug number provided with each improvement is a unique ID that you can give Microsoft Customer Support, include in StackOverflow comments or use in web searches.

Getting the Update

The Preview of Quality Rollup 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.

[table][tr]Product Version Preview of Quality Rollup KB [/tr] [tr][td]Windows 8.1 Windows RT 8.1 Windows Server 2012 R2[/td] [td]Catalog 4103473[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4095875[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098974[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4098972[/td] [/tr] [tr][td]Windows Server 2012[/td] [td]Catalog 4098968[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4095872[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098975[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4098971[/td] [/tr] [tr][td]Windows 7 Windows Server 2008 R2[/td] [td]Catalog 4103472[/td] [/tr] [tr][td].NET Framework 3.5.1[/td] [td]4095874[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098976[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4096234[/td] [/tr] [tr][td]Windows Server 2008[/td] [td]Catalog 4103474[/td] [/tr] [tr][td].NET Framework 2.0, 3.0[/td] [td]4095873[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098976[/td] [/tr] [tr][td].NET Framework 4.6[/td] [td]4096234[/td] [/tr] [/table]
Click to expand...

Read more: .NET Framework May 2018 Preview of Quality Rollup | .NET Blog

Brink · Nov 16, 2021

.NET Framework May 2018 Preview of Quality Rollup

Today, we are releasing the May 2018 Preview of Quality Rollup.

Quality and Reliability

This release contains the following quality and reliability improvements.

CLR

Resolves an issue in WindowsIdentity.Impersonate where handles were not being explicitly cleaned up. [581052]

Resolves an issue in deserialization when using a collection, for example, ConcurrentDictionary by ignoring casing. [524135]

Removes case where floating-point overflow occurs in the thread pool’s hill climbing algorithm. [568704]

Resolves instances of high CPU usage with background garbage collection. This can be observed with the following two functions on the stack: clr!*gc_heap::bgc_thread_function, ntoskrnl!KiPageFault. Most of the CPU time is spent in the ntoskrnl!ExpWaitForSpinLockExclusiveAndAcquire function. This change updates background garbage collection to use the CLR implementation of write watch instead of the one in Windows. [574027]

Networking

Fixed a problem with connection limit when using HttpClient to send requests to loopback addresses. [539851]

WPF

A crash can occur during shutdown of an application that hosts WPF content in a separate AppDomain. (A notable example of this is an Office application hosting a VSTO add-in that uses WPF.) [543980]

Addresses an issue that caused XAML Browser Applications (XBAP’s) targeting .NET 3.5 to sometimes be loaded using .NET 4.x runtime incorrectly. [555344]

A WPF application can crash due to a NullReferenceException if a Binding (or MultiBinding) used in a DataTrigger (or MultiDataTrigger) belonging to a Style (or Template, or ThemeStyle) reports a new value, but whose host element gets GC’d in a very narrow window of time during the reporting process. [562000]

A WPF application can crash due to a spurious ElementNotAvailableException. [555225]
This can arise if:

Change TreeView.IsEnabled

Remove an item X from the collection

Re-insert the same item X back into the collection

Remove one of X’s subitems Y from its collection
(Step 4 can happen any time relative to steps 2 and 3, as long as it’s after step 1. Steps 2-4 must occur before the asynchronous call to UpdatePeer, posted by step 1; this will happen if steps 1-4 all occur in the same button-click handler.)

Note: Additional information on these improvements is not available. The VSTS bug number provided with each improvement is a unique ID that you can give Microsoft Customer Support, include in StackOverflow comments or use in web searches.

Getting the Update

The Preview of Quality Rollup 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.

[table][tr]Product Version Preview of Quality Rollup KB [/tr] [tr][td]Windows 8.1 Windows RT 8.1 Windows Server 2012 R2[/td] [td]Catalog 4103473[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4095875[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098974[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4098972[/td] [/tr] [tr][td]Windows Server 2012[/td] [td]Catalog 4098968[/td] [/tr] [tr][td].NET Framework 3.5[/td] [td]4095872[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098975[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4098971[/td] [/tr] [tr][td]Windows 7 Windows Server 2008 R2[/td] [td]Catalog 4103472[/td] [/tr] [tr][td].NET Framework 3.5.1[/td] [td]4095874[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098976[/td] [/tr] [tr][td].NET Framework 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.1[/td] [td]4096234[/td] [/tr] [tr][td]Windows Server 2008[/td] [td]Catalog 4103474[/td] [/tr] [tr][td].NET Framework 2.0, 3.0[/td] [td]4095873[/td] [/tr] [tr][td].NET Framework 4.5.2[/td] [td]4098976[/td] [/tr] [tr][td].NET Framework 4.6[/td] [td]4096234[/td] [/tr] [/table]
Click to expand...

Read more: .NET Framework May 2018 Preview of Quality Rollup | .NET Blog

Windows 10: .NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

.NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

.NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

.NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

.NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups? - Similar Threads - NET Framework last

.NET Framework 8

.NET Framework 8

.NET Framework 4.8 at last, but how to be up-to-date with .NET Rollups?

.NET Framework 4 is corrupted

.NET Framework 4+

.NET Framework October 2018 Security and Quality Rollup

.NET Framework September 2018 Security and Quality Rollup

.NET Framework June 2018 Security and Quality Rollup

.NET Framework May 2017 Monthly Rollup