.NET Framework Rollup updates simplify handling updating systems regardless of the underlying version of .NET Framework present on a system. Rollups present a single (per-OS) update offering on Windows Update (WU) and Windows Server Update Services (WSUS) and Microsoft Update (MU) Catalog. For IT admins this means significantly less update management for all supported .NET Framework versions since Rollup handle patch applicability automatically on WU or WSUS. There is also a smaller portion of advanced IT admins managing environments that are disconnected from the internet, WU and/or WSUS, with workflows that require downloading .NET version-specific patches for pre-Windows 10 systems. For this subset of advanced IT admin customers, we are bringing this ability to search and download .NET version-specific updates from the MU Catalog (previously only possible per-OS configuration). We are also taking the opportunity to explain how .NET Framework updates are structured.
<<With the roll out back in 2016 of all-inclusive .NET ‘Rollup’ updates, we simplified handling updating systems regardless of the underlying version of .NET Framework present on the machine by presenting a single update offering on Windows Update (WU) and Windows Server Update Services (WSUS) and Microsoft Update Catalog. With this>>
How .NET Framework Rollup updates are structured
As explained in Announcing Cumulative Updates for .NET Framework for Windows 10 October 2018 Update):
- Pre-Windows 10 operating systems (Windows 8.1, Server 2012 R2 and below):
- One “parent” OS-level KB update, presented as “2019-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2”.
- Behind the scenes*** this update contains various patches that will only apply based on what version of .NET is on your system(s). These “child” KBs will follow a similar form:
- Security and Quality Rollup for .NET Framework for 3.5
- Security and Quality Rollup for .NET Framework for 4.5.2
- Security and Quality Rollup for .NET Framework for 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 (a single patch shared for these versions)
- Behind the scenes*** this update contains various patches that will only apply based on what version of .NET is on your system(s). These “child” KBs will follow a similar form:
- One “parent” OS-level KB update, presented as “2019-01 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2”.
- Windows 10 version 1803, Server 2016 and below:
- One Windows cumulative update that contains all .NET Framework content together with core OS content. No separate/individual updates.**
- Windows 10 version 1809, Server 2019 and above:
- One .NET cumulative update, alongside with the Windows cumulative update. A single update with no version-specific break down (carries 3.5 and 4.7.2 updates).
- [internal] Note that with .NET 4.8 we will have a separate 4.8-specific patch for 1809 (RS5), so this will change to closely mirror pre-Windows 10.
- One .NET cumulative update, alongside with the Windows cumulative update. A single update with no version-specific break down (carries 3.5 and 4.7.2 updates).
How to retrieve content from Microsoft Update Catalog depending on your scenario
With each new .NET Framework update you can access update specific information, including KBs for each OS and .NET version from the .NET Framework Blog and or from the Microsoft Security Update Guidance, as appropriate and depending on release type.
- I want to let WSUS/SCCM take advantage of automatic applicability management
- OS (“parent”)-level updates: You can search the MU Catalog for the regular per-OS KB, as follows:
- Search on Catalog steps..
- Import and deploy from WSUS or SCCM steps.
- OS (“parent”)-level updates: You can search the MU Catalog for the regular per-OS KB, as follows:
- I want to manage .NET version-specific updates manually within my Internet disconnected environment.
- Search on Catalog for “child” KBs steps..
The post .NET Framework updates on Microsoft Update Catalog appeared first on .NET Blog.