Microsoft .NET Framework 4.6.1 coming to WSUS

Hi WSUS Admins,

The Microsoft .NET Framework 4.6.1 will be made available via Windows Server Update Services for Windows 7 SP1 and Windows Server 2012 R2 platforms on 26 January 2016 and this blog highlights some of the key aspects.

The .NET Framework is a development platform for building apps for Windows, Windows Phone, Windows Server, and Windows Azure. The .NET Framework 4.6.1 is a highly compatible, in-place update to the .NET Framework 4, 4.5, 4.5.1, 4.5.2 and 4.6. The .NET Framework 4.6.1 can be installed fresh or can be used to upgrade your previous .NET 4 or 4.5 or 4.5.1 or 4.5.2 or 4.6 installation. Applications built against and running on .NET 4, 4.5, 4.5.1, 4.5.2 or .NET 4.6 will automatically roll forward to using the newer .NET 4.6.1 runtime without any need to recompile the application. 

The .NET Framework 4.6.1 installs side by side with older Framework versions lower than .NET 4 such as .NET 3.5 SP1. Applications that are based on earlier versions of the Framework such as .NET Framework 3.5 SP1 will continue to run on .NET 3.5 SP1 and will not automatically roll forward to using .NET 4.6.1.

You can learn more about .NET Framework 4.6.1 here.

Useful information about this release:

  1. The .NET Framework 4.6.1 and its corresponding language packs are being released via WSUS and WU for Windows 7 SP1 and Windows Server 2012 R2.  For other platforms, such as Windows 8.1, Windows Server 2008 R2 SP1 or Windows Server 2012, an offline installer is available here.
  2. The .NET Framework 4.6.1 Language Packs will also be available via WSUS, both to support the upgrade of previous language packs for .NET Frameworks 4, 4.5, 4.5.1, 4.5.2, 4.6 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.
  3. When you synchronize your WSUS server with Microsoft Update server (or use Microsoft Update Catalog site for importing updates), you will see that there are two updates with .NET Framework 4.6.1 being published for each platform. The difference in the updates is scoped to the different applicability logic for targeting different computers. Please read the details included in the description of the respective update to get more information. We recommend that you import both the updates, if you plan to deploy .NET Framework 4.6.1 in your Enterprise.
    • One of the .NET Framework 4.6.1 updates will install only on computers that have an earlier version such as .NET 4, 4.5, 4.5.1, or 4.5.2 installed
    • The other .NET Framework 4.6.1 update will install on those computers that either have .NET 4.6 installed or no .NET Framework installed.
  4. Computers that do not have .NET Framework 4.5.2 or a higher version installed with be offered both .NET Framework 4.5.2 and .NET Framework 4.6.1. You have an option to choose the .NET Framework version you need.
  5. Enterprises that have a specific need to block offering .NET Framework 4.6.1 on computers which can directly connect to Microsoft Update servers can do so by deploying the blocker registry key as described in following Microsoft Knowledge Base:  

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

Comments (19)
  1. Pat says:

    When the MS.NET Framework 4.6.1 will be made available via Windows Server Update Services for Windows 8 ?

  2. Root_racer says:

    When dotNET Framework will be in one package 3.5.1+4.*.* ??? 🙂

  3. It’s January 26 and still nothing in WSUS.

  4. @Pat – Windows 8 is out of support so .NET 4.6.1 won’t be made available for Windows 8 on Windows Server Update Services.

  5. @Root – Only .NET framework 4.6.1 is pushed on WU and WSUS and the package has only .NET 4.6.1 and does not have earlier versions of the framework packaged.

  6. @Preeti I just run sync on WSUS and nothing new.

  7. 127 says:

    When it will be available (by WSUS) for
    – w8.1
    – 2008R2
    – 2012 (non-R2)


  8. 127 says:

    how about 4.6.1 and Exchange.
    Is it still incomatible like 4.6 ?

  9. anonymouscommenter says:

    212 Microsoft Team blogs searched, 44 blogs have new articles. 139 new articles found searching from

  10. John Sebald says:


    thank you for the post article.

    But on my WSUS (2012 R2) i can’t download the Language Pack for Windows 7 SP1:
    Microsoft .NET Framework 4.6.1 Language Packs for x64 (KB3102433)
    Microsoft .NET Framework 4.6.1 Upgrade-Sprachpakete (KB3102433)

  11. @127 – We do not have anything to announce at this time regarding plans to release .NET 4.6.1 on WU/WSUS for the other platforms. There is an offline installer you can download @ for these platforms.

  12. Richard says:

    Why was this made available only to Windows 7 SP1 and Server 2012 R2 platforms only? The offline installer is available for download for the other operating systems, however I would rather have it available through WSUS than to manually install them in
    a managed environment. .NET 4.5.2 supported 8, 8.1, Server 2008, Server 2008 R2, and Server 2012 for the WSUS updates, why can’t 4.6.1 also support it?

  13. Rakesh says:

    Thanks for sharing these information. It’s a very nice topic. We are providing online training classes /dotnet-online-training/ / /"> dotnet-online-training

  14. VAKULU says:

    Thanks for sharing these information. It’s a very nice topic. We are providing online training classes /dotnet-online-training/ / /"> dotnet-online-training

  15. jolie says:

    Thanks for sharing these information. Regards.

  16. michal y says:

    Thanks for sharing these information. It’s a very nice topic. We are providing online training classes"> dot net online training

  17. Ramakanth says:

    I have read your information its very useful topic for me. Thanks for providing information. Hyderabadsys providing online training services">.NET Online Training

  18. Justin says:

    When is NET Framework 4.6.1 being made available via WSUS for Windows 8.1 and Server 2008 R2 by default?, this seems strange after so many months.

Comments are closed.

Skip to main content