|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
ISSUE 18.50.1 • 2021-12-28 By Susan Bradley The end of 2021 brings the final updates for Windows 10 2004. Meanwhile, most of us are planning not to in
[See the full post at: MS-DEFCON 4: Closing out the year of patching]
Susan Bradley Patch Lady/Prudent patcher
Still working fine for me @<span class=”bbp-author-name”>Save_Us_from_MS</span>
You should see the following on Windows Update:
Sorry, getting old. Forgot to change it before going to bed last night.
Susan Bradley Patch Lady/Prudent patcher
Apologies, I was swamped and didn’t get back to you. Is it the attention light blinking?
“Press any button on the control panel except the Cancel button
or in the printer software, click OK to continue.”
Can you try that?
Susan Bradley Patch Lady/Prudent patcher
Upgraded from 20H2 to 21H2 here on Windows 10 Pro yesterday, without issues. Changed my gpedit settings to target release 21H2, and then checked for updates.
However, I did uninstall my VPN and 3rd party firewall first, had a fresh image backup handy, and the only security running at the time of the feature upgrade was Windows Defender.
Re-installed the VPN and firewall afterwards, and all is good! 🙂
Windows 10 Pro 22H2
@WCHS –
I’m hazarding a guess here, but since the .net 3.5 and 4.8 platforms for Windows 10 haven’t had a security update since February of this year (KB4601050, as mentioned by @Alex5723 below), that’s probably why Susan hasn’t really paid much attention to those platforms. They are still current since they’re getting monthly patches that improve performance or fix one or more reported bugs that aren’t security threats.
As far as .net 5.0 goes, if you don’t have an application that tells you that it requires the use of .net 5.0, no need to worry about it for now. I have a feeling that if MS decides that 5.0 is going to replace 3.5 and 4.8 on Windows 10-based platforms (I really doubt it), we’ll hear about it right here for starters.
As a side note, when I had Windows 7 SP1 Pro 64 bit and needed .net 4.5.2 for one of my installed programs to use, it installed alongside .net 3.5.1 that came bundled with Windows 7 at the time instead of automatically replacing it. The same might hold true for .net 5.0, however since you probably don’t need it right now, don’t worry about it for now. 🙂
I hope this answers your questions.
They seem to have done away with the “Framework” moniker with the advent of .NET 5, which began calling things “Core”. That naming convention is currently in use. However, the first versions after 4.8 were called .NET Core 1.0, 2.0, and 3.0, but they seem to have been superseded by .NET 5.0 and .NET 6.0 for now. This is based upon my own observations of the MS pages dealing with .NET releases.
We need to end this discussion of .NET on this thread, because otherwise it might seem as if we’ve hijacked it, and that definitely wasn’t my intent by answering your questions.
Any further discussion relating to .NET can be had by please starting a thread at the location below:
Thanks to one and all!
Windows 10 Pro 21H2 .NET 6.
I hope you’ve updated your brand new (since November’s release anyway) .net 6.0 to 6.0.1. The .1 release was made on about the 14th of December and is labeled as a security release for .net 6.0 installations to help rectify CVE-2021-43877. Hopefully, Windows Update was able to get the update for you via your use of WUMgr.
So, if you upgrade to 21H2, does .NET 5 and/or .NET 6 come with it automatically??
No .NET does not come with 21H2. I’m currently on 21H2 and have .NET 3.5 (turned off) and .NET 4.8 (partially enabled, default setting) on my system.
This should end all discussion of .NET on this thread, as it’s now been going just long enough to possibly be considered as having “hijacked” this thread. Any future .NET discussion should be carried over to the forum meant for .NET right here:
Thank you!
OK, one final blurb about .NET, since this blurb DOES involve a security patch for.NET and doesn’t deal with actually installing or changing versions of .NET.
I don’t remember ever seeing a .NET security or monthly update ever included within the month’s cumulative update for Windows itself. This includes going all the way back to July 2010 when I got my Windows 7 machine.
Even back then, and every time since then, the .NET monthly rollups and/or security updates that have been released have been separate from the monthly Windows update(s). Even within WU on Windows 7, they had their own separate entry with a check box to download them separately from the monthly Windows updates.
So, same goes for Windows 10. I have an entry from this past February that is only for the .NET security rollup being installed separate from the entry for that month’s Windows rollup.
What I was trying to say in my post above is that at the time, I thought you should have been offered the separate .NET security update from 6 to 6.0.1 via Windows Update, and that behavior should have manifested itself by the .NET update showing up in WUMgr’s listings of what was available to either hide or install. However, after visiting the MSRC page about the CVE that was repaired by the security release on the 14th, I realized that a separate KB article for the CVE repair wasn’t developed…the links in the MSRC article to download the security update go to the Github file repository for .NET 6.0.1 to download the fixed version in its entirety, either the whole suite or just the desktop runtime, rather than just a patch. This explains why you weren’t offered the update via WU/WUMgr this time: There was no patch so no KB article and no release to WU. Instead the fix was incorporated into a revised version of the suite and released that way instead.
Kinda goes to show that communication with end users sometimes isn’t exactly MS’s strong suit. Many end users who have installed .NET 6 probably haven’t thought to look back at the Github site to see if there are any new releases for security issues within their .NET setup since it was installed. 🙁
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
