Jaa


Microsoft .NET Framework 4.7 coming to WSUS

(this post contributed by the .NET team. Note that WSUS 3.0 will fail to install if .NET 4.6 or later is already installed on the machine, per our previous article describing this behavior)

 
Hi WSUS Admins,

The Microsoft .NET Framework 4.7 will be made available via Windows Server Update Services for Windows 7 SP1, Windows 8.1, Windows 10 Anniversary Update (Version 1607), Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2 and Windows Server 2016 on June 13, 2017.

 

The .NET Framework 4.7 is a highly compatible, in-place update to all the previous 4.X versions of the .NET Framework including .NET 4, 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1 and 4.6.2. Applications built against and running on previous versions of .NET Framework will automatically roll forward to using the newer .NET 4.7 runtime without recompilation of the apps. .NET 4.7 can be installed on a fresh machine or can be used to upgrade your previous .NET 4.X installation.  Â

The .NET Framework 4.7 installs side by side with older Framework versions such as .NET 3.5 SP1. Applications compiled against .NET 3.5 SP1 will continue to run on .NET 3.5 SP1 and will not automatically roll forward to .NET 4.7.

You can learn more about .NET Framework 4.7 here:

 

More information about this release:

  1. The .NET Framework 4.7 update bundles for Windows 7 SP1, Windows Server 2008 R2 SP1 and Windows Server 2012 carry a DirectX dependency check (D3DCompiler: %windir%\system32\d3dcompiler_47.dll). This file needs to be present before the .NET 4.7 bundles will offer on these platforms.

The DirectX dependency is available in the May 2017 Monthly Rollup under the following Knowledge Base Articles:

The DirectX dependency is also available outside of the Monthly Rollup as an independent/standalone package in the Microsoft Update Catalog here.

 

  1. The .NET Framework 4.7 Language Packs will also be available via WSUS, both to support the upgrade of previous language packs for .NET Framework and for computers, that either have the localized version of the base operating system or have one or more Multilingual User Interface (MUI) packs installed.

 

  1. Enterprises that have a specific need to block offering .NET Framework 4.7 on computers that directly connect to Microsoft Update servers can do so by deploying the blocker registry key described in following Microsoft Knowledge Base:

KB4024204:  How to temporarily block the installation of the .NET Framework 4.7 and its corresponding language packs

Comments

  • Anonymous
    June 12, 2017
    Thanks Microsoft download updates, we get net frameworks, every week to update the net framework 3.5 up to net framework 4.7 and so on for Microsoft windows 7 genuine and Microsoft windows8 genune and Mcrosoft Windows 8.1.
  • Anonymous
    June 12, 2017
    Very good news!
  • Anonymous
    June 13, 2017
    What about the recent Skype/Lync-bug?Is that fixed with this release or do we have to change the registry key?https://blogs.technet.microsoft.com/uclobby/2017/05/24/lyncsfb-server-event-41026-ls-data-mcu-after-may-2017-net-framework-update/
  • Anonymous
    September 25, 2017
    Not working as advertised Macola ES, from Exact Software, and their Event Manager 1.9 fail when NET 4.7 Update is installed. Must roll back to version 4.5.2 to get working again.