.NET Framework 4.7.2 is available on Windows Update, WSUS and MU Catalog
8/20/2019 Update: The .NET 4.7.2 update has been republished to work around a known issue in Config Manager that resulted in errors when Config Manager tried to sync with an upstream WSUS server. Please note that there is no change to the installers below.
Today, we are happy to announce the Microsoft .NET Framework 4.7.2 is available on Windows Update, Windows Server Update Services (WSUS) and Microsoft Update (MU) Catalog. This release includes quality and reliability updates based on early feedback on .NET Framework 4.7.2.
.NET Framework 4.7.2 is available for the following client and server platforms:
- Client platforms: Windows 7 SP1, Windows 8.1, Windows 10 Anniversary Update (Version 1607), Windows 10 Creators Update (Version 1703), Windows 10 Fall Creators Update (Version 1709)
- Server platforms: Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 and Windows Server, version 1709.
The updated .NET Framework 4.7.2 installers (which include the additional quality fixes) are available on Download Center.
The updated .NET Framework 4.7.2 installer can be installed on top of the initial release of NET Framework 4.7.2 to upgrade you to the latest version. You can also wait for the fixes to be installed on your machine via Windows Update.
All download links are provided at .NET Framework downloads.
Note: .NET Framework 4.7.2 is included in the Windows 10 April 2018 Update. You need to wait to get the reliability in the next Cumulative Update for Windows 10 April 2018 Update.
Quality and Reliability fixes
The following fixes are included:
SQL Connectivity (SQL)
- Fixes an issue when the .NET Framework API ConnectionString property is used to set a null or empty connection string. In this case, a Null Reference Exception (NRE) occurs when you use the API together with .NET Framework 4.7.2. [611802, System.Data.dll, Bug]
- While connecting to Azure SQL DB and using MultipleActiveResultSets=true in the connection string with System.Data.SqlClient.SqlConnection, the async query operations would result in a bad TDS protocol request stream being sent from the client, causing the async query APIs to fail. This is now fixed. [620109, System.Data.dll , Bug]
Windows Presentation Framework (WPF)
- Adds an AppContext switch that opts out of some work done during AppDomain or process shutdown. This issue can reduce (but not eliminate) the possibility of a crash in applications that make unwarranted assumptions about the timing of the finalizer thread. [593963, WindowsBase.dll, Bug]
- Fixes a crash in WPF when replacing multiple characters with a single character (in a different language than the replaced text) by using IMEPad. [605996, PresentationFramework.dll, Bug]
- Combo box grouped items now report children correctly through UIAutomation. [605922, PresentationFramework.dll, Bug]
You can see the complete list of improvements for .NET Framework 4.7.2 in the .NET Framework 4.7.2 release notes.
Knowledge Base Articles
You can reference the following Knowledge Base Articles for the WU/WSUS/Catalog release:
.NET Framework 4.7.2 Redistributable
.NET Framework 4.7.2 Language Pack
|Windows 7 SP1/Windows Server 2008 R2||KB4054530||KB4054529|
|Windows Server 2012||KB4054542||KB4054533|
|Windows 8.1/Windows Server 2012 R2||KB4054566||KB4054534|
|Windows 10 Version 1607||KB4054590||KB4054535|
|Windows 10 Version 1703||KB4054590 (Catalog Only)||KB4054535 (Catalog Only)|
|Windows Server 2016||KB4054590 (Catalog Only)||KB4054535 (Catalog Only)|
|Windows 10 Version 1709||KB4073120 (Catalog Only)||KB4073705 (Catalog Only)|
|Windows Server, version 1709||KB4073120 (Catalog Only)||KB4073705 (Catalog Only)|
How is this release available?
.NET Framework 4.7.2 is being offered as a Recommended update. The reliability fixes for .NET Framework 4.7.2 will be co-installed with .NET Framework 4.7.2. At this time, we’re throttling the release as we have done with previous .NET Framework releases. Over the next few weeks we will be closely monitoring your feedback and will gradually open throttling.
While the release is throttled, you can use the Check for updates feature to get .NET Framework 4.7.2.
Note: Throttled updates are offered at a lower priority than unthrottled updates, so if you have other Recommended or Important updates pending those will be offered before this update.
Once we open throttling, in most cases you will get the .NET Framework 4.7.2 with no further action necessary. If you have modified your AU settings to notify but not install you should see a notification in the system tray about this update.
The deployment will be rolled out to various geographies globally over several weeks. So, if you do not get the update offered on the first day and do not want to wait until the update is offered, you can use the Check for updates feature, as described above.
Windows Server Update Services (WSUS) and Catalog
WSUS administrators will see this update in their WSUS admin console. The update is also available in the MU Catalog for download and deployment.
When you synchronize your WSUS server with Microsoft Update server (or use the Microsoft Update Catalog site for importing updates), you will see the updates for .NET Framework 4.7.2 published for each platform.
.NET Framework 4.7.2 can be downloaded and installed manually on all supported platforms using the links from here.
In addition to the language neutral package, the .NET Framework 4.7.2 Language Packs are also available on Windows Update. These can be used if you have a previous language pack for .NET Framework installed as well as if you don’t, but instead have a localized version of the base operating system or have one or more Multilingual User Interface (MUI) pack installed.
Blocking the automatic deployment of .NET 4.7.2
Enterprises may have client machines that connect directly to the public Windows Update servers rather than to an internal WSUS server. In such cases, an administrator may have a need to prevent the .NET Framework 4.7.2 from being deployed to these client machines to allow testing of internal applications to be completed before deployment.
In such scenarios, administrators can deploy a registry key to machines and prevent the .NET Framework 4.7.2 from being offered to those machines. More information about how to use this blocker registry key can be found in the following Microsoft Knowledge Base article:
KB4342394: How to temporarily block the installation of the .NET Framework 4.7.2 and its corresponding language packs
What do I need to do if I already have .NET Framework 4.7.2 product installed and want the reliability fixes?
If you installed .NET Framework 4.7.2 via Download Center earlier, then you need to reinstall the product using the links at the top of the blog.
Do I still need to install updated .NET Framework 4.7.2 if I am getting .NET 4.7.2 from Windows Update/WSUS?
No, .NET Framework 4.7.2 via Windows Update and WSUS will install the product and the included reliability fixes.
Will Windows Update offer the updated .NET Framework 4.7.2 if I already have the RTM version (4.7.3062) of .NET 4.7.2 installed?
Yes, Windows Update will offer the .NET 4.7.2 product update to machines that have the RTM version (4.7.3062) of the product already installed. After the update you will see the new version (4.7.3081) of files that were included for the reliability fixes.
Will the RTM version (4.7.3062) of the .NET Framework 4.7.2 installers still work if I had downloaded them earlier?
Yes, the installers will still work, but we recommend that you download the latest versions of the installers as per the links above.
Will the detection key (Release Key) for the product change after I install the updated .NET Framework 4.7.2?
No, the Release key value in the registry will remain the same. See here for guidance on product detection and release key value for .NET 4.7.2.
How can I get the reliability fixes for Windows 10 April 2018 Update (Version 1803)?
These reliability fixes will be available via the next Windows Cumulative update for Windows 10 April Update (Version 1803).