.NET Update Confusion

Topic

New Reply

I’m confused again about what’s going on with .NET updates. The 5/27/21 Master Patch List  advised to defer 4601554, 2021-01 Cumulative Update. I hid it using wushowhide. No subsequent “go” signal noted. The 6/8/21 Master Patch List advises to defer 5003254, 2021-06 CU. I hid that as well. What, if anything, should I do about 4601554? The last .NET update on my PC is 4601050, which was installed when I was still running 2004 prior to moving to 2oH2.

 

Thanks!

Reply | Quote

Replies

I’m using the “enterprise patching” view – none of these recent  .net include new security updates.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I didn’t see any .Net updates for Windows 10 Pro (20H2, 21H1) since 2/2021. Who gets them and who don’t ?

1 user thanked author for this post.

WCHS

Reply | Quote

So, I’m guessing that means don’t worry about any .NET updates until you post one that says INSTALL and is for a new security update?

Reply | Quote

My impression is that the .net updates are not recommended here on Ask Woody unless required by software applications.

Reply | Quote

No, I just want to equate what experience that businesses get. Until there is a security .net patch I don’t recommend it.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

doneager wrote:

The last .NET update on my PC is 4601050, which was installed when I was still running 2004 prior to moving to 2oH2.

Hi doneagar / Alex5723:

See WCHS’s 27-May-2021 KB4601554 – May .NET Framework for a similar discussion. We’re both still trying to figure out why our MS .NET Framework updates stopped after KB4601050 was delivered in Feb 2021. We have observed the following:

• If you view the package details for KB4601050 (2021-02) for Windows 10 v20H2 <here> in the Microsft Update Catalog it says it has been replaced by the the Preview build of KB4601554 (2021-02) released in Feb 2021 (see Image 1), and
• Both WCHS and I have disabled delivery of week C/D Preview Builds in our Group Policy Editor (gpedit) at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (i.e., Enabled, Semi-Annual Channel, defer for 1 day) and did not receive that KB4601554 Preview.

If you search the Microsoft Update Catalog <here> for KB4601554 for Win 10 v20H2 there is both a Preview build for KB4601554 (2021-02) released in Feb 2021 and a “stable” build for KB4601554 (05-2021) released three months later in May 2021 (see Image 2).

If you view the package details for the Preview build of KB4601554 (2021-02) released in Feb 2021 it replaces KB4601050 (02-2021) but was not replaced by any further updates (see Image 3). The supersedence chain for the KB4601050 seems to stops back in Feb 2021 with the KB4601554 Preview (which was never delivered to my system, presumably because of the Group policy edit I made to “Select When Preview Builds and Feature Updates Are Received“).

If you view the package details for the “stable” release of KB4601554 (05-2021) released in May 2021 it replaces KB4586876 (01-2021) and was later replaced by KB5003254 (06-2021) but there is no mention of KB4601050 (02-2021) in those package details (see Image 4).

At this point my best guess is that Microsoft did not revise the supersedence chain of KB4601050 when the “stable” KB4601554 was released in May 2021, and because WCHS and I never received that KB4601554 Preview build (possibly because of our gpedit tweak to “Select When Preview Builds and Feature Updates Are Received“) this has disrupted the delivery chain and is preventing further updates to KB4601050.
——–
64-bit Win 10 Pro v20H2 build 19042.985 * Firefox v89.0.0 * Microsoft Defender v4.18.2105.5 * Malwarebytes Premium v4.4.0.117-1.0.1318

Reply | Quote

lmacri wrote:

If you view the package details for the “stable” release of KB4601554 (05-2021) released in May 2021 it replaces KB4586876 (01-2021) and was later replaced by KB5003254 (06-2021) but there is no mention of KB4601050 (02-2021) in those package details (see Image 4).

