.NET Framework July 2022 Cumulative Update Preview

Salini Agarwal

July 26th, 20225 1

We are releasing the July 2022 Cumulative Update Preview Updates for .NET Framework.

Quality and Reliability

This release contains the following quality and reliability improvements.

Networking
  • Addresses an issue when Ssl negotiation can hang indefinitely when client certificates are used when TLS 1.3 is negotiated. Before the change renegotiation (PostHandshakeAuthentiction) would fail and SslStream or HttpWebRequest would observe timeout. Possible workaround is disabling TLS 1.3 either via Switch.System.Net.DontEnableTls13 AppContext or via OS registry.
WPF1
  • Addresses an issue where invoking a synchronization Wait on the UI thread can lead to a render-thread failure, due to unexpected re-entrancy.

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 5015732
Microsoft server operating systems version 21H2
.NET Framework 3.5, 4.8 Catalog 5015733
Windows 10 21H2
.NET Framework 3.5, 4.8 Catalog 5015730
Windows 10 21H1
.NET Framework 3.5, 4.8 Catalog 5015730
Windows 10, version 20H2 and Windows Server, version 20H2
.NET Framework 3.5, 4.8 Catalog 5015730
Windows 10 1809 (October 2018 Update) and Windows Server 2019 5016188
.NET Framework 3.5, 4.7.2 Catalog 5015736
.NET Framework 3.5, 4.8 Catalog 5015731

 

Previous Monthly Rollups

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

Salini Agarwal

Read next

5 comments

Discussion is closed. Login to edit/delete existing comments.

  • Dhanraj D 0

    Hi Shalini,

    The support page of KB5015731 says it is applicable for both .Net Framework version 3.5 and 4.8. But when we try to install it on the machine where it has only .Net Framework version 3.5, it says that the KB5015731 is not applicable. I raised the same kind of concern around a month back. Your help is much appreciated on understanding the root cause of the issue.

    Thanks and Regards,
    D.Dhanraj

    • abbodi86 assi 0

      KB5015731 require both (i.e. .NET 4.8 KB4486153 should be installed), otherwise use KB5015736

      • Dhanraj D 0

        Hi,

        Thanks for replying. But the support page of this KB5015731 says “To apply this update, you must have .NET Framework 3.5 or 4.8 installed.”

        It means it can be installed on either .NET Framework 3.5 or .NET Framework 4.8 right?. It does not say that we need to have both versions installed.

        Please clarify on this.

        Thanks again,

        Regards,
        D.Dhanraj

  • Steven Lippert 0

    Heck please give us back our XAML designer, HOT Reload can never replace a UI builder.
    When I change more than 5 lines in HOT Reload it always has to rebuild the whole project.

    That can never be the solution.

    I’ve been working with MAUI for over 2 months now, I love it but it wastes so much time trying to set proper properties for all elements and controls.

    Why just discard a perfectly running system like WPF and roll it back 30 years in the past?

    The competition has long since caught up and is delivering an incredibly strong builder, so why take so many steps backwards?

    Is there a chance we’ll get our builder back?

    That’s why there’s a lot of discussion on Github, but there are only philosophers there.

    Greetz
    Steven

Feedback usabilla icon