Patch Lady – .NET changes

Topic

New Reply

Back in the 7 and 8.1 era .NET was independently released and not part of the operating system – exactly – yes each shipped with a base .NET version,
[See the full post at: Patch Lady – .NET changes]

Susan Bradley Patch Lady/Prudent patcher

7 users thanked author for this post.

abbodi86, GreatAndPowerfulTech, Cesar, CyGuy, Fred, PhotM, Elly

Reply | Quote

Replies

Before to upgrade to a new .NET you had to go up a feature update to do so.

With one exception, this isn’t correct.

.NET Framework 4.7.2 was included with Windows 10 1803 but is also available for Windows 10 1607 and later: Microsoft .NET Framework 4.7.2 offline installer for Windows

.NET Framework 4.7.1 was included with Windows 10 1709 but is also available for 1607 and 1703: The .NET Framework 4.7.1 offline installer for Windows

.NET Framework 4.7 was included with Windows 10 1703 but is also available for 1607: The .NET Framework 4.7 offline installer for Windows

Similar story for .NET 4.6.2 being released for Windows 10 1507 and 1511.

The one exception is that you have to upgrade Windows 10 1507/1511 to Windows 10 1607 or later to get .NET Framework 4.7+, though this shouldn’t be an issue now since 1507 and 1511 are both out of support.

….. eerr, with one exception: Windows 10 Enterprise LTSB 2015.  Pity the poor maintenance folks at Microsoft who will now have to ship .NET Framework 4.6.2-specific patches solely for LTSB 2015, until the end of 2025.  All other supported Microsoft operating systems support .NET Framework 4.7.x and 4.8, including LTSB 2016, and even Server 2008 R2, which will receive (paid) security updates until late 2023.

 

2 users thanked author for this post.

abbodi86, Fred

Reply | Quote

warrenrumak

.NET 4.7.2 is included in both 1803 and 1809 versions of Win10

1903 will include .NET 4.8

also LTSB 2016 has support until late 2026

Reply | Quote

.NET Framework 4.8 Offline installer: https://go.microsoft.com/fwlink/?linkid=2088631

.NET Framework 4.8 Web Installer: https://go.microsoft.com/fwlink/?LinkId=2085155

.NET Framework 4.8 Language Packs for offline installation : https://support.microsoft.com/en-us/help/4497410/microsoft-net-framework-4-8-language-pack-offline-installer-for-window

.NET Framework 4.8 Developer Pack : https://dotnet.microsoft.com/download/dotnet-framework/net48

Thanks ghacks.net

2 users thanked author for this post.

Cesar, Fred

Reply | Quote

I wish Microsoft would just acquiesce to calling feature updates by their RTM year and month, e.g. 1809.  As you note, over time, marketing names  pale in the mist.

Reply | Quote

Good move, as long they release the updates chained

Reply | Quote

I honestly do not want to go back to the Windows 7 patch model of separate patches as I think the cumulative model – once we get the patch quality to where it should be – is what we need to do as it keeps our machines more secure – but at the same time you can tell that as Microsoft is listening to our complaints about patching, they are moving back to a model where things are more modular and optional.

I’m curious; after several years of this rigamarole of cumulative patches, what makes you think that “once we get patch quality to where it should be” is even an achievable goal?  If Microsoft could do it, would they not have by now?  Every month brings the same old thing; release, howls of pain, a bunch of “known issues” caveats added to the patch KBs.  Lather, rinse, repeat.  Would it not be logical to believe that if they could actually meet that threshold of “patch quality where it should be” – wherever that is – that they would have by now?

Also, I would object to your assertion that Microsoft is listening as facts not in evidence.  Making a single change to .NET servicing is hardly evidence that Microsoft is listening to anybody.  Afterall, everyone’s been asking for the mythical “better patch quality” and that is still nowhere to be found.

Reply | Quote

Why exactly is the cumulative model “more secure”?  It seems like the same changes, just delivered a different way.  When there is a problem with a patch, the old model allowed advanced users to avoid a problem with one update, but install all the other updates, getting most of the security patches without impacting stability.  With cumulative updates, the same situation instead means you have to either take the stability loss, or toss out all the security updates for the time being.

If you are arguing that normal users shouldn’t have the choice to not install updates (so as not to proliferate botnets), then as I see it, that is a separate argument from the cumulative patching model (they could release granular patches as before, while still making windows 10 update install them without asking).

1 user thanked author for this post.

Elly

Reply | Quote

Here is a nice resource with helpful information that might be useful for others:

What is Microsoft .NET Framework? Download Links for All Versions Inside
UPDATED on April 18, 2019: Information and download links added for the new Microsoft .NET Framework 4.8 version.
https://www.askvg.com/what-is-microsoft-net-framework-download-links-for-all-versions-inside/

 

Amazing Truths Revealed: Link to Simply Magnificent AskWoody Knowledge Bases

Reply | Quote