My situation is additionally confusing, because I did not install 20H2 until April 9, and so I do not have a record of having the 20H2’s KB4586876 (01-2021) installed because I wasn’t on 20H2 at the time it was released. The corresponding file in 1909 was KB4586878, but it was not in the WU queue to install and so was never installed. I am presuming that it was not there because a) it was not a security update and b) the GUI settings of 1909 were set to achieve the same results that the GP settings of 20H2 are set to achieve.

The last 1909 .NET update was the 2021-02 KB4601056, which was a security update. This 1909 file corresponds to the 20H2‘s 2021 02-KB4601050, which was in the WU queue to download and install ( and I did so) after I upgraded to 20H2. All of this is to say that since the 1909 GUI and the 20H2 GP settings achieve equivalent results, the pattern is the same in 1909 and 20H2: .NET security updates will appear in the WU queue to be downloaded and installed. .NET quality and reliability improvement updates (whether Preview or later stable versions) will not appear in the WU queue.

lmacri wrote:

At this point my best guess is that Microsoft did not revise the supersedence chain of KB4601050 when the “stable” KB4601554 was released in May 2021, and because WCHS and I never received that KB4601554 Preview build (possibly because of our gpedit tweak to “Select When Preview Builds and Feature Updates Are Received“) this has disrupted the delivery chain and is preventing further updates to KB4601050.

but I think there will be an update when the next one is a security update.

Reply | Quote

@WCHS and @lmacri -The .NET updates released since February’s are considered non-security updates by Microsoft. You aren’t seeing them in Windows Update due to your settings in Windows Update for Business (or in the registry for users of the Home edition of Windows 10).

While these settings keep you from being offered the preview updates for Windows and the .NET platform that are generally NOT a good idea to install, a side effect of these settings is that they are also keeping you from being offered the normal, non-security, non-preview updates for the .NET platform.

@WCHS , you are right in that the next .NET update that you will be offered will be one that’s also considered by Microsoft to be a security update.

How do I know all this? Well, because I changed my settings within Windows Update for Business in Group Policy and then used wushowhide to check for available updates. The June update for .NET showed up as available to hide, at which time I exited wushowhide, because I just wanted to see what was available with the changed settings. I then proceeded to revert my settings to those in AKB2000016 and, violà, the June .NET update disappeared from wushowhide.

If you really want to be offered the June .NET non-security update by Windows Update, change the following items in Windows Update for Business (within Group Policy) to “Not configured”: “Select when Preview Builds and Feature Updates are received”, “Select when Quality Updates are received”, and “Select the target Feature Update version”. Just remember to change them back to Enabled along with the individual settings within each one that you had before changing them to “Not configured”.

1 user thanked author for this post.

WCHS

Reply | Quote

Bob99 wrote:

If you really want to be offered the June .NET non-security update by Windows Update, change the following items in Windows Update for Business (within Group Policy) to “Not configured”: “Select when Preview Builds and Feature Updates are received”, “Select when Quality Updates are received”, and “Select the target Feature Update version”.

I ALREADY have “Select when Quality Updates are received” set to “Not Configured.” That means that in the WU queue I get the monthly CUs that come out on Patch Tuesday/Week B, but I can hide them because I have GP=2 (notify download/install). And I never see the CU Previews/Week C or D or E patches. As a matter of fact, I haven’t seen the out-of-band Week B patch KB5004476 either — that one Susan mentions today in the AskWoody Blog. I have TRV set to 20H2. If I change this to “Not configured,” then I am setting myself up for 21H1 (which I don’t want to do)!!

So, what about just leaving “Select Quality Updates are received” to “Not configured,” leaving “TRV” to “20H2”, and changing “Select when Preview Builds and Feature Updates are received” to “Not configured”? Will that bring forth the non-security, non-preview .NET Week B patches to the WU queue? while at the same time, a) allowing Quality/Week B CUs to appear (I’m not talking about.NET updates here), b) preventing Week C/D/E CUs from appearing (I am not talking about .NET updates here, either), and c) keeping me on 20H2? And of course, remembering to set it back to “Enabled” and setting “Semi-Annual Channel” to 1 day after the non-security, non-preview Week B patch shows up in the queue, and I download and install it.

