.NET Framework 4.8 is available on Windows Update, WSUS and MU Catalog

Namrata Karnam

We are happy to announce that Microsoft .NET Framework 4.8 is now available on Windows Update, Windows Server Update Services (WSUS) and Microsoft Update (MU) Catalog. This release includes quality and reliability fixes based on feedback since the .NET Framework 4.8 initial release.

.NET Framework 4.8 is available for the following client and server platforms:

  • Windows Client versions: Windows 10 version 1903, Windows 10 version 1809, Windows 10 version 1803, Windows 10 version 1709, Windows 10 version 1703, Windows 10 version 1607, Windows 8.1, Windows 7 SP1
  • Windows Server versions: Windows Server 2019, Windows Server version 1809, Windows Server version 1803, Windows Server 2016, Windows Server 2012, Windows Server 2012 R2, Windows Server 2008 R2 SP1

Note: Windows 10 May 2019 Update ships with .NET Framework 4.8 already included.

The updated .NET Framework 4.8 installers (which include the additional quality and reliability fixes) are available for download.

The updated .NET Framework 4.8 can be installed on top of the initial release of .NET Framework 4.8 from April this year. All download links are provided at .NET Framework downloads.

Quality and Reliability Fixes

The following fixes are included in this update:


  • Fixed System.Web.Caching initialization bug when using ASP.NET cache on machines without IIS. [889110, System.Web.dll, Bug]

 Windows Forms:

  • Fixed the ability to select ComboBox edit field text using mouse down+move [853381, System.Windows.Forms.dll, Bug]
  • Fixed the issue with interaction between WPF user control and hosting WinForms app when processing keyboard input. [899206, WindowsFormsIntegration.dll, Bug]
  • Fixed the issue with Narrator/NVDA announcing of PropertyGrid’s ComboBox expanding and collapsing action. [792617, System.Windows.Forms.dll, Bug]
  • Fixed the issue with rendering “…” button of PropertyGrid control in HC mode to draw button background and dots contrasted. [792780, System.Windows.Forms.dll, Bug]


  • Fixed a handle leak during creation of a Window in WPF applications that are manifested for Per Monitor DPI V2 Awareness.  This leak may lead to extraneous GC.Collect calls that can impact performance in Window creation scenarios.  [845699, PresentationFramework.dll, Bug]
  • Fixed a regression caused by the bug fix involving bindings with DataContext explicitly on the binding path. [850536, PresentationFramework.dll, Bug]
  • Fixed crash due to ArgumentNullException when loading a DataGrid containing a ComboBox while automation is active.  For example, when navigating Visual Studio to the Text Editor\C#\Code Style\Naming page in Tools\Options. [801039, PresentationFramework.dll, Bug]

You can see the complete list of improvements for .NET Framework 4.8 in the .NET Framework 4.8 release notes.

Knowledge Base Articles

You can reference the following Knowledge Base Articles for the WU/WSUS/Catalog release:

OS Platform.NET Framework 4.8 Redistributable.NET Framework 4.8 Language Pack
Windows 7 SP1/Windows Server 2008 R2KB4503548KB4497410
Windows Server 2012KB4486081KB4087513
Windows 8.1/Windows Server 2012 R2KB4486105KB4087514
Windows 10 Version 1607KB4486129 (Catalog Only)KB4087515 (Catalog Only)
Windows 10 Version 1703KB4486129KB4087515
Windows Server 2016KB4486129 (Catalog Only)KB4087515 (Catalog Only)
Windows 10 Version 1709KB4486153KB4087642
Windows 10 Version 1803KB4486153KB4087642
Windows Server, version 1803KB4486153KB4087642
Windows 10 Version 1809KB4486153KB4087642
Windows Server, version 1809KB4486153 (Catalog Only)KB4087642 (Catalog Only)
Windows Server 2019KB4486153 (Catalog Only)KB4087642 (Catalog Only)


How is this release available?

Automatic Updates

.NET Framework 4.8 is being offered as a Recommended update. The reliability fixes for .NET Framework 4.8 will be co-installed with .NET Framework 4.8. 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.8. Open your Windows Update settings (Settings > Update & Security > Windows Update) and select Check for updates.

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.8 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 instructions above to check for updates or download from here.

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.8 published for each platform.

Dot.NET Site

.NET Framework 4.8 can be downloaded and installed manually on all supported platforms using the links from here.

More Information

Language Packs

In addition to the language neutral package, the .NET Framework 4.8 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.8

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.8 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.8 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 KB4516563: How to temporarily block the installation of the .NET Framework 4.8.


What do I need to do if I already have .NET Framework 4.8 product installed and want the reliability fixes?

If you installed .NET Framework 4.8 via Download site 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.8 if I am getting .NET 4.8 from Windows Update/WSUS?

No, .NET Framework 4.8 via Windows Update and WSUS will install the product and the included reliability fixes.

Will Windows Update offer the updated .NET Framework 4.8 if I already have the RTM version (4.7.3761) of .NET 4.8 installed?

Yes, Windows Update will offer the .NET 4.8 product update to machines that have the RTM version (4.7.3761) of the product already installed. After the update you will see the new version (4.7.3928) of files that were included for the reliability fixes.

Will the RTM version (4.7.3761) of the .NET Framework 4.8 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.8?

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.8.

How can I get the reliability fixes for Windows 10 May 2019 Update (Version 1903)?

These reliability fixes will be available via the next .NET Framework Cumulative update for Windows 10 May Update (Version 1903).



Namrata Karnam
Namrata Karnam


Shane Sullivan 2019-08-14 01:22:27
Can I ask why this took four months to arrive?
Robert Richter 2019-08-15 00:59:01
I've already installed the RTM Developer Pack on my machine. Windows Updates offers me to update .NET Framework 4.8 - do I have to re-install the Developer Pack from the links above? Or is this not necessary if I let Windows Update do its job? Just asking, because Windows Update says .NET Framework and nothing about the Developers Pack.
Mikael Aspehed 2019-08-21 05:16:39
Hi, Does the .NET Framework 4.8 have any pre-reqs on Windows 7 SP1? Looking at it in SCCM, the Windows 7 clients do not tag it as required and therefore don't see it when it is deployed on them. BR Mikael
Jim Wooley 2019-08-21 08:14:03
What version of the 4.8 update solves the last WPF bug (specifically for Visual Studio's Naming styles window)? I have 1902 with the latest available 4.8 update (from July) and the bug still appears to be there for me. Is the Aug update not available yet?