Reply | Quote

WCHS wrote:

So, what about just leaving “Select Quality Updates are received” to “Not configured,” leaving “TRV” to “20H2”, and changing “Select when Preview Builds and Feature Updates are received” to “Not configured”?

I think @Alex5723 has answered that question at
#2370910. He’s got “Select when Preview Builds and Feature Updates are received” to “Not configured” and he has “Select the Target Feature Update Version” set to “Enabled”. As a consequence, he isn’t getting the non-security, non-preview NET week B patches.

So, it seems to me that if you really want a non-security, non-preview Week B .NET patch, the best bet would be to manually download and install it — maybe, waiting until MS-DEFCON = 3+ to do it. That would save you having to go into GP settings to change settings and then remembering to change them back.

Reply | Quote

Sorry, I guess I should have been a bit clearer in my original post…all three of the items I mentioned must be set to “Not configured” in order for you to be offered the non-security .NET updates. I never mentioned the word “all”. My apologies.  🙁

Once you set all 3 to “Not configured”, you should then be offered the regular, non-security update that was released on June 8th.

Once we got to the 15th of June (the third Tuesday of the month), however, the June 8th patch is possibly going to be superseded by a preview release for .NET which you will be offered instead of the update released on June 8th.

Reply | Quote

It seems a bit risky to me to set “Select the target Feature Update version” to “Not configured”, especially since I want to stay on 20H2, now that the later 21H1 is out.

I’m just going to note any new non-preview .NET patch on Susan’s monthly Master Patch List and if it isn’t a security update (which I would expect to show up in the WU queue because of my GP settings) and if I want to install it (i.e., a non-security, non-preview .NET patch, such as that in Week B May and Week B June), I will manually do it (or my McAfee A/V will tell me that it’s not installed and it will install it, if I tell it to.)

That’s easier than taking a risk by not remembering to set all 3 GP settings back to what they were.

Reply | Quote

That sounds like a great plan, because it’s what works reliably for you!  🙂   👍

1 user thanked author for this post.

WCHS

Reply | Quote

What I thought might happen (see #2370912) has actually come to pass. Given the Windows 10 Pro 21H1/21H2 GP policy settings that both Imacri and I have (delivery of week C/D Preview Builds disabled at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (i.e., Enabled, Semi-Annual Channel, defer for 1 day), the next update that IS a security update HAS NOW, in fact, APPEARED in Windows Update, namely the Jan, 2022 Week B .NET Framework patch KB5008876!! It’s the first security update since Feb, 2021 KB4601050.

Reply | Quote

From Susan Bradley’s AskWoody Plus Alert v18.32.1 sent out today (25-Aug:2021):

“In a change to my past update recommendations regarding .NET, I now recommend installing the .NET updates as well. For the last year, I’ve not experienced any side effects with the nonsecurity .NET updates and feel confident about their safety.”

According to my Windows Update history I haven’t received a .NET Framework update since KB4601050 (2102-02 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for 64x) was delivered back on 19-Feb-2021 when I was still running Win 10 Pro v2004.  The release notes <here> indicate that KB4601050 was the last .NET Framework updates that included a security improvement.

I made the following two changes in my Local Group Policy Editor (gpedit) that were suggested in PKCano’s ABK2000016: Guide for Windows Update Settings for Windows 10:

• Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select the Target Feature Update Version is ENABLED and currently set to “21H1” in order to prevent Windows Update from delivering Feature Update v21H2 when it goes into wide release.
• Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received is ENABLED and currently set to Semi-Annual Channel (with Preview Builds and Feature Updates deferred 1 day) to prevent Windows Update from installing week C/D preview builds.

Am I correct that I would have to change both those settings back to their default (Not Configured or Disabled) in order to re-start the delivery of .NET Framework updates that do not include a security improvement (e.g., like the latest KB5004331 cumulative update released 10-Aug-2021)? I agree with WCHS’ comment in post # 2370949 – I don’t like the idea of having to disable that Target Release Version (TRV) setting (and don’t understand why setting my TRV to “21H1” should prevent the delivery of stable .NET Framework updates on Patch Tuesdays in the first place), but I also don’t like the idea of having to manually download and run standalone .msu installers for  .NET Framework updates every Patch Tuesday either.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1165 * Firefox v91.0.2 * Microsoft Defender v4.18.2107.4 * Malwarebytes Premium v4.4.5.130-1.0.1430

1 user thanked author for this post.

WCHS

Reply | Quote

lmacri wrote:

Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received is ENABLED and currently set to Semi-Annual Channel (with Preview Builds and Feature Updates deferred 1 day) to prevent Windows Update from installing week C/D preview builds.

Make a note of your current settings.
Temporarily change only this one to not configured.
There are no Feature updates pending since you are on 21H1 (21H2 is not out and TRV will prevent you from getting it)
Give it a few days and see if the .Net non-Security show up.
If they haven’t shown up by Sept 1st, they are not going to. Change the settings back whether you have them or not.

Reply | Quote

Hi PKCano:

I’d have to test myself, but according to Alex5723’s 12-Jun-2021 post # 2370910 changing that one setting “Select When Preview Builds and Feature Updates Are Received” back to Not Configured will not re-start delivery of .NET Framework updates released after KB4601050 (rel. 09-Feb-2021) that do not include security improvements. If anything, feedback in this thread suggests that enabling “Select the Target Feature Update Version” (TRV) could be the culprit. That’s why I’m confused about the exact Group Policy Editor setting(s), if any, that actually affect delivery of .NET Framework updates that do not include security improvements.
————
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1165 * Firefox v91.0.2 * Microsoft Defender v4.18.2107.4 * Malwarebytes Premium v4.4.5.130-1.0.1430

Reply | Quote

I really don’t think TRV is the problem. I believe it deals with the WinOS version, not .NET

Reply | Quote

PKCano wrote:

I really don’t think TRV is the problem…

Hi PKCano:

Either do I. In fact, I’m not even sure the theory that all .NET Framework updates that do not include a security improvement are treated like an optional Preview update and are not delivered if “Select When Preview Builds and Feature Updates Are Received” is enabled is even correct. It’s just as plausible that there’s a glitch in the supersedence chain of the .NET Framework updates that is preventing Windows Update from installing any .NET Framework updates later than KB4601050 (rel. 09-Feb-2021) on my system – see my post # 2369888. Unfortunately, the only way I can be sure is to leave my Group Policy Editor (gpedit) settings as they are and wait patiently for Microsoft to release another “stable” .NET Framework update that includes a security improvement to see if it’s actually delivered on Patch Tuesday while “Select When Preview Builds and Feature Updates Are Received” is enabled.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1165 * Firefox v91.0.2 * Microsoft Defender v4.18.2107.4 * Malwarebytes Premium v4.4.5.130-1.0.1430

1 user thanked author for this post.

WCHS

Reply | Quote

Yeah, just leave it then. You are not at risk if there are no security holes to fix.

2 users thanked author for this post.

Melvin, WCHS

Reply | Quote

I found this in Woody Leonhard’s 24-Jul-2020 Windows Update is a Bifurcated Mess:

“There’s also some (undocumented) relationship between the TargetReleaseVersion group policy and whether the Preview patch shows up.“

Does anyone have more information about that “undocumented” relationship?

I’m still not convinced that Windows Update treats all .NET Framework updates that do not include a security improvement as if they were a Preview build, but there do seem to be quite a few Win 10 Pro users posting in this thread who haven’t received a .NET Framework update since KB4601050 was released on 09-Feb-2021 who also have the TRV setting (Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select the Target Feature Update Version) enabled in gpedit.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1165 * Firefox v91.0.2 * Microsoft Defender v4.18.2107.4 * Malwarebytes Premium v4.4.5.130-1.0.1430

Reply | Quote

lmacri wrote:

Does anyone have more information about that “undocumented” relationship?

Have you looked at:
1. abbodi86’s observations

2. yes, those rules work. (in answer to my question at #2309288 as to whether the v1909 rule “FU Deferral + TargetReleaseVersion = no CU Preview” works for 2004 and 20H2 and @abbodi86 answers with some additional rules. You have to translate 1909’s “FU Deferral” to the corresponding 2004, 20H2, 21H1 GP settings, of course.)

Reply | Quote

I honestly would leave it as is.  My advice is more for those that were going out of their way to not install .NET and were having to go through such horrific processes to do so.

Susan Bradley Patch Lady/Prudent patcher

2 users thanked author for this post.

Melvin, lmacri

Reply | Quote

I couldn’t figure out why I wasn’t receiving .NET updates, most of which seem to be “non-security. ” So I just started downloading and installing them manually from the Catalog whenever Susan says it’s OK, which hasn’t been often. Seems like this simple solution has been validated and works for me.

Reply | Quote

As a home user newbie, I am wondering whether I should restart my computer for the cumulative update for .net framework (KB5004331) when prompted to do so, or wait until the regular cumulative update is also finished installing (KB5005033) and restart after both are installed?  The second cumulative update other than .net is taking so long and I’m wondering if it needs the restart of the framework in order to complete its work.   Thank you.

Reply | Quote

In the situation you describe, I generally wait for both updates to complete before restarting. In the past, I have responded too hastily to the .NET-generated restart, which interrupted the other larger update. After the restart, the larger update started over from scratch, taking more time than if left to complete in peace before the restart. In my opinion, it is best to avoid  disruption of the process where possible.

1 user thanked author for this post.

Jasmo1046

Reply | Quote

So bottom line is:

Wait for Windows Updater to deliver the next .NET Update

Don’t go looking for a manual update in the Windows Catalogue

Don’t install the most current KB5004331 .NET per the Master Patch List

Correct?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

I fit in the subject title’s group, too. I haven’t received a .NET update since the February KB4601050 for my 20H2 system. Updates shown on the Master Patch List had shown up on my Windows Update until now.

I’ll follow the latest posts from Susan Bradley and PKCano to leave it alone.

So the bottom line to Tex265’s bottom line is don’t install the current KB5004331 unless offered by Windows Updater. 😀

Win 11 Pro 23H2, Office 2024.
Win 10 Pro 64-bit 22H2, Office 2019.
Win 7 Pro 64-bit, Office 2010.
Nethermost of the technically literate.

1 user thanked author for this post.

JLamede

Reply | Quote

The bottom line is don’t install any updates unless offered.
Unless you are testing stuff and have lots of backups.

cheers, Paul

Reply | Quote

Paul T wrote:

The bottom line is don’t install any updates unless offered…

I have a slightly different perspective – at least in this particular case. If I am not receiving .NET Framework updates on Patch Tuesdays that are being offered to other users I’d like to know why.

I understood from PKCano’s ABK2000016: Guide for Windows Update Settings for Windows 10 that enabling my Win 10 Pro Group Policy Editor (gpedit) setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (i.e., Enabled, Semi-Annual Channel, defer for 1 day) would prevent delivery of week C/D Preview Builds. I was not expecting that one of the side effects of changing this setting would be that it would also prevent delivery of “stable” (non-preview) .NET Framework updates on Patch Tuesdays if they did not include a security improvement – assuming that theory is even correct.

If there are unintended consequences to enabling that Select When Preview Builds and Feature Updates Are Received setting I would like to have known that in advance so I could make an informed decision whether I should leave that setting as Not Configured and manage my week C/D Preview Builds another way (e.g., using Settings | Update & Security | Windows Update | Advanced Options | Pause Updates to skip Preview Builds offered on  weeks C/D, using a utility like WuMgr to manage all my Windows Updates, etc.).
——–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1165 * Firefox v91.0.2 * Microsoft Defender v4.18.2107.4 * Malwarebytes Premium v4.4.5.130-1.0.1430

Reply | Quote

lmacri wrote:

f there are unintended consequences to enabling that Select When Preview Builds and Feature Updates Are Received setting I would like to have known that in advance…

I have had the same GP/GUI settings as you have as far back as Feb, 2020 when I was in version 1909. Those settings worked then and I always received the non-preview .NET patches in the WU queue on Patch Tuesday.

The last patch Tuesday patch I have received was in Feb, 2021 and I was on 1909 then. In April, 2021, I skipped v2004 and upgraded to 20H2 by re-setting TRV and by changing the GUI settings to the same GP settings you have.

Then, in early August, I moved to 21H1 by resetting TRV and I kept the GP settings (same as yours) as I had in 20H2.

Like you, I have not received any non-security, non-preview .NET Patch Tuesday updates via WU in 20H2 nor 21H1. But, I don’t think this problem could have been foreseen. I believe that Microsoft changed its habits about Previews (usually in Week C) and their succeeding ‘stable’ versions in Week B. I have noticed that the last 4 Week B .NET patches were issued as a preview in the preceding Week C and then issued in the following Week B as a stable (non-preview) version with the same KB# as the preceding preview.

I am talking about:

But the stable February Patch Tuesday (Week B) was preceded by a Preview that had a different KB#”

I speculate that if a .NET preview (Week C) does not have any security improvements in it, it keeps the same preview KB number when it is released in the following Patch Tuesday (Week B). Although it is now a “stable” version, there must be something in its attributes that makes it destined to appear in the lower half of the WU screen (where optional updates appear) and if you have those GP settings that prevent optional updates from appearing in the WU queue, you will not get these Week B stable, non-security.NET updates. For a related comment, see non-security .NET Week B patch is just a wrapper for the preview.

And, I agree with you that we will have to wait for the next security .NET patch to see if this is correct.

1 user thanked author for this post.

lmacri

Reply | Quote

My notes show back when I was on ver 1909 that I have .NET ver 4.8 and installed KB4578974 .NET back on 10/18/20. Then KB4580980 .NET back on 11/25/20.

Updated to Win ver 2004 in February via WU and held KB4601050 .NET in wushowhide.

Updated to Win 20H2 in April via WU and was still holding KB4601050 .NET in wushowhide.

Updated to 21H1 on August 6 via WU and noted KB4601050 .NET was no longer in wushowhide.

Have not received anything .NET to-date.

WCHS wrote:

Although it is now a “stable” version, there must be something in its attributes that makes it destined to appear in the lower half of the WU screen (where optional updates appear) and if you have those GP settings that prevent optional updates from appearing in the WU queue, you will not get these Week B stable, non-security.NET updates.

I have my Group Policy settings as recommended by PK Cano. I have never seen an optional update section appear in the lower half of the WU screen much less an optional update.

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

I have never seen an optional update section appear in the lower half of the WU screen much less an optional update.

The reason that you are not seeing the optional update section in the lower half of the screen and have not seen any optional update there is because you have PKCano’s settings.

However, there have been 4 non-optional, non-security .NET updates released on Patch Tuesday after KB4001050 (Feb 8/9): 4601554 (May 10/11), 5003254 (June 8/9), 5003537 (July 13/14), 5004331 (Aug 10/11). The first date is the release date in the MS Catalog; the second date is Patch Tuesday).

These 4 should have appeared in the upper half of the screen, since they are non-optional. But, each of these four Tuesday patches (the stable update) has been preceded by a preview. Both the stable one and the preview one have the same KB#. @abbodi86 has remarked that when the KB#s are the same, the stable one is a wrapper of the preview (see just a wrapper). If that is the case, I believe that the preview attributes still remain in the wrapper and this prevents the stable version from appearing in the upper half of the screen. And since you have PK Cano’s settings, they won’t appear in the lower half, either.

2 users thanked author for this post.

Melvin, Tex265

Reply | Quote

So should we go to the MS Catalogue, manually download and install the most current KB5004331 .NET per the Master Patch List?  Or wait for a non-wrappered “clean” .NET Security update?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Tex265 wrote:

So should we go to the MS Catalogue, manually download and install the most current KB5004331 .NET per the Master Patch List?

I don’t know about “should“, but that is what I did because I don’t know how long it will be before a non-wrappered, “clean”, security .NET update comes down the pike and it might be a good idea to be up-to-date on the non-security improvements. I don’t think it’s going to “hurt” anything to do it.

Reply | Quote

lmacri wrote:

If I am not receiving .NET Framework updates on Patch Tuesdays that are being offered to other users I’d like to know why.

I haven’t received any .NET updates for 21H1 since Feb. 2021 and I am not worried.
I have only 3 settings in GP :
‘Notify don’t download’ = 2.
Block drivers updates.
TRV set to 21H1

I use WUmgr to download and run the updates and hide those I don’t want, mainly drivers.

1 user thanked author for this post.

lmacri

Reply | Quote

Although this topic is beyond my skill range, I thought I can add to the discussion by indicating the .NET Framework updates that have been successfully and automatically installed in 2021 on my Win 10 Pro 21H1 (build 19043.1165) Lenovo T-450 laptop.  By automatically I mean after I cancel update deferral when AskWoody raises the patch defense to 4.

Quality Updates:

February 9, 2021-KB4601050 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2

Other Updates:

August 10, 2021-KB5004331 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2, and Windows Version 21H1

July 13, 2021-KB5003537 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2, and Windows Version 21H1

There were 3 more other .NET Framework updates that were Previews during 2021 (one each in March, May, and June).  After reading many sensible comments on AskWoody, I’ve now stopped installing Preview Updates.

Dell XPS17, 11th Gen Intel I7, 64gb RAM, Windows 11 Home 23H2

1 user thanked author for this post.

lmacri

Reply | Quote

Paul wrote:

There were 3 more other .NET Framework updates that were Previews during 2021 (one each in March, May, and June).

I can find neither a March .NET preview nor a following April .NET stable version in the MS Catalog. Do you have a KB#?

Reply | Quote

I also am very confused about not getting the .NET cumulative updates using the Windows Update for Business group policies (as specified in the PKCano guide in Topic 2000016) – and I seem to have plenty of company. I am Win10 Pro and have gone from 2004 to 20H2 and now 21H1.

The last .NET Cumulative Update I got was KB4601050 (2021-02 CU for .NET). It sure looks like I was at Win10 Pro 20H2 at that time. I must have had the same WUfB group policies set then as I do now. The only difference that stands out is security vs non-security.

I don’t have a test system to try out all possible combos of Windows Update settings, so apologies I do not have much to add.

I can add however that when I set all 3 WUfB group policies to “Not Configured” then the 2021-08 CU for .NET magically appeared. And if I set any one of the WUfB policies to “Configured” then the 2021-08 CU would vanish. It feels like it is WUfB itself is hiding things maybe more than one specific group policy.

Does this trigger any thoughts?

And it makes me wonder what else has been being hidden by using WUfB group policies.

Reply | Quote

When I jumped from Win10 Pro 1909 to 2004 – and then 20H2 and then 21H1, I had believed using the Windows Update for Business group policy settings as outlined in topic 2000016 would produce identical results as the GUI settings in 1909. But like so many others here, I no longer get the non-security CUs for .NET.

If I set all 3 WUfB group policies to “NOT CONFIGURED”, then the 2021-08 CU for .NET magically appears. When I set any one of the 3 WUfB policies to “CONFIGURED”, then the CU for .NET vanishes.

Is this representative of experiences by others? It feels like it is the WUfB mechanism itself that hides the non-security CUs for .NET. Am I understanding this correctly?

So if one wishes the non-security CUs for .NET, then the only two choices are to download from the Windows Update catalog or set all 3 of the WUfB group policies to “NOT CONFIGURED” ???

Not wishing to be dense – getting updates in Win7 was so much easier.

Reply | Quote

.NET’s are very confusing in how they are packaged and handled by Windows update.  If you leave your machine and don’t set any group policy settings, you get updates that have bug fixes but not any new security updates.

If you set any of the normal deferrals, you get treated like a “business” patcher and only get offered when a .NET update gets released with a new security update.

What you are experiencing is indeed “normal”.

Susan Bradley Patch Lady/Prudent patcher

4 users thanked author for this post.

paulgutten, Melvin, WCHS, castiel

Reply | Quote

thanks, susan! very helpful, indeed.

i have cited you at https://superuser.com/q/1685906/326187

this “normal” behaviour seems to be a major pain.

Reply | Quote

Thank you so much for this thread!

I have set TargetReleaseVersion/ProductVersion/TargetReleaseVersionInfo and also wondered why I haven’t received a .net CU since KB4601050 (Feb 2021).

That Microsoft handles it like this is quite illogical… (at least in my case) it is clearly a pure windows setting.
Well at least I’ll be spared from the .net preview updates.

As soon as a (future) .net CU contains security updates again, I should receive them again – right?

Thanks and greetings,
Martin

Reply | Quote

Update 11-2021: Still no .net update for WUfB:
2004 + 20H2 still only receives the 02-2021 update (KB4601050) and 21H1 remains on 05-2021 (KB4601554).
There is not any kind of “opt-in for .net updates for WUfB” – right?

Reply | Quote

Hi doneager:

Just an FYI that my January 2022 Patch Tuesday update delivered KB5008876 (Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 20H2, Windows Server, version 20H2, Windows 10 Version 21H1, and Windows 10 Version 21H2 – released January 11, 2022. This .NET Framework update includes a security update that patches CVE-2022-21911.

I haven’t run a manual “Check for Updates” to trigger a Windows Update to look for available updates since my last .NET Framework update was delivered in February 2021 (i.e., KB4601050 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10, version 2004, Windows Server, version 2004, Windows 10, version 20H2, and Windows Server, version 20H2 – released February 9, 2021 that patched CVE-2021-24111) and I don’t use a third-party utility like WUMgr to control my Windows Updates. My results would seem to confirm the theory that one of the tweaks I’ve made to the Windows Update settings in my Win 10 Pro Local Group Policy Editor (gpedit.msc) has the unexpected side-effect that stable .NET Framework updates will not be delivered to my system unless they include a security update.

See my post # 2418023 in WCHS’ May 2021 thread KB4601554 – May .NET Framework for further details.  For now I’m assuming that changing my Local Group Policy Editor setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received to Semi-Annual Channel is the culprit.

However, I have two other GPEdit tweaks (i.e., my Target Release Version at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update is currently set to Windows 10 / 21H2, and delivery of driver updates by Windows Update is blocked at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Do Not Include Drivers With Windows Updates) so I can’t be 100% certain that setting  Select When Preview Builds and Feature Updates Are Received to Semi-Annual is the cause.
———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.1466 * Firefox v96.0.0 * Microsoft Defender v.4.18.2111.5-1.1.18800.4 * Malwarebytes Premium v4.5.0.152-1.0.1538

Reply | Quote

What you say here is true for me, as well, with the exception that
a. I am on 21H1 (and not 21H2),
b. my TRV is 21H1,
c. I have an additional GPEdit tweak whereby delivery of updates by Windows Update is set for 2- Notify for download/install at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Configure Automatic Updates),
d. I don’t ever run a manual “Check for updates” [instead I hide the monthly patches via WUSHOWHIDE, then unhide them after MS-DEFCON is 3+, and wait for Windows Update to give me a “Download” button],
e. I manually installed the August .NET Framework KB5004331 to keep up with reliability fixes.

So, these differences are insignificant with regard to delivery of .NET Framework updates. I can confirm for my system, too, that stable .NET Framework updates will not be delivered unless they include a security update.

P.S. I never get .NET Framework Previews either — only stable .NET Framework updates that include a security update.

Reply | Quote