Comments on AKB 2000016: Guide for Windows Update Settings for Windows 10

Topic

New Reply

Due to the fact that this will be an ongoing discussion, a separate topic has been created.

Please feel free to ask questions about AKB2000016 here.

AKB2000016: Guide for Windows Update Settings for Windows 10.

6 users thanked author for this post.

mije2003, Save_Us_from_MS, LHiggins, TonyC, abbodi86, DriftyDonN

Reply | Quote

Replies

I have some comments concerning the document AKB2000016. I don’t currently have a Windows 10 system. I am a Windows 7 user who is now in the process of buying a new PC and trying to decide whether to install Windows 10 Home or Windows 10 Pro on it. Hence my interest in this document.

1. There are statements on the Internet that the metered connection setting works only for a Wifi connection – it does not work for an Ethernet connection. If this is correct, I think this should be stated in the document. And where would this leave Windows 10 Home users trying to manage updates over an Ethernet connection?

2. I have seen a Windows 10 Home system (at the 1903 feature level) on display in a local store and, in the Advanced Options section, it also had the ability to set an ending calendar date for pausing updates. It therefore appears that Windows 10 Home and Windows 10 Pro have identical function in the Windows Update GUI for pausing updates. If this is correct, I think this should be stated in the document.

3. The document suggests specific settings for managing updates to Windows 10 Pro, but it would be useful if it did the same for Windows 10 Home.

4. The problem I am facing in trying to choose between Windows 10 Home and Windows 10 Pro is that I am trying to build a picture in my mind how I might manage updates with each version. The document lists 4 types of update: Feature, Quality, Optional and Other.

One issue is how do I find out, for each type of update, what updates are available for download and installation? As a Windows 7 user (and a former user of many of its predecessors), I would be tempted to click “Check for Updates”, but the document explicitly warns you not to do this. I can only assume that they just suddenly appear in the Windows Update GUI.

Another issue is, once I know, for each type of update, what is available, how do I either hide the update or install it? I am guessing that wushowhide, the “Download” button, and the “Download and install now” instruction have a role to play in this.

In summary, for my purpose, the document would have been better if it had contained a suggested procedure for managing the updates to each of Windows 10 Home and Windows 10 Pro rather than just suggested settings.

Reply | Quote

1. There are statements on the Internet that the metered connection setting works only for a Wifi connection – it does not work for an Ethernet connection. If this is correct, I think this should be stated in the document. And where would this leave Windows 10 Home users trying to manage updates over an Ethernet connection?

Metered connection for Ethernet was not originally available in Settings, but has been since version 1703. So any articles that say metered connection is only available for wi-fi are nearly three years out of date.

1 user thanked author for this post.

TonyC

Reply | Quote

TonyC wrote:

2. I have seen a Windows 10 Home system (at the 1903 feature level) on display in a local store and, in the Advanced Options section, it also had the ability to set an ending calendar date for pausing updates.

The information on ending date has been added.

The answer for #3 – QKB2000016 says:

The “Pause” period begins when you click “Pause.” If you click “Pause” three times (for example), it will pause updates for 21 days. This should delay updating long enough to see if there any real problems with the patches.

Another issue is, once I know, for each type of update, what is available, how do I either hide the update or install it? I am guessing that wushowhide, the “Download” button, and the “Download and install now” instruction have a role to play in this.

That is correct and is covered in the document.

There is no procedure that is correct for everyone. The individual has to choose the settings that are correct for them. I have given an example in the settings I use for Pro and the reasons I use them. But that does not work for all.

2 users thanked author for this post.

TonyC, Bluetrix

Reply | Quote

Hmm..I am using win1903 Pro AND Home. (different systems) When the pause function appeared in1903, it was the same on both. At the end of the time period selected, some updates were downloaded and installed without any options. Others waited for click to download. It is worrisome that we are not given the option on EACH update. Perhaps Group Edit in Pro would give more choice but seems Home users are in the dark. Wushowhide therefore would be useful in some instances, not in others.

Comments?

Don

Reply | Quote

PKCano, thank you so much for your Update Settings guide. It was invaluable in helping me set up a new W10 pc. The update process is so much more complex that W10’s predecessors.

I began setting up a new W10 pro desktop last week using your recommended settings in your guide. Fortunately, the pc has 1909 installed so I will not have to worry about a version update for awhile.

Pause Updates: It was set to 7 days as set up from Dell

Defer Feature Updates: I changed it to 365 I think; thought I could change it again if needed. This option later disappeared.

Defer Quality Updates: Left at 0.

Used gpedit to change update setting to “2”.

Questions:

1. After setting that, the Defer Feature Updates setting disappeared entirely. Do not know why.
2. On Monday, Windows Update screen showed about 8 or so pending/available updates. I did not take a photo of the screen. Then the list no longer appears on the screen. I do not know why as the updates were not installed. WUshowhide shows no updates to hide. Is this because “pause updates” is set?
3. When the Pause Updates day arrives, how do I know what will be installed? In the last paragraph, you state that you can see what updates are pending, but none show up on this pc.
4. At minimum I should install Svc Stack 4538674 and cum update 4532691 from February. How is this done if there is no list to select from?

I have spent a number of hours trying to resolve these questions, but my searches have been in vain so far.

Why did MS make the update process so convoluted when it was simple, although imperfect, before?

Thanks for your assistance to a W10 novice.

Reply | Quote

Read AKB2000016 more closely. It answers all your questions.

hms wrote:

After setting that, the Defer Feature Updates setting disappeared entirely. Do not know why

Yes. There are settings in Group Policy under Windows Update or Windows Update for Business. As stated, the only setting in Group Policy for Windows Update should be the “2” (notify download/install). The rest should be “Not configured” because any setting there will cause the pulldowns in the WU GUI to be grayed out or disappear. The pulldowns in the GUI is where you should set the Feature/Quality deferrals (they are certainly easier to get to). There are links to show how to set the “2” in AKB2000016.

Then the list no longer appears on the screen.

When you defer, pause, or hide updates, you are telling WU NOT to show them as pending. So they won’t show up in the WU queue until the time is over or they are unhidden.

hms wrote:

When the Pause Updates day arrives, how do I know what will be installed? In the last paragraph, you state that you can see what updates are pending, but none show up on this pc.

When the Pause ends, ALL the available pending updates will download/install irrespective of the “2” setting in Group Policy. Once Pause is ended, you cannot use it again until the pending updates are installed. That is why I do not use Pause (as stated).

 

Reply | Quote

Thanks for the response.

I carefully followed your instructions in sec 3, Group Policy Settings. I set only the “2” notify/download. I did not make any other changes using the Group Policy Settings.

I left the Pause updates to 7 as that seemed to be the instruction before the Defcon setting was raised to 3. My mistake.

When paused updates install, will the optional ones install as well?

Reply | Quote

hms wrote:

When paused updates install, will the optional ones install as well?

Everything that is pending in the WU queue will install. Probably not the optional ones, b/c they will not appear.

hms wrote:

I carefully followed your instructions in sec 3, Group Policy Settings. I set only the “2” notify/download. I did not make any other changes using the Group Policy Settings.

You may have only set what I suggested, but you need to look at what the Vendor of the new PC set. The pulldowns in the GUI will not disappear unless there are settings set in Group Policy in Windows Update and/or Windows Update for Business.
If you use the settings I suggested, you do not need to Pause. The available updates will show in the queue but not download until you click “Download,” thus giving you the chance to hide anything you don’t want to install.
You need to look at the Pause date end. You can extend it by clicking again on the “Pause” button up to 35 days total. You do not want updates until at least 14-21 days after the next Patch Tuesday (that’s Mar 10). Also, there is a Topic discussing how you can extend it farther here. Once you get past this initial pause, with Pro version, I would recommend not using it again.

Reply | Quote

[hms]

The Feature Update Deferral was there until I made the entry in Windows Update. All other settings in Windows Update section are “not configured”. I do not know how to access the Windows Update for Business.

I may just have to reinstall windows to get it back.

 

PS: After sending this, searched the forum. Woody had an article in Computerworld 11/7/2019 – “Disappearing Windows Update deferral pane suddenly reappears”. The article explains that the deferral option may disappear if one enters a different number. This pertained to 1903 and may apply to 1909 as well. May be fixed with an update. May post something in the general forum to see if anyone else has had the issue.

• This reply was modified 5 years ago by hms.

Reply | Quote

[PKCano]

Windows Update for Business is below Windows update, a “subfolder” of it.
And, no, you don’t have to reinstall Windows to get it back.
You should not make the Feature deferral setting in Group Policy – undo that.
You should use the GUI settings only.
The only GP setting should be “2”

• This reply was modified 5 years ago by PKCano.

Reply | Quote

The panel for “Update and Security” has no Business settings folder – just Windows Update.

I changed Feature Deferral in the Advanced Options screen -Pause Updates section. The Quality Update box is still there, but not the Feature Update. As I mentioned in my amended prior post, it was a problem apparently in 1903. I will post in general forum to see if anyone has had this issue in 1909 so I will not bother you anymore with this minor issue.

Thanks for your help.

Reply | Quote

[PKCano]

Please look at this picture. On the left just below the red arrow pointing at Windows Update is Windows update for business.
It is in Group Policy NOT in the GUI panel.

• This reply was modified 5 years ago by PKCano.

Reply | Quote

Oops, sorry. Misunderstood that “Business” was in Group Policy. Checked this section – nothing is configured there. I also “unconfigured” the download setting for the time being since “Pause” seems to be controlling anyway.

Thanks for bearing with me.

Reply | Quote

It’s not the “2” you should unconfigure in Group Policy.
It’s the 365 days deferral that should be unconfigured in Group Policy.
When you unconfigure the deferral in GP, the pulldown for Feature deferral will reappear in the GUI (you may have to reboot).

Reply | Quote

Where is this setting in group policy? I used the GUI drop down when I set it.

Reply | Quote

The settings in Group Policy are either under Windows Update or Windows Update for business. See picture in link three posts above.

Reply | Quote

PKCano wrote:

The available updates will show in the queue but not download until you click “Download,” thus giving you the chance to hide anything you don’t want to install.

So, 1) the updates appear in the queue with a “Download” button and 2) immediately thereafter, you hide the ones you don’t want to install.

So, given 1) and 2) above:
1. Are they hidden immediately, i.e., they then (spontaneously) disappear from the WU screen? Or do you have to wait until the Scheduler does a WU again for them to disappear the WU screen?

2. If you don’t want to wait for the scheduler to act, you yourself can make them disappear from the WU screen by following the instructions of AKB2000013?

3. Does following the instructions of AKB2000013 get rid of the updates altogether (i.e., they no longer exist anywhere, not even in wushowhide ‘show hidden updates’)? Or does following AKB2000013 serve the purpose of making them disappear from the WU screen immediately, but at the same time keeping them hidden (i.e., AKB2000013 updates the WU screen right away)?

Reply | Quote

Please reread AKB2000016 and AKB2000013. The answers to your questions are there. Repeating them would be redundancy.

1 user thanked author for this post.

Elly

Reply | Quote

hms wrote:

Why did MS make the update process so convoluted when it was simple, although imperfect, before?

To be fair, Microsoft’s update process isn’t that convoluted – in fact, it’s rather simple.

End-user attempts to control that update process, to make it into something it isn’t – that’s where you get into convoluted territory.

1 user thanked author for this post.

b

Reply | Quote

I think I asked you this before but I needed to set up a new win10 and so I dug out the “update” settings post and I’ll ask the question I asked before: Is there a *difference* between setting the feature update stuff from  “windows update for business” with gpedit versus doing it from an admin-account Settings->Update & Security GUI?   I realize that setting it with gpedit might mess up the GUI, but if that’s not an issue is there any other benefit to doing it with the GUI?

Reply | Quote

Personally, I find accessing the GUI much easier. The “2” setting in GP is set and forget. But is is a much easier to get to the pulldowns in the GUI. They will not be available if you use the GP settings.

Here’s an example. I maintain/update the Office computer for my Homeowners Assn. I have kept them on v1809 until this morning. What with the quarantining and isolation demands today, I didn’t want to get caught up against v1809 EOL in May.
So, this morning, to do the upgrade to v1909, all I had to do was change the Feature deferral pulldown from 365 days to 120 days and check for updates. A 30-second task (then wait for three hours for the completion of the install).

See AKB2000016 for more information.

2 users thanked author for this post.

Coldheart9020, Elly

Reply | Quote

Thanks for adding and confirming that registry values which emulate the “removed” deferral GUI options from advanced setting still works in v2004

Reply | Quote

AKB2000016 has been updated 8/6/2020.

Included is information on the TargetReleaseVersion settings and how to use them. Screenshots have been added in #2286499.

Other general information has also been added.

5 users thanked author for this post.

Perq, jburk07, Elly, abbodi86

Reply | Quote

I am looking at AKB2000016: Guide for Windows Update Settings for Windows 10 at #2125149, Section 5 for Win10/Pro beginning with 2004. Under Method 2 (Using Group Policy under Windows Update\Windows Update for Business), in the section “for deferrals:” at + Setting Target Release Version, it says “Select the target Feature Update version = Enabled, Target Version for Feature Updates = 1909”

If one has to be on Version 2004 (as the heading for Section 5 says) for the instructions to apply, how is it possible to set Target Version for Feature Updates to 1909?? Or will these instructions also work if you are on Version 1909 and want to remain on 1909 (ala #2286499)?

EOL for 1909 is May 11, 2021. I have FU=365 and that applies to the most recently released version, 2004 (released May 27, 2020), right? So, will Target Version for Feature Updates = 1909 let me remain on 1909 until July 11, 2021 (60 days past 1909 EOL of May 11, 2021)? And if I don’t set Target Version for Feature Updates=1909, will I be pushed to 2004 on May 11, 2021 (EOL for 1909)? Or will I be pushed to 2004 on May 28, 2021 (365 days past May 27, 2020)??

I am trying to figure out how to make 1909 last for as long as is possible.

Reply | Quote

When you use “Feature Deferral” you specify how many days after release you want to wait before being eligible for the next version. The MAXIMUM is 365 days.
In the Target Release Version, you specify which version you want to STAY on or MOVE to.

Windows versions have a life of somewhere around 18 months from release to EOL.
If you use the maximum deferral = 365 days (12 months), you may run out of “deferral” before the actual EOL (somewhere around 547 days).
So, if you want to ride the version out up to the end, you need to switch from deferral=365 to TargetReleaseVersionInfo=the version you want to STAY on. But there is the caveat there, that MS says it will automatically update you to the current version NEAR EOL (and their definition of NEAR may not be the same as yours).

If on the other hand, you are on, say, 1903 and you want to move to 2004, you can set the TargetReleaseVersionInfo to 2004 and you will be offered that version. OR you can move to 2004 by manipulating the number of deferral days.

See #2286499 for more explanation.

2 users thanked author for this post.

Perq, jburk07

Reply | Quote

I thought FU (in the GUI, version 1909) is how many days after the release of the most current version (2004) and not how many days after the release of the version I am on (1909).

You say “Feature Deferral” — is this a reference to the item in the GPE (and not to GUI, 1909)?

And to what does the statement in AKB2000016 that says in #2286499 that “It should also be noted that if the device is not updated before it reaches EOS, the device will automatically be updated once it is 60 days past end of service for its edition” apply? To FU (GUI,1909)?? To GPE > Target Release Version (1909 and 2004)? or both?

Reply | Quote

WCHS wrote:

I thought FU (in the GUI, version 1909) is how many days after the release of the most current version (2004) and not how many days after the release of the version I am on (1909).

Feature deferral begins when the newer current version Feature Update is released and extends for the number of days you set. For that number of days you will not be offered the newer Feature Update.

This is an example (NOT ACCURATE FIGURES):
Say you are on 1903. it was released
2004 was released 94 days ago. 1909 was released 292 days ago.
If you defer for 365 your deferral is greater than 94 or 292 so you won’t get either.
If you set the deferral at 200 days, 2004 has not been deferred 200 days (only out 94) so you won’t get 2004. But 1909 has been out 292 days and it was only deferred 200, so you will get 1909.
If you set deferral at 50 days,, 2004 has passed it’s 94 so you will get 2004.

You get the latest version that’s passed the deferral time.

See my answer above for the rest of your questions.

Edit: Updated “current version” to read “Feature Update” as is explained in the given examples. Apologies for the confusion.

1 user thanked author for this post.

Reply | Quote

PKCano wrote:

Feature deferral begins when your Feature Update is released and extends for the number of days you set. For that number of days you will not be offered a new Feature Update.

Why not just say: Feature deferral begins (or starts) on the date a newer Feature Update version is released ……………etc ?

Saying …. “when your Feature Update is released” …. is what confuses folks as it is often taken to mean the Feature Update you are (currently) using.

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

3 users thanked author for this post.

Perq, b

Reply | Quote

Does that change help you?

1 user thanked author for this post.

Tex265

Reply | Quote

It seems much more clear to me.

A version of this wording seems to come up repeatedly in this post as well as in Susan’s post, Patch Lady – my favorite new windows update setting discussion.

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

Reply | Quote

Tex265 wrote:

…Why not just say:…

I don’t know how many times I have read AKB 2000016 Guide. Plenty. But, I just noticed that Section 3 in AKB2000016 says that feature deferral can apply to several Feature updates at a time. For example, when there are two released versions less than 365 days old (i.e., the newer 2004 and the even newer 20H2), both beyond the older-than-365-day version you are on (1909).

+ Feature update deferral – This setting allows you to defer Feature Updates (twice-yearly version upgrades) for up to 365 days. The deferral starts from the day a Feature Update is released for general use.
It can apply to several Feature updates at a time (My italics). Say, for example, version A was released 220 days ago and version B was released 30 days ago. Setting the deferral to 200 days will allow version A to be available to Windows Update, but not version B. Setting the deferral to 20 days will make version B available. You can choose which version you want to install by setting the appropriate number of deferral days.

In other words, you have to find the sweet spot to get the newer version you want. We can’t talk about 1909 anymore, because it was released more than 365 days ago. But, if you want 2004, then make the number of days be fewer days than when 2004 was released, but at the same time more days than when 20H2 was released. If you want 20H2, then make the number of days be fewer days than when 20H2 was released.

So, it all depends on which “newer” version (2004? or 20H2?) the word newer in the change refers to.

This is to say that it’s best to take a careful look again at AKB 2000016, Section 3, + Feature update deferral and use that to figure out what your deferral number should be.

Of course, the simpler route is to set TRV to the version you want to upgrade to.

Reply | Quote

WCHS wrote:

We can’t talk about 1909 anymore, because it was released more than 365 days ago.

How many days old your installed version 1909 doesn’t matter here. Only how long ago a Newer Feature version(s) has been released.

You still need to keep an eye on that “365 day deferral” as when it runs out, you will be Feature Updated by MS.

WCHS wrote:

But, if you want 2004, then make the number of days be fewer days than when 2004 was released, but at the same time more days than when 20H2 was released. If you want 20H2, then make the number of days be fewer days than when 20H2 was released.

I think this should read: But if you want 2004, then make the number of days be “more” days than when 2004 was released. If you want 20H2, then make the number of days be fewer days than when “2004” was released, but at the same time more days than when 20H2 was released.

 

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

Reply | Quote

Tex265 wrote:

How many days old your installed version 1909 doesn’t matter here. Only how long ago a Newer Feature version(s) has been released.

The point was that you can no longer defer version 1909 if you’re on a previous version.

Tex265 wrote:

I think this should read: But if you want 2004, then make the number of days be “more” days than when 2004 was released.

That would not get you 2004.

Tex265 wrote:

If you want 20H2, then make the number of days be fewer days than when “2004” was released, but at the same time more days than when 20H2 was released.

That would get you 2004.

2 users thanked author for this post.

WCHS

Reply | Quote

You are correct and so is/was @WCHS.

Lost my train of thought I guess.

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

3 users thanked author for this post.

WCHS, b

Reply | Quote

PKCano wrote:

Windows versions have a life of somewhere around 18 months from release to EOL. If you use the maximum deferral = 365 days (12 months), you may run out of “deferral” before the actual EOL (somewhere around 547 days). So, if you want to ride the version out up to the end, you need to switch from deferral=365 to TargetReleaseVersionInfo=the version you want to STAY on. But there is the caveat there, that MS says it will automatically update you to the current version NEAR EOL (and their definition of NEAR may not be the same as yours).

In v1909, If you are using the maximum deferral = 365 days set via GUI, also using  wushowhide and have Group Policy – set to 2 (notify), upon reaching EOL or near EOL will Windows bypass the Group Policy setting and actually install v2004 or will Windows Updater notify you but not download and install the update?  Would wushowhide then allow you to hide it?

If the above is not possible to prolong v1909, does making the setting in Group Policy – Target Release Version to v1909, “gray out”, “remove”, or do anything to the Feature Update deferral GUI in v1909?

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

Reply | Quote

Will Windows bypass Group Policy near EOL – I have never had it happen to me, but it depends on whether or not MS is pushing a given version. I’m not Microsoft, so I can’t guarantee anything.

If you want to use a version past max 365 deferral, you should switch to TargetReleaseVersion settings. But, here again, it depends on whether MS will force the upgrade.

I’m afraid, if you want a guarantee, you will have to take it up with Microsoft.

1 user thanked author for this post.

Perq

Reply | Quote

Tex265 wrote:

If the above is not possible to prolong v1909, does making the setting in Group Policy – Target Release Version to v1909, “gray out”, “remove”, or do anything to the Feature Update deferral GUI in v1909?

PK, any knowledge regarding the second question?  Thx

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

Reply | Quote

I have never tried it. Why don’t you try it and let us know.

Reply | Quote

PKCano wrote:

Why don’t you try it and let us know.

I am on 1909 and have set TargetReleaseVersion=1909. GUI is not greyed out.

2 users thanked author for this post.

Perq, jburk07

Reply | Quote

Some of this stuff is above my head. Any chase you could make an all-in-one .reg or .bat file to apply the settings? Thanks for the great info nonetheless.

 

Reply | Quote

If you want more options, you need to upgrade from Home to Pro Edition. Home has very few options.

There is no “all-in-one” because there are so many different combinations/needs.
If you can’t understand the instructions, there are screenshots (pictures) below the instructions to show how to set things up.

Reply | Quote

[CraigS26]

PKCano wrote:

Will Windows bypass Group Policy near EOL – I have never had it happen to me, but it depends on whether or not MS is pushing a given version. I’m not Microsoft, so I can’t guarantee anything.

If you want to use a version past max 365 deferral, you should switch to TargetReleaseVersion settings. But, here again, it depends on whether MS will force the upgrade.

I’m afraid, if you want a guarantee, you will have to take it up with Microsoft.

I’ve seen NO Date mentioned  BUT … IF (on/about) 11/12/19 was the 1909 Release date – the 365 Deferral is up in about 2 months. What steps are taken to — “switch to TargetReleaseVersion settings — ?

I have BOTH now and per “switch to” above that must be wrong. If I keep 1909 in GrpPol “WU for Business” block/ Select Target Feature Update Ver , what is done with the GUI Deferral setting now at 365 ? (GUI presumed to be Task bar cog wheel/Update & Security/Advanced)

Thanks as always!

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

• This reply was modified 4 years, 6 months ago by CraigS26.

Reply | Quote

+ Set the TargetReleaseVersion to 1909 when the deferral gets close to the max 365 days.
+ You should NOT have Feature deferrals set in Group Policy (which grays out the GUI pulldown), but set with the GUI pulldown instead.
+ Group Policy settings take precedence over GUI settings – TargetReleaseVersion should prevail.
+ So you can leave the GUI pulldown where it is, as it applies to how long the later version (v2004) has been deferred, which was around 107 days on Sept Patch Tues. v2004 was released May 27, 2020 – so you are deferring it for the number of days from that date.

v1909 is EOL on May 11, 2021. MS says it will push an upgrade when the version is “near” EOL. Microsoft’s definition of “near” may not be the same as yours.

5 users thanked author for this post.

WCHS, Perq, Coldheart9020, CraigS26

Reply | Quote

I’m in a self-imposed 10-minute Time-out in the corner for not noticing many of the latest posts. A link takes you to almost the end, I get absorbed there & forget to look above since last visit. Embarrassing!

Finally, in Early May ’21 (just prior  to 2004’s (365) deferral expiration)  when I setup the Grp Pol / WU for Business 1909 Target Release Version — must the 365 Deferral setting then be altered & How if Yes?

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

Reply | Quote

CraigS26 wrote:

Finally, in Early May ’21 (just prior to 2004’s (365) deferral expiration) when I setup the Grp Pol / WU for Business 1909 Target Release Version — must the 365 Deferral setting then be altered & How if Yes?

At this point the question is moot as v1909 will be EOL (May 11). And MS may upgrade you to whatever the latest version is without your asking for it (control). They get very pushy near EOL.

1 user thanked author for this post.

CraigS26

Reply | Quote

PKCano wrote:

At this point the question is moot as v1909 will be EOL (May 27).

At Windows lifecycle fact sheet, it says that EOL for 1909 Win10 Home/Pro is May 11, 2021.

So, are saying the question is moot because EOL for 1909, which is May 11, 2021, is before 2004’s FU’s 365 deferral expiration, which is May 26, 2021, including end date?

And, if you want to stay on 1909, are you saying that you have to set Grp Pol / WU for Business Target Release Version to 1909 BEFORE May 11, 2021?

Reply | Quote

I’m saying that TargetReleaseVersion setting does you no good keeping you on a version after the version’s EOL. It’s not going to keep you safe from a forced upgrade if MS thinks want’s to do so. Microsoft states that in the documentation.

I want to stay on a specific version

If you need a device to stay on a version beyond the point when deferrals on the next version would elapse or if you need to skip a version (for example, update fall release to fall release) use the Update/TargetReleaseVersion (or Deploy Feature Updates Preview in Intune) instead of using feature update deferrals. When you use this policy, specify the version that you want your device(s) to move to or stay on (for example, “1909”). You can find version information at the Windows 10 Release Information Page.

2 users thanked author for this post.

WCHS

Reply | Quote

I’m on the fence right now. I don’t know yet whether I want to stay on 1909 or whether I will change to v 2004 (20H1). If things improve with 2004 in the next month (i.e., before the Oct/Nov 20H2 arrives), I will reduce FU from 365 to a lower value and move to 2004. If things do not improve with 2004, I will want to stay on 1909. So, what is the deadline for me to set the TargetRelease Version to 1909, if things are not improving with 2004?

Or do you suggest setting TargetReleaseVersion to 1909 now and when/if I decide to go to 2004, then change it to 2004?

Reply | Quote

Set TargetReleaseVersion to 1909 now. When you want to install Version 2004, set TargetReleaseVersion to 2004.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

geekdom wrote:

Set TargetReleaseVersion to 1909 now. When you want to install Version 2004, set TargetReleaseVersion to 2004.

And what do I do with the GUI for FU (I’m still in 1909)? Right now I have FU=365, QU=0, GPE=#2, notify download/install.

Reply | Quote

Did you read #2295348?

Reply | Quote

PKCano wrote:

And why is it necessary to keep hijacking threads for your personal instruction?

Please be kind. I have been thinking that members can ask questions for needed instruction. Am I wrong about this?

Am I the only one who cannot keep everything in my head at the same time???

Nevertheless, I am grateful that you pointed me back to a previous post.

1 user thanked author for this post.

DriftyDonN

Reply | Quote

If I am following this correctly, the OP is on ver 1909 (same as me) with GUI Feature Update set to 365 days deferral.

Feature Update 365 deferral days are the number of days since the 1909 release date which was 11/12/2019 = 322 days ago counting today.

So the 365 days deferral will end on 11/10/2020 (even though EOL is 5/11/2021).

We are approaching the point where Windows Update will update us to 2004 unless we switch to utilizing the Group Policy setting TargetReleaseVersion and set it to ver 1909.

If correct, my question is proper sequence for changing from the GUI Feature Update 365 days to the Group Policy Target Release Version setting.  Do you simply leave the GUI 365 setting alone and activate the Group Policy setting? Or carefully lower the GUI to 0 days then activate the Group Policy setting? Or activate the Group Policy setting and then lower the GUI to 0 (or some other number)?

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

Reply | Quote

Tex265 wrote:

We are approaching the point where Windows Update will update us to 2004 unless we switch to utilizing the Group Policy setting TargetReleaseVersion and set it to ver 1909.

Or, with wushowhide and Group Policy =2 (ask to download) can we catch the Feature Update when Windows Update offers it and then hide it like any other update until 5/11/2021 EOL?

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

Reply | Quote

The 365-day expiration isn’t coming up soon. See post #2295348, where PK explained that the feature deferral defers the most current version (2004, not 1909):

“… it applies to how long the later version (v2004) has been deferred, which was around 107 days on Sept Patch Tues. v2004 was released May 27, 2020 – so you are deferring it for the number of days from that date.”

Linux Mint Cinnamon 21.1
Group A:
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux
Win l0 Pro x64 v22H2 Haswell, dual boot with Linux
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux,offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline

2 users thanked author for this post.

WCHS

Reply | Quote

jburk07 wrote:

The 365-day expiration isn’t coming up soon. See post #2295348, where PK explained that the feature deferral defers the most current version (2004, not 1909):

I do think what I said is true, that the 1909 365 day expiration date is coming up.  Higher up in this post on August 29, PK Cano says:

Feature deferral begins when your current version is released and extends for the number of days you set. For that number of days you will not be offered a new Feature Update.

This also agrees with the definitions laid out in the actual Guide AKB2000016.

Not sure, but think a different point was being raised in the verbiage you refer to – that is you can select which new Feature version you want to install by lowering the 365 day deferral on your current version to within a days number range that a new Feature version has been out.  Example of this is also laid out in the actual Guide.

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

Reply | Quote

When PKCano says

Feature deferral begins when your current version is released

I read that to say “… when the current version is released”, in other words NOT your current version (i.e., the version you are on), but the current version (i.e., the latest version available — which would be 2004 right now).

Here’s what Microsoft says

When you defer feature updates, new Windows features won’t be offered, downloaded, or installed for a period of time that is greater than the deferral period set. Deferring feature updates doesn’t affect security updates, but it does prevent you from getting the latest Windows features as soon as they’re available.

Of course, “the latest version available” will have a different reference as soon as 20H2 is released (some time soon).

1 user thanked author for this post.

jburk07

Reply | Quote

[Tex265]

WCHS wrote:

When PKCano says Feature deferral begins when your current version is released

I read that to say “… when the current version is released”, in other words NOT your current version (i.e., the version you are on), but the current version (i.e., the latest version available — which would be 2004 right now

With all due respect by you changing PKCano’s actual words, you change the comment to fit what you say. However using the actual words literally, if at the time you are setting the deferral days, your current version is 1909 the deferral begins from when 1909 is released.

Also using your logic, when the next version after 2004 is released you would get yet another 365 days deferral on 1909.

PK also corrected your initial interpretation of how the Feature deferral works twice when you asked your original question on August 29.

When you use “Feature Deferral” you specify how many days after release you want to wait before being eligible for the next version. The MAXIMUM is 365 days.

Also read the definitions and examples given in the actual  AKB Guide.

Perhaps PKCano will chime in and provide the definitive answer.

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

• This reply was modified 4 years, 5 months ago by Tex265.

2 users thanked author for this post.

WCHS

Reply | Quote

Tex265 wrote:

With all due respect by you changing PKCano’s actual words

Please note that I did NOT change his words … I interpreted them.

Yes, I originally misunderstood “your current version” to mean the version I was on (1909).

Reply | Quote

WCHS wrote:

I read that to say “… when the current version is released”

That is the way I read it as well, based on how PKCano has explained it in the past. I am on version 1909 and have my feature update deferral set to 200 days. If those 200 days were based on the release date of 1909, I should have seen 2004 (or at least that message that it was coming?) by now, since 200 days has elapsed since November 2019. But I haven’t seen hide nor hair of 2004.

Admittedly, the 2004 rollout has been mysterious about which machines are targeted, so it’s possible I’m not seeing it for other reasons.

Seems to me the best and simplest advice is what geekdom advised in post #2295426 above (https://www.askwoody.com/forums/topic/comments-on-akb-2000016-guide-for-windows-update-settings-for-windows-10/#post-2295426}:

“Set TargetReleaseVersion to 1909 now. When you want to install Version 2004, set TargetReleaseVersion to 2004.”

Linux Mint Cinnamon 21.1
Group A:
Win 10 Pro x64 v22H2 Ivy Bridge, dual boot with Linux
Win l0 Pro x64 v22H2 Haswell, dual boot with Linux
Win7 Pro x64 SP1 Haswell, 0patch Pro, dual boot with Linux,offline
Win7 Home Premium x64 SP1 Ivy Bridge, 0patch Pro,offline

2 users thanked author for this post.

WCHS

Reply | Quote

Higher up in this post on August 29, PK Cano says:

Feature deferral begins when your current version is released and extends for the number of days you set. …

This also agrees with the definitions laid out in the actual Guide AKB2000016.

The bolded bit is just plain wrong.

It should say, “… each later …”, not ” … your current …”

I can’t find any definition in AKB200016 which agrees with the bolded phrase here.

3 users thanked author for this post.

WCHS, Tex265

Reply | Quote

Correction: “your current version” changed to read “Feature Update,” as it was explained by the given examples.

2 users thanked author for this post.

WCHS

Reply | Quote

For PKCano and only PKCano to pls answer:

Regarding the Feature Update days deferral setting:

If you are currently on ver 1909 (current version on your system) and you set Feature Update deferral days to 365 days, is that deferring you for 365 days from:

1. the release date of version 1909, or
2. the release date of version 2004 ?

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

Reply | Quote

Here is an explanation of how it works:

PKCano wrote:

This is an example (NOT ACCURATE FIGURES): Say you are on 1903. it was released 2004 was released 94 days ago. 1909 was released 292 days ago. If you defer for 365 your deferral is greater than 94 or 292 so you won’t get either. If you set the deferral at 200 days, 2004 has not been deferred 200 days (only out 94) so you won’t get 2004. But 1909 has been out 292 days and it was only deferred 200, so you will get 1909. If you set deferral at 50 days,, 2004 has passed it’s 94 so you will get 2004. You get the latest version that’s passed the deferral time.

Also see #2299887.

Reply | Quote

To PK Cano:

The crux of  the question here is simply when does the 365 days of deferral run out on ver 1909?

1. 365 days from the release date of 1909, or
2. 365 days from the release date of 2004?

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

Reply | Quote

See #2299963 and #2299887.

Reply | Quote

Based on what PKCano is saying below from post #2299887 dated today, it appears the 365 day deferral period starts from the day a more current Feature Update (2004) is released.

If you have v1909 on the computer, Feature deferral = 365 will keep you from getting v2004 (v2004 was out only 107 days on Sept Patch Tues, so around 130 days now).

Anyone else read something different out of this as this is not what I thought was being previously said.

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

Reply | Quote

anonymous wrote:

Feature deferral begins when your current version is released and extends for the number of days you set. …

So anonymous says this should read: Feature deferral begins when each later version is released and extends for the number of days you set.

PKCano corrects it to read: Feature deferral begins when Feature Update is released and extends for the number of days you set.

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

Reply | Quote

PKCano wrote:

Correction: “your current version” changed to read “Feature Update,” as it was explained by the given examples.

Tex265 wrote:

PKCano corrects it to read: Feature deferral begins when Feature Update is released and extends for the number of days you set.

FINALLY, this is resolved!!

A new Feature Update (20H2) is due anytime soon, I understand.

Reply | Quote

PKCano wrote:

+ Set the TargetReleaseVersion to 1909 when the deferral gets close to the max 365 days.

In am on 1909 and want to stay on 1909. Settings are GPE=2 (Notify download/install), FU=365 and QU=0 and I have not changed those, but I have now set TargetReleaseVersion to 1909.
This is what the Configured Update Policies screen now says. It hasn’t changed from what it said before I set TargetReleaseVersion. Should it say something about setting TargetReleaseVersion to 1909? Or does this screen remain silent on this setting?

Reply | Quote

So on 2004, with group policy settings of deferral for quality updates set to 30 right now, when Woody gives the ok and raises the defcon level to 3 or higher, all I should need to do is : (Listed in order of performing them)

1. Lower the quality deferral number to zero(0)

2. Use wushowhide to find and unhide the monthly September updates for 2004 (.net and the monthly “rollup” for 2004)

3. Click “check for updates” to allow WU to d/l and install the updates

Right? My Automatic Updates setting is enabled, with a value of 2.

Reply | Quote

Bob99 wrote:

1. Lower the Quality deferral number to zero(0)

Set Quality deferral at 0 (zero) and leave it there. You do NOT need to set Quality deferral if you have GP setting of “2” because the updates will NOT download unless/until you click the “Download” button. If you set a deferral you cannot see what is pending to be able to hide what you don’t want.

Bob99 wrote:

2. Use wushowhide to find and unhide the monthly September updates for 2004 (.net and the monthly “rollup” for 2004)

You DO NOT need to hide updates you want it you have GP setting “2” because the updates will NOT download unless/until you click the “Download” button. Only hide what you do not want. You are putting in controls then invalidating them with other controls. You can’t see what you’ve got if you keep deferring and hiding what you want to install.

Bob99 wrote:

3. Click “check for updates” to allow WU to d/l and install the updates

NEVER, NEVER, NEVER click “Check for updates.” If you have the GP setting of “2” there will be a “Download” button (when you leave Quality deferral – 0) – click on that.

2 users thanked author for this post.

opti1, Perq

Reply | Quote

The problem is is that I had deferral for quality updates set to zero on one of my machines earlier this month, and a definition update for Windows Defender showed up in WU and was the only thing listed as pending. So, I clicked on the button to d/l and WU installed not only the definition update that was listed but the September updates for 2004 and .net! That’s why I have quality updates set to 30, so that doesn’t happen again. Once bitten, twice shy.

Reply | Quote

If you leave the Quality deferral at zero, all the pending ones show up and that won’t happen.
When WU scans, the list of available updates are stored in a cache, and that’s what you see in the queue. The cache is not refreshed until the next WU scan by the system. It is a static list between scans.

wushowhide uses the same Windows Update service to scan, but the list is current b/c you initiate the scan. But if you have deferral set, wushowhide can’t see the pending updates either.

If you leave the deferral at zero, when you use wushowhide you get a current list. What’s in the WU queue will match it when the system initiates a WU scan (then the cache is refreshed).

As long as you have Quality deferral set, you’re flying blind b/c neither tool can work for you.

4 users thanked author for this post.

opti1, Perq, LHiggins, jburk07

Reply | Quote

Ok, another question (thanks for the clarification above, BTW): Usually (9.5 times out of 10) we don’t want the weeks c/d/e “preview” patches that are released. I haven’t seen them appear yet for September, which is a good thing.

However, should the need arise to get one d/l’d and installed due to fixing a really bad problem with a system of ours, how would we go about getting it to show up in WU to download and install? Or, would we have to go get it from the Catalog instead?

Reply | Quote

You can do that two ways (if you want the Previews).
You can download from the Catalog and install manually.
OR
You can click “Check for Updates” or the “Download and install now” link( if the latter shows in WU).

1 user thanked author for this post.

Perq

Reply | Quote

Good morning! I am glad to see that this topic is still active, as I find I have a few questions about a Win 10 Pro initial set-up. I have finally bitten the bullet and ordered a refurbished Dell laptop – seems pretty nice – 16 GB RAM, 512 GB SSD. I am planning on keeping my Win 7 Thinkpad around, but it seemed time to take that next step.

So – I will be going through all of the set-up steps once the laptop arrives, and find that I have a few questions.

I am not sure if the laptop will come with 2004 or 1909 – and Dell just says “Version will be updated to the latest one as soon as you connect to the internet and start the Windows Updates.”

So – after I do all of the offline set up and set Feature Updates as indicated by PKCano – my question (I think) is – once I go online, before doing anything else, should I run WUSHOWHIDE and hide any upgrade to 2004 that shows, or will setting the feature update deferral keep 2004 from even showing up in Windows Update in the first place?

Or to quote a post in an earlier discussion 1736802: “What eventually occurs the first time I allow updates to install after I initially block everything? Is the initial blocking so I can hide anything unwanted before I allow the first round of updates? ”

I really don’t want to start out having to do that upgrade right away, and would prefer to be able to get comfortable with it all first.

Or – will hiding that in WUSHOWHIDE “remove” it from the update queue if it is there, as long as I don’t check for updates?

And I guess one other WUSHOWHIDE question – does an update need to be hidden before it shows up in the Windows Update queue or will hiding it after make it disappear?

Thanks for the help. I have done some of this about a year an a half ago but just wanted to refresh my memory on this one part of the process since last time, the Feature Update was not imminent and I had time to sort it all out before that eventually became available.

Reply | Quote

The initial setup should be done OFFLINE (not connected to you network) if you want a LOCAL ID. If you connect to your network, you will be forced into a MS ID.
It will ask you several times during the initial setup if you want to update and look for drivers. The answer is NO (you are offline).
Then you need to set Windows Update so you don’t get bombed when you do go online.

If you have v1909 on the computer, Feature deferral = 365 will keep you from getting v2004 (v2004 was out only 107 days on Sept Patch Tues, so around 130 days now). If you have v2004 on the computer, 365 days will keep you from getting 20H2. If you have anything earlier than v1909, setting Feature deferral at 200-250 days should get you v1909, then you can set it up to 365.
Depending on which version (1909 or 2004), use the Group Policy settings in AKB2000016 for that version (I am assuming you are getting Win10 Pro).

Beside WU, you should also go through all the settings in the Settings App and adjust them for your level of privacy BEFORE you go on line.

The only thing you need to hide with wushowhide are updates you don’t want, like drivers, Previews, etc. The patches you DO want will just sit in the queue until you click the “Download” button if you have the “2” set in Group Policy.

2 users thanked author for this post.

opti1, LHiggins

Reply | Quote

[LHiggins]

Thanks so much – just what I was looking for!

PKCano wrote:

Then you need to set Windows Update so you don’t get bombed when you do go online.

Yes, that is what I wanted to avoid.

PKCano wrote:

If you have anything earlier than v1909, setting Feature deferral at 200-250 days should get you v1909, then you can set it up to 365. Depending on which version (1909 or 2004), use the Group Policy settings in AKB2000016 for that version (I am assuming you are getting Win10 Pro).

Yes – Win 10 PRO. And I am just guessing that it might be 1909 – could be earlier. Is there an easy way to tell which it is?

PKCano wrote:

The only thing you need to hide with wushowhide are updates you don’t want, like drivers, Previews, etc. The patches you DO want will just sit in the queue until you click the “Download” button if you have the “2” set in Group Policy.

Great – thanks! I thought that I might need to do something with 2004 if it was there. Glad the deferral settings should take care of it.

Hoping to get the new one delivered next week – so I will post any other questions as they come up – though the guide is very clear as to the steps. And yes – OFFLINE for sure – I definitely don’t want a MS account, and plan to disable Cortana right off as well.

And – I’ve learned my lesson about admin and standard users, too. I am planning to set up both types of accounts and use the standard account as my everyday account. When would I do that – after setting up the deferrals, etc?

Thanks again!

ETA – just got the notice that this laptop has shipped and might be delivered this week – 10/1! Fast – wow!! Guess I’d better get all of my instructions organized – LOL!

 

 

 

• This reply was modified 4 years, 5 months ago by LHiggins.

Reply | Quote

LHiggins wrote:

Yes – Win 10 PRO. And I am just guessing that it might be 1909 – could be earlier. Is there an easy way to tell which it is?

When you get to the desktop for the first time, run winver and it will tell you version and Build.

If you need help, create a topic and we can step you through it (using your other PC).

1 user thanked author for this post.

LHiggins

Reply | Quote

PKCano wrote:

If you need help, create a topic and we can step you through it (using your other PC).

Thanks! I’ll see how far I get and I will create a new topic if need be!

Thanks again!!

Reply | Quote

PKCano wrote:

If you need help, create a topic and we can step you through it (using your other PC).

Yep – I do need help. Started a new topic since I find that this laptop is on V 1809 and have questions.

Thanks!

Reply | Quote

Already answered

Reply | Quote

One more detail, if I may…

LHiggins wrote:

And – I’ve learned my lesson about admin and standard users, too. I am planning to set up both types of accounts and use the standard account as my everyday account. When would I do that – after setting up the deferrals, etc?

Thanks!

Reply | Quote

You need to do the WU settings under the Admin account. In fact, it’s best (IMO) to do all system and install tasks under the Admin and just use a Standard account for everyday activities.

1 user thanked author for this post.

LHiggins

Reply | Quote

I am running Windows 10 Pro, Version 1909.  Several weeks ago, I set the Feature Update Deferral = 365 and the Quality Update Deferral = 0 AND, in Group Policy, I set Configure Automatic Updates = ENABLED, Value 2.  The problem is that I am no longer getting the Security Intelligence Updates for Microsoft Defender Antivirus which used to install automatically on nearly a daily basis.  I would like the Security Updates to continue to install automatically.  Is there a work-around for this?

Reply | Quote

I have not looked at this b/c I use Bitdefender Free on my Win10 and it turns Defender off.
I was under the impression that the definitions were applied even with the “2” settings.
I can suggest you look at the Defender definition versions and verify they are not being updated. If not, then check the settings in Defender and in Group Policy to possibly set updating. Maybe set up a task in Task Scheduler.

Reply | Quote

billk22 wrote:

I would like the Security Updates to continue to install automatically.

I have your settings in v1909. (FU=365, QU=0, GPE=2 (notify download/install)). I hide the monthly Tuesday patches until MS-DEFCON is 3 or greater and then I unhide them. But, Defender updates always appear in the WU display with a download button, whenever there is a new version available. So, Defender updates do not install automatically with GPE=2; you have to click the download button, whenever it comes up.
Here’s the screen that just appeared in my WU display.

I have McAfee Security Center installed but Windows Defender does periodic scanning as well and updates regularly as you see in the screen above. To get Windows Defender to do the periodic scanning, at the bottom of the Update & Security > Windows Security > Virus & threat protection screen, I have periodic scanning turned on.

Reply | Quote

Except that, yesterday, my WU screen had a Defender update AND a Preview update for .NET Framework…. so, if I clicked on Download, I’d get the Preview too, which I don’t want.  Today, only the Preview update is showing up… the Defender update has disappeared.  How do I get that back?  Actually, is it possible to get all Defender’s Definition Updates since 8/26/20?

If I disabled the GPE setting and set QU=28, would I have any control over Preview and Other updates?

Reply | Quote

Did you check to see if the Defender update went ahead and installed, not just disappeared? Are you checking the Defender definition version numbers/dates?

Reply | Quote

[Tex265]

@billk22

I have the same settings as you.

Defender Definitions “usually” show up in the Window Update GUI, but not always.  Whether they show up or not, they will always self install whether you click the Download/Install button or not if you wait awhile.

If it appears and you click Download, it will install and appear in the Update History. If it self installs, it will not appear in the Update History, but is still installed.

You can check in the Settings for Defender to see what version is installed, or better is to go to Search in the Task Bar and search for “Reliability History”. This will show everything that installed on a given day including the Defender Definitions, version number, and time.

If you didn’t click Download the entry shows up once. If you clicked Download the entry show up twice (makes me wonder if always installs automatically and the Download button does it again).

If Defender update appears in Windows Update with other Updates, just wait and let it self install, then it will disappear after the next automatic Windows Update takes place.  Of course by then there may be a newer Defender update available.  The only way I know of to separate Defender updates from other Updates you do not want to install is to use the wushowhide tool and hide the Updates  you do not want to install.

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

• This reply was modified 4 years, 4 months ago by Tex265.

1 user thanked author for this post.

Perq

Reply | Quote

Tex265 wrote:

The only way I know of to separate Defender updates from other Updates you do not want to install is

There is another way to separate out a Defender update so that you get the latest one available:

Update & Security > Windows Security > Virus & threat protection > scroll down to Virus & threat protection updates and click on the link “Check for updates” This will tell you the version that is installed. Then, if you click on the button that comes up for “Check for updates,” you will get the latest one, if available, and it will then show up in the Reliability Monitor (aka Reliability history), too.

1 user thanked author for this post.

Perq

Reply | Quote

**NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both.
If you use TargetReleaseVersion, set deferrals to 0 0r 1, as they are going to be ignored anyway.

Reply | Quote

I’m v1909, TargetReleaseVersion=1909, FU=365, QU=0, GPE=2 (notify download/install)

Don’t Optional Cumulative Update Previews and Optional Cumulative Update dotNet Previews fit into the category of Feature Deferral? If you have TargetReleaseVersion set and you have no Feature Deferral set, then how do you avoid these optional preview updates?

Reply | Quote

Previews are NOT Feature updates. Feature Updates are version changes (1909 -> 2004, 2004 -> 20H2).

You should NOT use BOTH Feature deferrals and TargetReleaseVersion settings. If you have TargetReleaseVersion set, the 365-day Feature deferral is ignored (according to MS documentation). If you use TargetReleaseVersion, set deferrals to 0 0r 1, as it’s going to be ignored anyway.

Both methods work individually, just not together.
Choose one or the other, whichever is easier for you to remember, and stick with it. It works unless MS arbitrarily changes things (for which we have no advanced warning or control over).

Reply | Quote

I know that Previews are NOT Feature Updates, but my understanding from @abbodi86 #2284115 is that they are in the category of Feature Update, i.e. they are handled in the same way as Feature Updates.

Reply | Quote

PKCano wrote:

You should NOT use BOTH Feature deferrals and TargetReleaseVersion settings. If you have TargetReleaseVersion set, the 365-day Feature deferral is ignored (according to MS documentation).

If TargetReleaseVersion=1909, FU=0, QU=0, GPE=2-notify download/install, is there a GPE setting anywhere that will prevent CU Previews (i.e., Week ‘C’ or ‘D’ or ‘E’ CU patches) from being offered in the ‘Optional updates available-download and install’ area of the WU display?

Reply | Quote

Actually in my brief tests, with TargetReleaseVersion set, if you also set FU deferral to even 1 day, it will prevent CU Preview

5 users thanked author for this post.

WCHS, Perq, Elly, jburk07

Reply | Quote

New user here with two wushowhide questions:
 

1. I read your guide and mention to uncheck “Automatically Apply Updates”. What does that do and why uncheck? I believe the default is checked.
2. WUSHOWHIDE has always worked well for me. However,in the last month every time I use wushowhide and either click hide or show – nothing more needed, it throws elevated errors. They appear in user/appdata/local/elevateddiagnostics.There is a cab containing the same files as appear separately. All .xml except for one .sml schema. I do not see anything that shows a real error. There is no windows error report.
   I’ll be happy to upload the .cab if that helps diagnose the issue. I only found it by using CCleaner and I KNOW for sure this has not happened before.

Appreciate your replies and thoughts.

Reply | Quote

wushowhide is a troubleshooter. Unchecking the box means any changes won’t be applied automatically. They need tobe applied manually.

Are you using a Administrator ID or a Standard ID?
I have never seen the errors you are talking about, and I use wushowhide all the time.

Reply | Quote

Thanks, but I am still confused. It is checked now. If I hide an update, it is hidden from updates. At least the next day. If I unhide, same, it unhides.

You are saying I should uncheck and then do something else to hide if that is what I am trying to do?

Sorry, just not clear to me.

Using my ID, but I am administrator. I have not seen these errors for years and not until perhaps a month, maybe less ago. Would uploading the .cab be helpful?

Thanks.

Reply | Quote

Not necessary to upload the cab. It’s probably too big anyway.
Uncheck the box and see if the error disappears.

Reply | Quote

Sorry, been busy for a few days.

.cab is only 50 KB. Very small.

Even with Apply Immediately unchecked still throws the error every time Show or Hide is run to check. Check user/appdata/local/elevateddiagnostics to see if you have anything there PKCano. I never did see these before very recently.

And still not understanding the reason to uncheck Automatically Apply? If I want to Hide a new Update, I would want it to apply now, mo? Same with Unhide. If I had a reason to Unhide I would want it to be available to download now, no? So why uncheck and if I do what is the expected workflow?

Thanks.

Reply | Quote

anonymous wrote:

Check user/appdata/local/elevateddiagnostics

Nope, nothing

Reply | Quote

Interesting. Thanks for checking. Makes me wonder why me then? And also why my posts here are coming as anonymous as I sign it before posting.

One of those days.

I have googled this and will try one more time.

~Bob

Reply | Quote

Update: Elevated Diagnostics are now captured not only from using wushowhide, but anything Windows Update such as attempts to download and install that Printer update from 2006 which in itself is baffling. So seems something related to Win 10 update has activated ElevatedDiagnostics.

Reply | Quote

Look in Settings App\Privacy\Diagnostics & feedback
Minimal is:
“Required diagnostic data”
Improve inking and typing = OFF
Tailored experiences = OFF
Feedback frequency = Never

Reply | Quote

Just a heads up for folks: The TargetReleaseVersion setting’s name in version 2004 has changed. It is now called “Select the target Feature Update version” instead of what it was called before. Its location remains the same within GPEdit.

I just noticed this a couple of days ago while seeing exactly what value would get the 20H2 update to show up in wushowhide. Turns out that to get 20H2, I had to enter “20H2”, not 2010 or 2009 as has been previously reported elsewhere on this site. So, I guess that’s yet another change that MS has thrown our way.

BTW, the testing I did was conducted on a fully updated (including the November updates) Win 10 Pro x64 system, version 2004 winver 19041.630.

R/

Bob99

3 users thanked author for this post.

WCHS, Perq, abbodi86

Reply | Quote

I used a link I found on AKB 2000016 I thinks ..not sure which one..to pause or stop updates..possibly by setting a group policy. Now when I check windows update..I come upon “Pause isn’t available per your organizations policy” I own the Pc..there is no organization. I want to stay with 1909..but since the Pc hasn’t been updated since October 2019, I’d like to get the updates..I bought it as a clean refurb a month ago..Win10 Pro. Thanks for any help you care to provide.

Reply | Quote

The message you are getting (“Pause isn’t available per your organizations policy”) is most likely due to settings that have been made in Group Policy (the organization).

There is a link at the top of this thread to AKB2000016. I would suggest you read through the information. There are two ways to stay on v1909: Setting Feature Update Deferral OR using TargetReleaseVersion settings. Both methods are explained there, and there are screenshots below the text to show where the settings are located. I would also suggest you remove settings that don’t match the method you choose.

Reply | Quote

@PKCano –

I know that all the monthly updates for Win 10 are labeled “LCU” for Latest Cumulative Update, and I also realize that WU will silently download and attempt to install the latest SSU before installing the LCU for the current month.

However, given that @MrToad28 says that the PC hasn’t been updated in just over a year (since Oct 2019), would he perhaps be required to install an SSU from somewhat earlier this year in order to successfully download and install the latest SSU and LCU for November through Windows Update?

Reply | Quote

I don’t think he needs to do anything if he goes through Windows Update. The CUs are cumulative and he will get the latest SSU along with it.
He’s just got to straighten out Windows Update.

Hopefully, setting GP will do that (unless there is another problem blocking it). But the message he’s getting (in my experience) is due to GP settings somewhere. I think @b ‘s link below will help locate it. If the refurb was on a domain, there may be other “User hands-off” settings as well.

Reply | Quote

@PKCano –

Yep, you nailed it! I just found the setting within GPEdit for @MrToad28 to look at and change!

Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Windows Update

(BOY, what a long path!)

In the settings that show when “Windows Update” is highlighted on the left side of the window, slowly scroll through the myriad of preferences on the right side of the window until you come upon the one that says

“Remove access to “Pause updates” feature”

Make sure that item is either set to “Not configured” or set to “Disabled”.

That should do it. On my machines, it’s set to “Not configured”

Reply | Quote

OOPS! Same thing that’s stated in the link that @b posted below. However, that link is for enabling the lack of access, not for disabling the lack of access.

Oh well, six of one half dozen of the other.

Reply | Quote

Bob99 wrote:

However, that link is for enabling the lack of access, not for disabling the lack of access.

The link describes how to do either one.

Reply | Quote

Since version 1909’s release date was November 12. 2019, it seems that the Feature Update deferral of 365 days won’t work any more for staying on 1909, since we’re now at the end of November 2020.

Shouldn’t the folks wanting to stay on 1909 now ensure that the TargetRelease Version item is set to 1909 instead?

Reply | Quote

v2004 was released May 27, 2020 – hasn’t been near 365 days of deferral yet. 365 Deferral is still good on v1909 till around May 2021. You are deferring the next versions.

1 user thanked author for this post.

Perq

Reply | Quote

See How to disable the ‘Pause updates’ feature

Reply | Quote

Following @bob99 advice: the Pause updates feature..was set to not configured..but I changed to disabled
Still seems Blocked
Under settings I found “view configured update policies”
All are source: Admin. Type: Group policy
Policies set on you device:
Disable Pause updates by user
End date for pausing quality updates
En able quality update deferral
Quality update deferrel period

Thanks for the help guys..I’ve been doing windows PC’s since early 1990’s it bothers me that I can’t seem to fix this..If I let updates rip..I fear they’ll do just that..but now I got year long update constipation. D*****d if you do….

Any way, really appreciate the guidance.

Reply | Quote

Try rebooting your computer and see if anything’s changed.  As I mentioned in my earlier post,  I have the “Remove access to “Pause updates” feature” setting at “Not configured” on my computers. However,  I would think that setting it to “Disabled” would accomplish the same thing.

R/

Bob99

Reply | Quote

@PKCano –

What should @MrToad28 expect to see once he gets the pause updates straightened out? The November patch for 1909, the latest .net patch and drivers that have been released since October of last year that MS thinks he’s “worthy enough” (in their opinion) to receive?

Reply | Quote

PKCano wrote:

Look in Settings App\Privacy\Diagnostics & feedback
Minimal is:
“Required diagnostic data”
Improve inking and typing = OFF
Tailored experiences = OFF
Feedback frequency = Never

Thanks. Sorry for the slow reply.

Everything there is off. I think I have set something in GPEdit a while ago so that sections show managed by my Admin (me :). All off or grayed. And I have not set or changed anything there in a long, long time.

So just to remind, this started recently. MAYBE(?) with an ESET update a month or so ago? Possible? I looked but did not find a new option that seemed to correlate to this. But never had these before and anything that touches windows update triggers those elevated diagnostics.

The cab is small. The reports inside small and in xml. I have looked and do not see anything of interest showing why these elevateddiagnostics have started.

~Bob

 

Reply | Quote

Sorry, may have replied to a post that was not directed to me.

Reply | Quote

Reply wherever you want, we don’t mind.

cheers, Paul

Reply | Quote

Actually it was in reply to a comment directed to me. Was a bit hard for me to follow the threading as I replied being new here to these topics and formats. So question is open as to why these new elevateddiagnostics.

Reply | Quote

MrToad28 wrote:

the Pause updates feature..was set to not configured..but I changed to disabled

Change it back to not configured and reboot. Any joy?

cheers, Paul

Reply | Quote

rebop2020 wrote:

PKCano wrote:

Look in Settings App\Privacy\Diagnostics & feedback
Minimal is:
“Required diagnostic data”
Improve inking and typing = OFF
Tailored experiences = OFF
Feedback frequency = Never

Thanks. Sorry for the slow reply.

Everything there is off. I think I have set something in GPEdit a while ago so that sections show managed by my Admin (me :). All off or grayed. And I have not set or changed anything there in a long, long time.

So just to remind, this started recently. MAYBE(?) with an ESET update a month or so ago? Possible? I looked but did not find a new option that seemed to correlate to this. But never had these before and anything that touches windows update triggers those elevated diagnostics.

The cab is small. The reports inside small and in xml. I have looked and do not see anything of interest showing why these elevateddiagnostics have started.

~Bob

 

OK, more thinking. Since this is Elevated Diagnostics and never happened until recently, could something have changed permissions on trouble shooters to force Run as Administrator or do they always run that way? There is a setting under advanced for the Show/Hide shortcut for run as admin, but it is unchecked.

Reply | Quote

Is there some other place you would post this seeking the answer for what changed to activate elevated diagnostics?

Reply | Quote

PK, as my signature indicates, I have 2 machines now. My question is with the refurbished Windows 10 machine that I’ll be buying from a friend soon. They’ve been kind enough to let me “try before I buy”, & they have never used it since they completed a training course. I just today decided to access this AKB, & my question relates to applying the December 2020 patches when MS-DEFCON changes, probably this week.

Background: My Win10 machine is currently running Version 1909. It was on 1903, but I updated to 1909 before the previous version reached EOL. Feature Update deferral is set to 365 days. My machine has Conexant audio, so until those drivers are updated, or I decide to bypass them & use Microsoft default audio drivers instead, Microsoft won’t put Version 2004 on my machine. I’m cool with that, since neither Patch Lady Susan, you, nor any of the other AskWoody Bosses have okayed it yet. I’ll worry about 2004 (or 20H2, for that matter) when I’ve heard that the Green Light has been given.

My specific question is about applying patches AKA Quality Updates. On Dec. 7, the day before this month’s Patch Tuesday (Dec. 8), I set the Quality Update deferral to 30 days. I think this is how Woody showed the GUI set. Having finally read AKB 2000016, I learned that you recommend Quality Update deferral be always set at 0. Similar to how Win 8.1 works (my old reliable), it will show that the patches are present & ready, but I must click a button or link to “Download and install now”.

Here’s my plan when MS-DEFCON changes to 3, 4, or 5: Change the Quality Update deferral to 0 days, verify that the proper patch appears & is ready to install, then click on the button or link to let Microsoft make the Magic happen. Of course, backups will be done 1st. Leave Quality Update deferral at 0 for the foreseeable future. Obviously this machine has Win 10 Pro installed, or I wouldn’t be talking about these GUI settings. I’d be using the Pause Updates for Win 10 Home. I’ll be notified via e-mail on my Win 8.1 machine for any follow-up replies, so let me know if I’ve got this right, or should do something different before MS-DEFCON changes. As for the current 30 day setting, if I do nothing, patches should appear on 01/05/21. This is the “A” week Tuesday, when non-security Office patches are dropped. Thank You!

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

There are three settings you need for Win10 Pro 1909. They are explained in AKB2000016 Sections 3 and 4. There are screenshots below (scroll down) to show where the Group Policy “2” is located. (You also need wushowhide.):

GUI: Windows Update\Advanced settings Feature Deferral pulldown =365, Quality Deferral pulldown = 0
Group Policy:
Computer Configuration\Administrative Templates\Windows Components\Windows Update
Configure Automatic Updates = Enabled, value = 2 (notify download/install)

By setting the “2” in GP, the updates will not download to your PC until you click the “Download” button (NOT “check for updates”). This will allow you to hide the ones you do not want with wushowhide, then clear the WU queue, so you only have the ones you want showing in WU. Then you can download.

Using those settings, you do not need Pause or Metered connections.

When you get ready to upgrade to 2004 (or later) you will need to change the settings as stated in AKB2000016 Section 5, as the GUI pulldowns will no longer be available. This change should be done immediately prior to the upgrade so they are in effect for 2004 from the start.

2 users thanked author for this post.

Perq, WildBill

Reply | Quote

Maybe some one could parse this MS Doc quote for me:

When you set the target version policy, if you specify a feature update version that is older than your current version or set a value that isn’t valid, the device will not receive any feature updates until the policy is updated. When you specify target version policy, feature update deferrals will not be in effect.

The first sentence seems (to me) to be implying I could set the version to say 1111 and I would

not receive any feature updates until the policy is updated

from https://docs.microsoft.com/en-us/windows/deployment/update/waas-wufb-group-policy#i-want-to-stay-on-a-specific-version

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

Correct, but for clarity it’s best to use a valid number.

cheers, Paul

1 user thanked author for this post.

wavy

Reply | Quote

If I am reading Section 5. Method 2 with corresponding screen shots correctly, after all the directions and commentary, it appears we need to Enable and set only one (1) item under GP Windows Update > Windows Update for Business.  And that is “Select the target Feature Update version”.

“Select when Preview Builds and Feature Updates are received”  is to utilize Feature Update deferral days and this should not be set when utilizing Target Release Version setting. Or Enabled with deferral days set to 1 or 0. But then advised it will be ignored anyway so why not just leave as Not Configured.

“Select when Quality Updates are received”  should be set to 0 days or left Not Configured.

There is no commentary provided to do anything with the remaining two (2) settings:

“Disable safeguards for Feature Updates”  Default =Not Configured

“Manage preview builds”  Default = Not Configured

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

Reply | Quote

Tex265 wrote:

“Select when Preview Builds and Feature Updates are received” is to utilize Feature Update deferral days and this should not be set when utilizing Target Release Version setting. Or Enabled with deferral days set to 1 or 0. But then advised it will be ignored anyway so why not just leave as Not Configured.

My understanding is that if you Enable with deferral days set to 1 or 0, you will not get any Previews on the WU screen (not even with a Download button) – not any CU Previews or any .NET Previews. That’s how it’s working in Version 1909, using the GUI.

Reply | Quote

[Tex265]

Can you point me to where you obtained that info as PK only addresses using the setting by selecting Semi Annual Channel and that controls Feature Update days deferral.

The settings box says: “Enable this policy to specify the level of Preview Build or Feature Updates to receive, and when.”

That seems to be either or?

PK makes this statement in the AKB

“Group Policy settings under Windows Update for Business.
I do not configure to receive C-week, D-week, and E-week (or any “Previews”) released other than the Security Updates released on Patch Tuesday (=B-week = second Tuesday).
Care must also be taken here. “Preview Builds” refer to Insider Releases which are also not configured.”

But I could figure out why or what to do with it.

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

• This reply was modified 4 years, 1 month ago by Tex265.

Reply | Quote

Tex265 wrote:

But I could figure out why or what to do with it.

Should read “But I could not figure out why or what to do with it.”

It appears in the Section 5, Method 2 narrative (second paragraph).

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

Reply | Quote

Follow the instructions for Group Policy in AKB2000016 Section 5 and see #2286499.

Reply | Quote

Per AKB and #2286499

**NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both. If you use TargetReleaseVersion, set deferrals to 0 0r 1, as they are going to be ignored anyway.

This wording is confusing.

“you should choose either …. OR”  “You should not use both”  [BUT] “If you use TargetReleaseVersion [setting] set deferrals to 0 or 1….” [in  Feature Deferrals even though I told you not to use both]   What?

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

Reply | Quote

The guide is based on experience and recommendations from knowledgeable sources.
The suggested settings work.
But there is no obligation for anyone to follow the guidance.
If you have a better method, by all means, use it.

1 user thanked author for this post.

geekdom

Reply | Quote

All I would like to know is whether or not we are supposed to use both setting at the same time.

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

Reply | Quote

Here is a direct quote from AKB2000016. Let me interpret the meaning

Using Target Release Version to stay on current version or to upgrade to a designated version.
[…]
**NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both. If you use TargetReleaseVersion, set deferrals to 0 0r 1, as they are going to be ignored anyway.

“You should choose either Feature Deferrasl OR TargetReleaseVersion settings” means the setting you use to control updates should be one or the other. Are you trying to control which version you maintain OR are you trying to prevent/change versions in a given number of days. If you want to maintain v2004, for example. you should set TRV to 2004. If you want to defer (delay) the upgrade to v2004 for 120 days, then upgrade, you should use Deferral = 120. But you should NOT USE BOTH to maintain 2004 for 120 days, because the 120-day deferral will be ignored and the TRV=2004 will prevail. You would NOT be getting the results you intended.

If you use TRV to control Feature upgrades, using deferral = 0 or 1, as suggested, is NOT using deferral as a means of controlling Feature Upgrades (because it will be ignored), so you are NOT USING BOTH.

But if you look at the settings for Feature deferral (see the second screenshot in #2275043), you may find other things involved and setting it to 0 or 1 just might be advantageous.

It might help you to understand the suggestions if you look at all the settings involved.

2 users thanked author for this post.

lmacri, abbodi86

Reply | Quote

PKCano wrote:

If you use TRV to control Feature upgrades, using deferral = 0 or 1, as suggested, is NOT using deferral as a means of controlling Feature Upgrades (because it will be ignored), so you are NOT USING BOTH. But if you look at the settings for Feature deferral (see the second screenshot in #2275043), you may find other things involved and setting it to 0 or 1 just might be advantageous.

PK, thanks and I am not trying to be difficult just questioning if what is being instructed over and over is needed. Practically the result is Windows is not functionally using both settings, but technically both are activated for no stated purpose.

You are saying don’t use both GP settings. MS is saying if you use the TVR setting,  the “Select when Preview Builds and Feature Updates are received” setting is ignored.

The second screen shot shows the “Select when Preview Builds and Feature Update are received” setting with Semi-Annual Channel selected which equates to activating the Feature Updates control for which we are told to enter 0 or 1 for the days deferred.

So technically, we have activated both the TRV setting AND the Feature Update deferral setting. In reality the Feature Update deferral setting will be ignored once the system recognizes that the TRV setting is Enabled and takes priority. Therefore after suggesting its best practive that we use the TRV setting why are we even being told to Enable the other  setting that in the end is ignored? Why not just leave it Not Configured?

“Select when Preview Builds and Feature Update are received” setting can be used for other items, but we are not being advised/shown to utilize/activate those other options, just the Feature Update deferral.

Is there something else not mentioned that enabling the Feature Update setting is doing?

 

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

Reply | Quote

I’m just trying to understand what settings to use when I move to ver 2004.

Can you pls explain the dichotomy between the 2 instructions.

Are we to use both settings, TRV and GP Feature Updates set to 0 or 1 days, or only one or the other?

Is what @WCHS says below correct?

WCHS wrote:

My understanding is that if you Enable with deferral days set to 1 or 0, you will not get any Previews on the WU screen (not even with a Download button) – not any CU Previews or any .NET Previews. That’s how it’s working in Version 1909, using the GUI.

Reply | Quote

I would recommend that you pick one or the other but not both.  Not that anything horrific will happen, just that it will be easier on you to remember which option you picked.  I prefer the targetreleaseversion method these days, but that’s just me.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Tex265

Reply | Quote

[WCHS]

Tex265 wrote:

Can you point me to where you obtained that info ..

I’m only mentioning how it works in GUI version 1909 (and TRV set). I am not on 2004 yet, but I know that it doesn’t have the GUI anymore and that you have to use GP instead. I am assuming that you can get the same 1909 GUI FU Deferral settings in 2004 by using the GP settings (since GUI is not available in 2004).

If you want me to tell you where I found info about setting FU Deferrals to 0 or 1, with TRV set, to prevent CU Previews and .NET Previews — all in version 1909, I will try to find that. But, I do know that being in 1909, I am not getting CU Previews and .NET Previews (not even with a Download button), and I believe that this is the case because with TRV=1909, I also have FU Deferrals set to 1.

Also, look at the signature of @CraigS26 on Jan 10, 2021 (I believe that he has now moved to 20H2).

• This reply was modified 4 years, 1 month ago by WCHS.

Reply | Quote

[CraigS26]

WCHS wrote:

If you want me to tell you where I found info about setting FU Deferrals to 0 or 1, with TRV set, to prevent CU Previews and .NET Previews — all in version 1909, I will try to find that. But, I do know that being in 1909, I am not getting CU Previews and .NET Previews (not even with a Download button), and I believe that this is the case because with TRV=1909, I also have FU Deferrals set to 1. Also, look at the signature of @CraigS26 on Jan 10, 2021 (I believe that he has now moved to 20H2).

I am on 20H2 (1/18) having made TRV “Not Configured” prior to Clk’ing the “Update Now” button on the 20H2 dnload page.

Feature Deferral is “1” strictly per PKC’s prior post to block Preview CU’s, TRV is now Not Configured, and Semni-Annual (I think) because I don’t fear Feature Updates (while having Images). I presume (in Bus Update) Quality Updates Enabled = 0 and “Not Configured” are the same, but I’ll leave my Signature showing QU=0.

Worth repeating that multi-posters here/elsewhere had No Issues updating to 20H2 WHILE UN-installing their Conexant Driver ( & NOT chk’ing the DELETE software Box that appears in DevMgr). The Same Conexant Driver Data is there after 20H2 loaded and me doing nothing to cause it. Others posted they “Installed” the MS Driver after the Uninstall, and I presumed (they didn’t say) they Clk’d Search for drivers and MS provided it. Were I a “basic” setup  like me I wouldn’t fear 20H2 as long as Images were made prior. Great so far.

W10 Pro 22H2 / Hm-Stdnt Ofce '16 C2R / Macrium Pd vX / GP=2 + FtrU=Semi-Annual + Feature Defer = 1 + QU = 0

• This reply was modified 4 years, 1 month ago by CraigS26.

Reply | Quote

CraigS26 wrote:

I am on 20H2 (1/18) having made TRV “Not Configured” prior to Clk’ing the “Update Now” button on the 20H2 dnload page.

What is the proper value for TRV, if you want to configure it and stay on 20H2? Is is ’20H2′, ‘2010’, ‘2011’, or what? I am guessing that Version 21H1 is coming out in April/May and so to prevent that and stay on 20H2, one would have to set the 20H2 value, whatever it is.

Reply | Quote

Group Policy Editor tells you to “Enter version as listed in the Windows Release Information page aka.ms/ReleaseInformationPage“. So, 20H2.

1 user thanked author for this post.

WCHS

Reply | Quote

CraigS26 wrote:

Feature Deferral is “1” strictly per PKC’s prior post to block Preview CU’s

Could you (or anyone) please provide the specific posting # reference to that prior PKC post for context reading purposes?  Rather strange that a GP setting targeted at “Feature update deferral” would also block “Preview CU’s”.  I can find no mention or reference to that side benefit in any of that setting’s instructions or AKB2000016, but then this is Microsoft.

If true, then there would be benefit to Enabling this setting assuming that this entire GP setting is actually not ignored (as MS says it is) when the TRV setting is Enabled.  However, I can find no documentation to an exception such as this either.

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

Reply | Quote

All the details are in AKB2000016, but the goal posts are always moving so you have to live with a lack of references and possible inconsistencies.

cheers, Paul

Reply | Quote

Tex265 wrote:

Could you (or anyone) please provide the specific posting # reference to that prior PKC post for context reading purposes?

It’s not @PKCano posts but @abbodi86 posts.

See topic Patch Lady – checking for updates,

especially #2309287, as well as above and below this post.

3 users thanked author for this post.

Perq, lmacri, Tex265

Reply | Quote

@WCHS Thank you very much for your link.  This explains why we do need to Enable and make the described setting in both GP “Select when Preview Builds and Feature Update are received” as well as GP “Select the target Feature Update version”.

And that is ,when used together, they prevent “Preview” Cumulative Updates and “Preview” .NET Updates from being displayed in the Windows Update GUI.

And though MS says the GP setting “Select when Preview Builds and Feature Update are received” is ignored when also using the GP setting “Select the target Feature Update version” to set the TRV, that is not completely true as some component of that setting is still being used to keep Preview updates from being displayed in the Windows Update GUI.

This is not documented in any published information I could find regarding the usage of those setting as they read to be targeted at controlling Feature Update deferrals not Preview Updates.

Suggest AKB 2000016 be amended to clarify that you do need to use (Enable) both GP settings if you want to prevent Preview Updates from being displayed in Windows Update GUI.

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

1 user thanked author for this post.

WCHS

Reply | Quote

Tex265 wrote:

as they read to be targeted at controlling Feature Update deferrals not Preview Updates.

As I understand it, Feature Updates and Preview Updates are, at some level, in the same category — something having to do with the fact that they are both optional updates and are thus in a special queue (can’t remember the name of it) that is different from the usual update queue and are thus handled differently from Cumulative Updates and other kinds of updates. I want to think of it this way: Feature Update is a cover term for both Version updates (i.e., from 1909 to 2004 or 2004 to 20H2) AND Cumulative Previews.

I not sure that one can include .NET Previews in this set of updates in this special queue. My understanding is that there won’t be a .NET Preview made available if the .NET update it is superseding has not been installed. Which means that if you wait until MS-DEFCON is 3+ to install a .NET update, the superceding .NET Preview has already been suppressed, and then when you DO install the .NET update, the suppressed .NET Preview is already water under the bridge (so to speak). I always wait until MS-DEFCON is 3+, so I don’t know whether this .NET rule is protecting me from .NET Previews or whether the FU=1 is. (Keep in mind that I am still on Version 1909, and so I am using the GUI.)

Some experienced person, help me out here to make it more clear (or to correct/clarify).

1 user thanked author for this post.

Tex265

Reply | Quote

[lmacri]

Hi PKCano:

I have a question regarding Win 10 Pro v2004 and Preview Updates (i.e, week C/D non-security cumulative updates).

I just upgraded from 64-bit Win 10 Pro v1909 to v2004 on 20-Jan-2021 by setting TargetReleaseVersion to “2004” (i.e., I set Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update Version to “2004” with GPEdit and then changed Settings | Update & Security | Windows Update | Advanced Options | Choose When Updates Are Installed | Feature Updates in the v1909 Windows Update advanced settings from 365 to 0). Yesterday I noticed that Windows Update shows the optional quality update 2021-01 Cumulative Update Preview for Windows 10 Version 2004 for x64-based Systems (KB4598291, OS build 19041.789, rel 02-Feb-2021) is waiting for download as shown in the attached screenshot.

I don’t want to upgrade to v20H2 yet, so what is the best way to prevent Windows Update from offering these Preview Updates? After reading abbodi86’s post # 2283011 in Windows Update’s Bifurcated Mess I’m a bit confused about whether I can:

a) Simply enable Defer Preview Updates in GPEdit (Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Defer Preview Updates) and leave TargetReleaseVersion set at “2004” or if I must
b) Enable Select When Preview Builds and Feature Updates are Received in GPEdit (Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates are Received – choosing Semi Annual Channel and deferring Feature Updates for 365 days) as you suggested in Section 5 / post # 2275043) and then disable TargetReleaseVersion.
————-
64-bit Win 10 Pro v2004 build 19041.746

• This reply was modified 4 years, 1 month ago by lmacri.
• This reply was modified 4 years, 1 month ago by lmacri.

Reply | Quote

There are three settings you need as described here (ignore the part about the pulldown switches in 1909).
Let me know if that works for you.

1 user thanked author for this post.

Dan Montague

Reply | Quote

Could someone explain the purpose of the GPEdit setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Manage Preview Builds. If I enable that setting and then choose “Disable Preview Builds” as shown in the attached screenshot, does that simply prevent me from accidentally enrolling in the Windows Insider Program at Settings | Update & Security | Windows Insider?  The description for “Disable Preview Build” is “Selecting “Disable preview builds” will prevent preview builds from installing on the device. This will prevent users from opting into the Windows Insider Program, through Settings -> Update and Security.”

According to the information at https://insider.windows.com/en-us/, Build 19042.789 is now available in the Beta Channel and Release Preview Channel for the Windows Insider Program. I still have TargetReleaseVersion set to “2004” (Build 19041.x) and not “20H2” (Build 19042.x) but if I had chosen to “Disable Preview Builds” at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Manage Preview Builds wouldn’t that also have prevented Windows Update from offering the optional quality update 2021-01 Cumulative Update Preview for Windows 10 Version 2004 for x64-based Systems (KB4598291, OS build 19041.789 and 19042.789, rel 02-Feb-2021) I showed in my post # 2341100? If I can use this “Disable Preview Builds” setting to permanently prevent optional week C/D non-security updates from being offered that would make life much easier, because when I am finally ready to install version 20H2 I could simply change TargetReleaseVersion to “20H2” and I wouldn’t have to worry about resetting the number of deferred days from 365 back to 0 or 1 for “Select When Preview Builds and Feature Updates are Received”.

Or am I completely confused about this, and is using the setting at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (Semi-Annual Channel, defer for xxx days) the only way to prevent these optional week C/D non-security updates from being delivered to my v2004 / Build 19041.x OS?
————-
64-bit Win 10 Pro v2004 build 19041.746

Reply | Quote

It is my interpretation the “Disable Preview Builds” refers to Insider Builds, as it references “flights” and “Insider Builds” (Insider terminology) and points to Settings-> Update & Security ->Windows Insider Program.

1 user thanked author for this post.

b

Reply | Quote

Remember the intent for these Windows update for business settings is to let enterprises “test out” these Insider editions.  So these settings are for IT admins to control testing rings.  Preview updates are (in theory) not SUPPOSED to install via the Windows update channel.

February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789) Preview (microsoft.com)

“Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update”

It’s not supposed to push out.  When they do, Microsoft has screwed up a setting on their side.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

lmacri

Reply | Quote

@Susan Bradley & @PKCano Thank you for all that you do for this community.

The following is not a question on AKB 2000016, rather it is a report of an apparently successful use of your mighty good works.

Before attempting the windows update, I read Susan Bradley’s article “Tasks for the Weekend – January 30, 2021” and PKCano’s article “AKB2000016: Guide for Windows Update Settings for Windows 10” and I read the comments (posted separately from the article) and PKCano’s responses.

I was on Windows 10 version 1909 and decided to accept updates to 2004 and nothing later. Per PKCano’s advice, I made a full disk image, a separate backup for data, and made a rescue disk (tested to make sure it was bootable).

Upon starting the update, I was a little surprised to find the Group Policy Editor item “target Feature Update version” was available to me on version 1909 (From reading “Tasks for Weekend” I thought that it did not become available until version 2004; I decided this was probably an error in my understanding and chose to press on). I set the target Feature Update version to 2004, made sure no other settings were configured. Also made sure the Group Policy Editor Windows Update settings = 2 (Notify for download and auto install), enabled install other MS products, and no other settings. Before updating, I checked Windows Update Advanced Options and observed they were as usual (in this case, “Pause until February 12, 2021,” also feature update defer 365 days, and quality update defer 30 days). I left them alone.

I pressed “Resume Updates” and set metered connection off (wrong sequence, but seemed to work out). I left it to run unattended but checked in from time to time. About 9 hours later it needed reboot and an additional 2 hours after that it had finished all its various reboots, etc. I double checked to make sure Group Policy Editor settings were as before (they were unchanged). Also double checked Windows Update Advanced Options and observed that Pause Updates now had no date specified, and the deferral & defer dates mentioned above were not present.

About 4 hours later I noticed that Windows Update needed some attention: Updates available:

Windows Malicious Software Removal Tool x64 – v5.85 (KB890830)

2020-11 Update for Windows 10 Version 2004 for x64-based Systems (KB4023057)

2020-10 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 2004 for x64 (KB4578968)

2020-10 Security Update for Adobe Flash Player for Windows 10 Version 2004 for x64-based Systems (KB4580325)

[All of the above are Status: Pending download]

Updates are ready to download

These 4 updates above seem to be several months old, they don’t have the word “Preview,” and seem innocuous. I am considering downloading the above 4. If anyone knows something different, please respond.

BUT there is another: 2021-01 Cumulative Update Preview for Windows 10 Version 2004 for x64-based Systems (KB4598291). This is recent and has the word “Preview” in it. So, I intend to ignore it for at least another month. Subsequently I read Imacri’s query of February 5, 2021 to PKCano, and also read PK’s response https://www.askwoody.com/forums/topic/comments-on-akb-2000016-guide-for-windows-update-settings-for-windows-10/#post-2341104. I admit this latest query/response has me puzzled, but I’m going to wait a while.

My impression is this Windows Update experience went very smoothly for me. Thanks again for all your good works.

Dan Montague

Reply | Quote

I personally haven’t had issues with KB4023057: Update for Windows 10 Update Service components (microsoft.com) , and the .NET and Flash are the most recent security updates for those components.  I don’t have a problem with those.  Malicious software removal is optional.

The preview update is indeed a preview and will be included in next week’s normal patch.  Skip over that one.

And thank you for the report!!  It’s always wonderful to hear survivor stories 🙂

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

There are some changes you should make to your Group Policy settings.

There are three important settings, two of which you already have:
+ In GP under Windows Update – the “2” (notify download/install)
+ In GP under Windows Update for Business – TargetReleaseVersion set to the version you want to maintain.
+ Under Windows Update for Business, set Select when Preview Builds and Feature Updates are received as shown in the second screenshot in #2275043 ****but use the setting of 0 or 1 instead of 365.
The last setting will help prevent WU offering you Previews.

Also, you should NOT use Pause if you use this method. The “2” setting will prevent updates from downloading and installing until you click the “Download” button.

Please read AKB2000016 Section 5 for information on the settings for 2004 and later.
You also may find AKB2000013 on clearing the Windows Update queue interesting. Beside the method in the main post, read @matador ‘s method from #2286979 down. This method works as well.

1 user thanked author for this post.

Perq

Reply | Quote

See my post #2337911 for more details on preventing Preview Builds.

Tex265 wrote:

Suggest AKB 2000016 be amended to clarify that you do need to use (Enable) both GP settings if you want to prevent Preview Updates from being displayed in Windows Update GUI.

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

1 user thanked author for this post.

lmacri

Reply | Quote

AKB2000016 has stated/already states, in multiple places, that if you use TRV you should also set deferrals to 0 or 1. In fact, it is stated in bold.

However, I have NOT found, in MS documentation (as yet), the other information. The suggestion that it has other effects is based on some testing by @abbodi86 ( #2309326 ) and my own experience.
So, until I can link MS documentation to substantiate, AKB2000016 will remain as it is.

Reply | Quote

Susan Bradley wrote:

…Preview updates are (in theory) not SUPPOSED to install via the Windows update channel. February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789) …It’s not supposed to push out. When they do, Microsoft has screwed up a setting on their side.

Hi Susan Bradley:

That sounds like the Windows Update glitch being discussed in your topic Barb Bowman Reports Preview NET Kicks Reboot regarding KB4598299 (rel. 02-Feb-2021) is the same reason I was offered the optional quality update 2021-01 Cumulative Update Preview for Windows 10 Version 2004 for x64-based Systems (KB4598291, OS build 19041.789, rel 02-Feb-2021) shown in my screenshot in post # 2341100.

I was unable to find any detailed online documentation on the “Disable Preview Builds” setting in GPEdit at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Manage Preview Builds, but I noticed this unexpected message at Settings | Update & | Windows Insider Program that starts with “To manage the Windows Insider Programs settings for your device and allow it to stay in the Windows Insiders program, you’ll need to turn on optional diagnostic data…” that seems to suggest that I’ve inadvertently opted in to one of the Windows Insider Program rings.

I just upgraded from Win 10 Pro v1909 to v2004 on 20-Jan-2021 by changing my Target Release Version (Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update Version) to “2004” and changing my v1909 Feature Update deferral in Windows Update from 365 to 0. I have Settings | Privacy | Diagnostics & Feedback | Diagnostic Data set to “Required Diagnostic Data” instead of the default “Optional Diagnostic Data”, and I wonder if Windows Update incorrectly assumes I want Windows Insider preview builds when Target Release Version is set to “2004 and my Privacy setting is set to send required diagnostic data only. Perhaps that also explains why it’s important for some users to explicitly set the release channel at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received (Semi-Annual Channel, defer for xxx days) so that Windows Update doesn’t incorrectly offer Windows Insider Program preview builds when TargetReleaseVersion is enabled – especially for users like me who are are only sending required diagnostic data to Microsoft.
————-
64-bit Win 10 Pro v2004 build 19041.746

Reply | Quote

Semi-Annual Channel and Semi-Annual Channel (Targeted) pertained to CU and CU Previews, where the SAC only received the security CUs released on Patch Tues, and the SACT received the non-security CU Previews released other than on Patch Tues.
SAC and SACT did not, to my knowledge,  pertain to Preview Builds, which, are previews of Feature Updates and have been part of the Insider Program.
MS has done away with the SAC and SACT designations, but the SAC designated in the Windows Update for Business deferral settings still SEEMS to keep away the CU Previews, although I have found no documentation that specifically substantiates this.

 

2 users thanked author for this post.

Perq, lmacri

Reply | Quote

Hi PKCano:

Then I’m still a bit confused about your instructions in in AKB 2000016: Guide for Windows Update Settings for Windows 10. Could you confirm that this what you’re suggesting for Win 10 Pro v2004 users who want to defer a version upgrade to v20H2 using GPEdit:

a) If you only want to prevent the upgrade to 20H2, change Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update Version to “2004”. If this is the only Business setting changed in GPEdit you will be offered week C/D preview updates in v2004 by Windows Update [i.e., as if your release channel is Semi-Annual Channel (Targeted)]. When you are ready to upgrade to v20H2 change your TargetReleaseVersion from “2004” to “20H2”.

b) If you want to prevent the upgrade to 20H2 AND prevent Windows Update from offering week C/D preview updates in v2004, change Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update Version to “2004” AND  enable Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates are Received, choose Semi-Annual Channel and defer Preview Builds and Feature Updates for 0 days (not 365 days). [i.e., as if your release channel is Semi-Annual Channel]. When you are ready to upgrade to v20H2 just change your TargetReleaseVersion from “2004” to “20H2”. (NOTE: This might be the best option for me but this is where I get confused.  If you defer Preview Builds for 0 days instead of 365 days, does choosing a release channel of “Semi-Annual Channel” prevent the delivery of optional Preview Builds, just as setting TargetReleaseVersion to “2004” overrides the number of days that Feature Updates are deferred?).

c) If you want to prevent the upgrade to 20H2 and prevent Windows Update from offering week C/D preview updates in v2004, an alternate method is to leave Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select the Target Feature Update Version as “Not Configured” (or “Disabled”). ONLY enable Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates are Received, choose Semi-Annual Channel and defer Preview and Feature Updates for 365 days (not 0 days) as you suggested in post # 2275043. When you are ready to upgrade to v20H2 (and not beyond v20H2) set your TargetReleaseVersion from “2004” to “20H2” AND temporarily change the deferral of Preview and Feature Updates from 365 to 0 days until v20H2 is delivered. Once v20H2 is delivered change TargetReleaseVersion back to “Not Configured” or “Disabled” and change the deferral of Preview Builds and Feature Updates back to 365 days to stay on v20H2.

———————————-

Like Tex265, I find the comment in post # 2286499 of AKB 2000016 (“Using Target Release Version to Stay on Current Version or to Upgrade to a Designated Version”) that “**NOTE: When delaying version updates, you should choose either Feature Deferrals OR TargetReleaseVersion settings. You should not use both to achieve update control. If you use TargetReleaseVersion, you should also set deferrals to 0 0r 1 as shown in the second screenshot in #2275043. They are going to be ignored anyway” to be somewhat confusing, because you seem to be telling me I should use BOTH settings as described above in Option B to stop Windows Update from offering week C/D preview updates if I have TargetReleaseVersion set to “2004”.
————-
64-bit Win 10 Pro v2004 build 19041.746

Reply | Quote

[Tex265]

lmacri wrote:

to be somewhat confusing, because you seem to be telling me I should use BOTH settings as described above in Option B to stop Windows Update from offering week C/D preview updates if I have TargetReleaseVersion set to “2004”.

Tex265 wrote:

This explains why we do need to Enable and make the described setting in both GP “Select when Preview Builds and Feature Update are received” as well as GP “Select the target Feature Update version”. And that is ,when used together, they prevent “Preview” Cumulative Updates ….. from being displayed in the Windows Update GUI. And though MS says the GP setting “Select when Preview Builds and Feature Update are received” is ignored when also using the GP setting “Select the target Feature Update version” to set the TRV, that is not completely true as some component of that setting is still being used to keep Preview updates from being displayed in the Windows Update GUI.

Note: my above comments are the result of various members’ feedback confirming those results.

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

• This reply was modified 4 years ago by Tex265.

Reply | Quote

I have a new home PC with Win10 Pro x64 2004 installed. I have not yet connected it to the Internet. I am new to Win10, but I am a very experienced user of previous versions of Windows.

So far, I have been spending time customising the system, but I have now reached the stage where I am planning to connect it to the Internet. However, I don’t want any surprises when I do connect it. In particular, I don’t want updates or upgrades to occur without my knowledge. I have therefore been trying to follow the advice in AKB2000016. I have read the document a number of times, but I am still confused with some parts of it and there appears to be a lot of duplication of the information.

As far as I can gather, in order to achieve my objective, I need to configure only the following in the Local Group Policy Editor and leave everything else not configured:

• In the Windows Update folder, Configure Automatic Updates is “Enabled” with a value of “2” (Notify for download and auto install).
• In the Windows Update for Business folder, Select the target Feature Update version is “Enabled” and set to “2004”.

In the Windows Update folder, I have also set Do not include drivers with Windows Updates to “Enabled”. And I have wushowhide.diagcab ready to use if and when necessary.

Have I missed, forgotten or misunderstood anything?

Just in case anyone thinks that I should be warned, I am aware that Defender will not get regular virus definition updates with these settings, but I know what to do in order to keep Defender up to date. (I do think that AKB2000016 ought to have an explicit “health warning” in this respect.)

Reply | Quote

Have I missed, forgotten or misunderstood anything?

Not really, but to help avoid being offered any previews by Windows Update, in Group Policy in the Windows Update for Business folder, please set the following up in the “Select when Preview Builds and Feature Updates are received” entry:

Click the Enable button and once you’ve done that, in the “Options part of that entry’s window, select “Semi-Annual Channel in the drop down menu, and set the number of days’ deferral to at least 1 in the box right underneath the one for Semi-Annual Channel.

Now just click OK and you’re all set…you won’t be offered any previews that you shouldn’t be installing.

As far as Windows Defender not receiving updates with the three settings you mentioned above, that’s false. With those settings, Defender on my installations of 2004 always got updates that it needed, and it holds true on 20H2 as well for me (I’ve since updated my 2004 installations to 20H2).

I hope this helps a bit.

Reply | Quote

One bit of clarification to avoid confusion from reading my post right above: The box under the one for Semi-Annual Channel that I’m talking about is the one that says “After a Feature Update or Preview Build is released defer for this many days:” and has little up and down arrows on the right side of the box. Make sure that box has a value of 1 in it

The box below that, which calls for entering a specific date, should be left blank.

Sorry for any confusion I may have created or inadvertently added to.

Reply | Quote

There are screenshots below the instructions that show the settings. Scroll down and find the ones you need.

Reply | Quote

@TonyC:
There’s a discussion of this GP setting to prevent CU previews at #2309328. Also, above and below that post.

Reply | Quote

anonymous wrote:

Not really, but to help avoid being offered any previews by Windows Update, in Group Policy in the Windows Update for Business folder, please set the following up in the “Select when Preview Builds and Feature Updates are received” entry:

I’m on a learning curve here, so please bear with me.  My understanding is as follows.

If I set Select when Preview Builds and Feature Updates are received to “Enabled” with the “Semi-Annual Channel” option, it is not going to have any effect if my TRV is set to 2004 and I am already on 2004.  I’m not going to be offered any other feature update.

It would have an effect only if I set my TRV to a later feature update level which had not yet achieved semi-channel readiness.  But then, I’m probably not going to do that.  In the future, I would probably want to set my TRV only to a feature update level that had already achieved semi-channel readiness.

Is my understanding correct?  Am I missing any subtlety?

Reply | Quote

Some versions ago, MS had a way to limit “important” Security CUs vs. “optional” non-Security Preview CUs.
Semi-Annual Channel (SAC) made available CU rated “ready for business,” the Security updates released on Patch Tuesday.
Semi-Annual Channel Targeted (SACT) made available both the Security updates released on Patch Tuesday and the “optional” non-Security Preview CUs released on C, D, and E weeks.

Both those designations have gone by the wayside with MS’s many and frequent changes in terminology and methodology.
But it would seem that setting “Semi-Annual Channel” and the deferral to 0 or 1 (instead of 365) prevents the Preview CUs from appearing in Windows Update so that only the Patch Tuesday Security CUs are available. (See the second screenshot in #2275043) With TRV set to the desired version to keep or upgrade to, the documentation says the deferral will be ignored. I have not found documentation on the Semi-Annual Channel setting – the reason I used “it would seem” above.

See AKB2000016 for more information on Windows Update Settings.

3 users thanked author for this post.

Perq, TonyC, WCHS

Reply | Quote

Ah, I was missing a subtlety!  Thank you.  As a newcomer to Win10, it all seems a little perverse and confusing.

To me, a Preview CU and a Preview Build are two entirely different objects.  And it never crossed my mind that the option you specify in the Select when Preview Builds and Feature Updates are received folder might have an effect on whether you receive Preview CUs or not.

It would appear from what you have stated that this subtlety has been discovered solely by user experience.

Reply | Quote

TonyC wrote:

It would appear from what you have stated that this subtlety has been discovered solely by user experience.

Here’s the “user experience”: abbodi86 – 2309326

Reply | Quote

Given the recent comments in this thread about Windows Defender definition updates, does that mean that DU stands for Defender / Definition Update and CU stands for Cumulative Update (the non-Security Cumulative Updates or “Preview” updates usually released in weeks C/D) in abbodi86’s post # 2309326, because I’m still not certain what the abbreviations UUP, CU and DU mean. I’m assuming WUA = Windows Update Agent, FU = Feature Update, QU = Quality Update (the monthly Security Cumulative Update and other updates released on Patch Tuesday / week B). Abbodi86’s post would be much clearer if there was a footnote explaining what the abbreviations mean for those of us who aren’t immersed in the lingo surrounding Windows Updates.
————-
64-bit Win 10 Pro v2004 build 19041.804 * Windows Defender v4.18.2101.9

1 user thanked author for this post.

TonyC

Reply | Quote

Thank you for raising this issue.  I was also puzzled by some of these acronyms.

The acronym QU was new to me, but I assumed that it refers to Quality Update, the monthly security cumulative update. The problem I had then was what does CU refer to in this context? I had always considered CU to be an abbreviation for any cumulative update, which would mean that QU is a specific type of CU. But I don’t think this is the case in this context.

Reply | Quote

You are correct with your presumptions of what QU (Quality Update) and CU (Cumulative Update) mean.

They have been used interchangeably to mean the same thing: The monthly update that fixes (or at least is supposed to fix) issues of misbehaving software and that also patches security holes that have been found.

One reason the QU and CU terms have been used interchangeably is that the monthly Quality Updates are, indeed, Cumulative. So this month’s update contains all the fixes of the previous ones plus new fixes for this month.

BTW, FU means Feature Update, and that’s the update that pushes you from one version of Windows 10 to the next, such as 2004 to 20H2 or 20H2 to 21H1.

Reply | Quote

anonymous wrote:

You are correct with your presumptions of what QU (Quality Update) and CU (Cumulative Update) mean. They have been used interchangeably to mean the same thing: The monthly update that fixes (or at least is supposed to fix) issues of misbehaving software and that also patches security holes that have been found.

One problem is that AKB2000016 defines “Quality Update” to be:

… the monthly Security Cumulative Update and other updates released by Microsoft on the second Tuesday of the month (Patch Tuesday).

This means that QU could refer to other updates released on Patch Tuesday and these updates might not be cumulative.

And then the other problem is that abbodi86 in #2348362 defines CU to mean:

Latest Cumulative Update (whether Security or Preview)

This implies that a CU might be a QU, if it is a security cumulative update, or it might not be a QU, if it is a preview cumulative update.

1 user thanked author for this post.

lmacri

Reply | Quote

WUA = Windows Update Agent
UUP = Unified Update Platform (the underneath Windows Update federated search service)
USO = Update Service Orchestrator
DU = Dynamic Update (used during complete OS upgrades)
CU = LCU = Latest Cumlative Update (whether Security or Preview)
SSU = Servicing Stack Update
FU = Feature Update
QU = Quality Update

6 users thanked author for this post.

Perq, TonyC, WCHS, hms, PKCano, Bob99

Reply | Quote

Perhaps a key to all the acronyms should be incorporated into AKB2000016?

Reply | Quote

PKCano wrote:

But it would seem that setting “Semi-Annual Channel” and the deferral to 0 or 1 (instead of 365) prevents the Preview CUs from appearing in Windows Update so that only the Patch Tuesday Security CUs are available.

I’m a little confused because anonymous in #2347948 seemed insistent that the deferral in this context should be set to at least 1. Does it really matter whether it is 0 or 1? Unless there is a good technical reason, I would prefer to use 0 simply because it is a nice round number (sorry for the pun!).

Reply | Quote

anonymous wrote:

As far as Windows Defender not receiving updates with the three settings you mentioned above, that’s false. With those settings, Defender on my installations of 2004 always got updates that it needed, and it holds true on 20H2 as well for me (I’ve since updated my 2004 installations to 20H2).

There is plenty of information on the Internet that differs from what you state.

On Win7, MSE receives virus definition updates independently of how Windows Update is configured.  On my Win7 system, I have always had automatic updates for Windows Update disabled (= Never check for updates (not recommended)), but MSE has always automatically received virus definition updates regularly as a background task.

My understanding from what I have read on the Internet is that how and when Defender on Win10 receives its virus definition updates depends on how Windows Update is configured.  If Configure Automatic Updates is “Enabled” with a value of “2” (Notify for download and auto install), as it is on my Win10 Pro system, Defender will not automatically receive regular virus definition updates as a background task.

This is not really the right topic/thread to discuss this issue but, if anyone can confirm which is correct, I would be grateful.

Reply | Quote

TonyC wrote:

If Configure Automatic Updates is “Enabled” with a value of “2” (Notify for download and auto install), as it is on my Win10 Pro system, Defender will not automatically receive regular virus definition updates as a background task.

This is what the WU screen looks like, if GP=2:

1 user thanked author for this post.

TonyC

Reply | Quote

Thank you.  Your attachment shows what I expect to happen.

However, can you confirm what Tex265 reports in #2348160 that, even though automatic updates is set to “2” (Notify), virus definition updates will ultimately be received by Defender automatically?

Do you have any opinion on how long it takes for virus definition updates to be automatically received by Defender after they appear in the Windows Update window?  If it is a matter of minutes or a few hours, it is not a problem.  If it is a matter of days or weeks, it is a problem.  I don’t want to have to look in Windows Update every time I logon.  Once a month to do the monthly updates is enough for me.

BTW, some of the abbreviations in this area are beginning to confuse me.  I think I know what GP=2 is referring to.  But what do the letters GP actually stand for?

Reply | Quote

[Bob99]

GP stands for Group Policy. You can use GP to edit the behavior of Windows Defender in terms of automatically updating itself, so that it automatically updates itself after each time the computer starts and the Windows Defender service starts.

However, I haven’t seen an entry that would dictate that Windows Defender should check for updates, say, every 2 or 4 hours. If that type of setting exists, I’d be very interested in seeing it and just maybe tweaking it a bit.

@TonyC -If you’re confident in looking into the group policy editor, I can tell you just where the entry lies that will allow your copy of Windows Defender to automatically update itself every time the computer and its service restart.

Because I realize that the topic of automatic updates to Windows Defender is off-topic for this thread, it may be a good idea to put your reply in the form of starting a new thread with the subject of Windows Defender automatic updates, or something similar.

• This reply was modified 4 years ago by Bob99. Reason: edited reply instructions

1 user thanked author for this post.

TonyC

Reply | Quote

Yes, I guessed that was what GP stood for.  But in the context of “GP=2” (that is, Configure Automatic Updates in the group policy editor set to “Enabled” with the value “2” (Notify)), it is far too cryptic in my opinion.

I will take your advice and raise the topic of automatic updates to Defender in the Windows 10 forum.

Reply | Quote

[Tex265]

anonymous is correct. You will automatically receive Defender updates as they are released via Windows Updater and be “held” in the Windows Updater window for a short period of time due to your GP 2 setting – Notify.  If you do not select the Download button rather quickly from the Defender’s update appearance in Windows Updater (minutes to sometime hours), the Defender updates (and only the Defender Updates) will automatically install so as to keep your system safe.

(Screenshot from WCHS is what you will see)

Be careful if the Defender update appears in the Windows Updater along with other regular type updates as selecting Download may download and install everything. In this case just ignore it and it will install itself eventually.

This is the way it has been working on my system since ver 1803.

TonyC wrote:

To me, a Preview CU and a Preview Build are two entirely different objects. And it never crossed my mind that the option you specify in the Select when Preview Builds and Feature Updates are received folder might have an effect on whether you receive Preview CUs or not. It would appear from what you have stated that this subtlety has been discovered solely by user experience.

See #2342854 above for more discussion on this abnormality.

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

• This reply was modified 4 years ago by Tex265.
• This reply was modified 4 years ago by Tex265.
• This reply was modified 4 years ago by Tex265.

2 users thanked author for this post.

Perq, WCHS

Reply | Quote

Is this site working properly?

I just spent 10 minutes creating a post to help TonyC  member out only to find it missing!

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

Reply | Quote

It had been automatically marked as spam due to several quick edits, but I’ve restored it now.

1 user thanked author for this post.

Tex265

Reply | Quote

hello, i just recently using win 10 pro 20H2 and have question about this
my last update is on 2nd May 2021 and after the update only optional update left which is the cumulative preview( i dont install this), after that i pause my windows update until 31th May

my question is : what will happen after the pause over if i do the setting here to my pc? will it still download the may security update right away or not?

i plan to do this setting on my group policy

Under Windows Update:
Set Configure Automatic Updates to Enabled ( its disabled for now, is this the default?)
Set Configure automatic updating to “2” (Notify for download and auto install)

Under Windows Update for Business:
Set Select the target Feature Update version to Enabled.
Set Target Version for Feature Update to 20H2

is it okay to leave Select when Preview Builds and Feature Updates are received not configured?
is there any setting that im missing?

Reply | Quote

Pause is a risky venture. If you end Pause by clicking “Resume Updates,” the system will initiate an immediate download/install, ignoring your other settings.
If you have the “2” set, and the Pause runs out, the updates MAY hang in the WU queue (and maybe not) until you click the “Download” button (NOT “Check for updates”).
This is the reason I never use Pause when Group Policy settings are available.

TargetReleaseVersion (TRV) will hold you on the version you are on, or move you to later versions, through WU, depending on the version you choose.

+ “Select when Preview Builds and Feature Updates are received” should be Enabled. Selecting Semi Annual Channel – allows deferring Feature Updates up to 365 days. I do not use any Pause settings here.
+ “Select when Quality Updates are received” if Enabled, I recommend using a deferral = o(zero)

These two settings, Enabled and set to 0 (zero) will keep you from getting Preview Builds. Notice the setting for Semi Annual Channel.

There are screenshots under the text. Be sure to read the instructions associated with those last two settings.

1 user thanked author for this post.

heybengbeng

Reply | Quote

im kinda new to this so sorry if im asking too much

the updates MAY hang in the WU queue (and maybe not) until you click the “Download” button (NOT “Check for updates”)

so what this means is if the updates hang on WU queue then i can just click download whenever i want to update( group policy working as intended)

if not then it will be auto downloaded, but the next month update will work as intended by group policy setting( by clicking download)

 

so about setting up group policy, im already on 20H2 now and want to stay like that for a while, so is this setting correct?

Under Windows Update:
Configure Automatic Updates to Enabled
Configure automatic updating to “2” (Notify for download and auto install)

Under Windows Update for Business:

“Select when Preview Builds and Feature Updates are received” = Enabled.

Selecting Semi Annual Channel – deferring Feature Updates to 1 days

“Select when Quality Updates are received” = Enabled, and deferral = 1 days( from what i read can also leave this whole setting not configured)

Under Windows Update for Business:
Select the target Feature Update version to Enabled.
Target Version for Feature Update to 20H2

(for Select when Preview Builds and Feature Updates are received”, i leave the Pause preview or features update starting” date empty since its empty on the screenshot)

if this setting is already correct, and later in the future i want to move to 21H1, i only need to change the TRV number to 21H1 right? or do i need to change the other settings too after i updated to 21H1?

Reply | Quote

The “2” setting will cause the updates to wait in the queue until you click the “Download” button – that is correct. Read about wushowhide.diagcab also (download link in AKB2000016). If there are updates you don’t want, you can HIDE them so they don’t install, but they must be cleared from the queue before you download.

“Select when Preview Builds and Feature Updates are received” = Enabled.

Selecting Semi Annual Channel – deferring Feature Updates to 1 days

“Select when Quality Updates are received” = Enabled, and deferral = 1 days( from what i read can also leave this whole setting not configured)

Using these Enabled keeps you from getting Previews. They are deferrals. Set them to 0 or 1. Setting them to 0 will result in the updates showing up in the queue on Patch Tuesday when they are released. If you set them to 1, the updates won’t show up until the next day (deferred 1 day).

When you want to change versions, the only thing you need to change is the TRV. The other settings remain the same.

FYI So you don’t get surprised. What you see in the WU queue is what will install. If you HIDE updates with wushowhide, you need to clear them from the queue before downloading. AKB2000013 deals with this. Also read @Matador ‘s method further down the thread. When WU does its scheduled daily check for updates, the hidden ones will also be cleared.

1 user thanked author for this post.

heybengbeng

Reply | Quote

@PKCano, thanks for your post of today May 26, 2021.

I mistakenly Paused until a specific calendar date. I had forgotten that I was on Windows 10 Pro with group policy edit settings as you recommended. So, now that I’ve already Paused, is the following a safe way to dig myself out of the hole?

1. Wait until MS-DEFCON 4 is announced,
2. Run wushowhide twice (first to hide unwanted updates, then second time to UNhide those updates that are wanted).
3. Set metered connection OFF .
4. [Here’s the part I’m most concerned about:] end Pause by clicking “Resume Updates”

Thanks again for your patience and your help.

Reply | Quote

Windows Update and wushowhide both use the Windows Update Service.
When you use Pause, WU can’t see any pending updates as long as Pause is in place – and neither can wushowhide.

If you have the GP setting “2” in place, disconnect from the Internet, turn off the Pause, click on “check for updates.” It should fail since you are not connected, probably to “Retry.”
Click on “Retry” and as soon as it starts checking for updates on its own, reconnect to the Internet. Hopefully the “2” setting will hold the updates in the queue. If not, Susan is probably going to set DEFCON to 4 this coming weekend, so you should be OK to go ahead with the updates.

Don’t use Pause. The “2” setting will hold the updates till whatever date you choose. 🙂

1 user thanked author for this post.

Dan Montague

Reply | Quote

When you have two “products” with the same version, you have to extend the distinguishment

currently in Windows 11 policies, and coming soon to Windows 10

registry equivalent:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]  
"ProductVersion"="Windows 11"

3 users thanked author for this post.

PKCano, Microfix, lmacri

Reply | Quote

After looking over your AKB2000016 Topic, I think Method 2 in June 24th 2020 seems easier to follow.

After I install Win 10 Pro offline, do you agree Method 2 is a good choice for my low level of tech skills ?
Looking for Method that has least amount of time of upkeep/I can set and forget. A Method that’ll update my PC when it’s safe (to help when busy)

 

Trying to install to Win 10 Pro and get September updates to defer Oct. update. on Tuesday.

Update on to do list before moving to Win10: I just need to create full image backup

Reply | Quote

Just a warning, later on tonight you’ll see the site go to DefCon 2.  I do this in advance of the second Tuesday just to give people time to change/push off updates.  You still have the weekend to do what you need to on your computer.  Take a backup first.

Susan Bradley Patch Lady/Prudent patcher

1 user thanked author for this post.

Alex5723

Reply | Quote

Hi PKCano:

According to EP’s 16-Nov-2021 post in 21H2 is Finally Out, the frequency of Feature updates in both Win 10 and Win 11 will change from a semi-annual to an annual cadence after v21H2 is installed, and the Windows Experience blog How to Get the Windows 10 November 2021 Update states that Microsoft is “renaming the servicing option for releases to the General Availability Channel starting with the November 2021 Update (Note: this replaces the previous “Semi-Annual Channel” term for the servicing option).”

Do you know if Win 10 Pro users who update to v21H2 (a.k.a. the Windows 10 November 2021 Update) will no longer see “Semi-Annual Channel” as an option in their Local Group Policy Editor at Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Updates Are Received if they are currently using this setting to prevent delivery of Week C/D Preview Builds?  Also, will the “Semi-Annual Channel” option automatically change to “General Availability Channel” after v21H2 is installed if a Win 10 Pro user has enabled this gpedit setting, or will this option have to be re-configured manually?

———–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H1 build 19043.1348 * Firefox v94.0.1 * Microsoft Defender v.4.18.2110.6-1.1.18700.4 * Malwarebytes Premium v4.4.10.144-1.0.1499

Reply | Quote

Win10 v21H1 Build 19043.1348 still says Semi-Annual Channel under WUfB.

I have just upgraded it to v21H2 Build 19044.1348 using the TRV setting. Group Policy still shows Semi-Annual Channel under WUfBSelect when Preview Builds and Feature Updates are received.  General Availability Channel has not been added to the list. So no change yet with the Nov upgrade.

1 user thanked author for this post.

lmacri

Reply | Quote

FWIW – I don’t find either “Channel” setting in my Win11 on ARM Insider VM. Only the TRV/Product Version settings.

Reply | Quote

Hi PKCano:

Further to my post # 2402131 of 17-Nov-2022 regarding the “Select When Preview Builds and Feature Are Received” setting:

I currently have a Win 10 Pro v21H2 (Nov 2022 OS Build 19044.2251). With previous OS builds I was able to prevent delivery of Week C/D Preview builds using my Local Group Policy Editor (gpedit.msc) as shown in the second image of  post # 2275043 of your 2000016: Guide for Windows Update Settings for Windows 10 (i.e., Computer Configuration | Administrative Templates | Windows Components| Windows Update | Windows Update for Business | Select When Preview Builds and Feature Are Received was enabled and set to Semi-Annual Channel). However, I checked that setting today and I no longer see a dropdown box where I can select Semi-Annual Channel.

Here is a an old screenshot I captured in January 2022 with Win 10 Pro v21H2 …

… and this is what I see now ( still Win 10 Pro v21H2).

I assume the option to select Semi-Annual Channel is gone because Win 10 has moved to a once-a-year cadence for release of new Feature updates, but what are the correct settings now for preventing delivery of Week C/D Preview builds by Windows Update? For example, is it sufficient to simply enable this setting and enter any value for the number of days (from 1 to 365) for deferral?

Note that I also have my Target Release Version (Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select the Target Feature Update Version) currently set to Windows 10 / 21H2, which I understand will override the number of days of deferral I choose for my Feature Update and will prevent delivery of the v22H2 Feature update until I change my Target Release Version.

The reason I checked this “Select When Preview Builds and Feature Are Received” setting today is because I received updates for KB5020930 (2022-11 .NET Core 3.1.31) and KB5020743 (2022-11 .NET 6.0.11) when my Nov 2022 Patch Tuesday updates were installed, even though those MS .NET (Core) Runtime updates don’t include a security update. In the past my MS .NET Framework updates were not delivered unless they included a security patch (an odd side-effect of blocking Week C/D Preview builds in gpedit), but I don’t know if blocking Week C/D Preview builds should also prevent delivery of MS .NET (Core) Runtime update that don’t include a security patch.  Both my .NET (Core) Runtimes have only been installed for a few months so I’m not really sure what “expected” behaviour is for MS .NET (Core) Runtimes when Week C/D Preview Builds are blocked.
————-
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.2251 * Firefox v106.0.5 * Microsoft Defender v4.18.2210.6-1.1.19800.4 * Malwarebytes Premium v4.5.17.221-1.0.1806 * Macrium Reflect Free v8.0.7090 * Inspiron 5583/5584 BIOS v1.21.0

1 user thanked author for this post.

WCHS

Reply | Quote

As you can see from Sections 3 and 4, AKB2000016 was written in the version 1909-2004 time frame. MS has changed GP settings since then.

Deferring Previews builds/Feature Updates for 0 or 1 day may still work. Previews have shown up in the second tier under the actual list of updates for me. There is a Registry setting:

HKLM\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\State
BranchRediness REG_SZ =CB

That used to signify “Corporate(?) Branch” that kept updates from being offered until they were declared “Ready for business.”

.NET is something else. I have always installed the .NET Framework security with the Patch Tues. updates before the Previews come out. And I have no experience with .NET (Core) as none of the programs I use require it.

Reply | Quote

PKCano wrote:

As you can see from Sections 3 and 4, AKB2000016 was written in the version 1909-2004 time frame. MS has changed GP settings since then.

Thanks for the quick response.  I guess I’ll have to wait until another MS .NET Framework update is released that does NOT have a security patch to see what happens.  This month’s KB5020687 (2022-11 Cumulative Update for .NET Framework 3.5, 4.8 and 4.8.1 for Win 10 v21H2 for x64) included a security patch for CVE-2022-41064 so I would have expected it to be delivered during my Nov 2022 Patch Tuesday Updates, regardless of whether Week C/D Preview Builds were blocked or not.

Once my Patch Tuesday updates are applied I often wait a few weeks and then pause any further updates at Settings | Update & Security | Windows Update | Advanced Settings | Pause Updates | Select Date so I wouldn’t know if Windows Update was trying to deliver a Week C/D Preview Build for my OS or not.  I’ll leave my Windows Update “unpaused” this month until the day before the Dec 2022 Patch Tuesday updates are released on 13-Dec-2022 and see if any Preview Builds are offered this month.

Just an FYI that the second image in  post # 2275043 of your 2000016: Guide for Windows Update Settings for Windows 10 that I referred to in my previous post is titled “Section 5. Method 2: Group Policy Settings beginning with Win10 v2004″.  That’s why I assumed that image still showing the option to select “Semi-Annual Channel” was meant to include Win 10 v21H2 (and presumably Win 10 v22H2).
————–
Dell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.2251 * Firefox v106.0.5 * Microsoft Defender v4.18.2210.6-1.1.19800.4 * Malwarebytes Premium v4.5.17.221-1.0.1806 * Macrium Reflect Free v8.0.7090 * Inspiron 5583/5584 BIOS v1.21.0

Reply | Quote

The “semi-Annual Channel” may have been what set the “CB” in the Registry because the function was the same. I did not remark when the “semi-Annual Channel” setting disappeared from GP.

Back in the days of 1909/2004 (maybe even back at 1809), I did a good bit of research on those Registry settings. There is a difference in location in the Registry where the GUI settings, available back then, and the Group Policy settings were placed. It is recorded on the site, along with screenshots, in several threads if you want do do some looking. Look at the dates on the earliest posts associated with AKB2000016 to get a starting point.

Reply | Quote

Do the instructions in Section 5 using Group Policy still apply if using Win 11 Pro?

:W10Pro and W11Pro 22H2

Reply | Quote

Basically “Yes.”
But the settings may be in a different location under Windows Update in Group Policy.
Just look for them.
If you can’t find them, just ask.

And wushowhide also works in Win11.

1 user thanked author for this post.

Perq

Reply | Quote

Posting this as an FYI. Not sure of this is the correct place, but perhaps the esteemed PKCano can re-home it to get it noticed.

At any rate, encountered the issue w/ wushowhide not running from a network drive, and moved (rather than copied it) to my Windows 10 machine. Went to run it from my Windows 11 machine, couldn’t find it (obv.), so I downloaded it from Major Geeks. When I ran it, I got a message that “Troubleshooters have been moved, and this tool will be retired” (see attachment).

The “Learn more” link brought me to this page (which tells you to run system>troubleshoot>troubleshooters instead): Deprecation of Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters – Microsoft Support

Unsurprisingly there isn’t an equivalent troubleshooter to wushowhide, and ironically, the Windows Update troubleshooter has the same “warning” banner.

Hoping this just means we won’t be able to D/L wushowhide anymore, versus it won’t run, but it seems in line with the general trend to make it much harder for us to selectively apply updates. Look forward to any thoughts, intel, suggestions you all might have.

Thanks!

Reply | Quote

cyclical01 wrote:

encountered the issue w/ wushowhide not running

Check WUSHOWHIDE is back here on AskWoody. The Microsoft URL for downloading is there. See if this one works.

Reply | Quote

There is a link to wushowhide download in the first section of AKB2000016.

Reply | Quote

Sorry – I guess I did not make the point of my post clear. As you can see in the attachment, running this on Win 11 22H2 I get a message wushowhide will be retired. Was just bringing it to the attention of the community because, if true, this resource may not be available to us in the future. Thanks!

Reply | Quote

PKCano wrote:

Basically “Yes.”
But the settings may be in a different location under Windows Update in Group Policy.
Just look for them.
If you can’t find them, just ask.

And wushowhide also works in Win11.

I found the corresponding settings for Win 11 Pro and they work as expected

:W10Pro and W11Pro 22H2

1 user thanked author for this post.

PKCano

Reply | Quote

Sorry for posting in a not so recent thread, but I wasn’t sure where else to put this.  I’ve seen this for a while now but have not seen addressed anywhere — my WUShowHide has had a message that says “Troubleshooters have moved and this tool will be retired.”  I noticed this a while ago, but it was not there before that.  Is this true?  Assuming it is, what would be the best replacement for someone on Windows 11 Pro who usually uses WUShowHide and “Edit group policy”?

Reply | Quote

Felix wrote:

I’ve seen this for a while now but have not seen addressed anywhere — my WUShowHide has had a message that says “Troubleshooters have moved and this tool will be retired.”

I’ve not ever seen that message in WUSHOWHIDE, not even just now.

If you look at the Master Patch List, you will see an AskWoody Block-a-Patch link to various tools for hiding patches, WUSHOWHIDE among them. You might considered replacing your old WUSHOWHIDE with a new one, from this URL. Or trying one of the others listed there.
Block-a-Patch

Reply | Quote

Reply | Quote

I see the same message on my Win 11 PC (but not on Win 10). I have actually asked this question twice, but never received a reply to either. I haven’t noticed any other change – it seems to still work fine but I worry it may suddenly stop working some day.

1 user thanked author for this post.

Felix

Reply | Quote

I assume the reason for not seeing any answer to that question is because currently it is just a warning message, the tool still works, and there is not yet any information or specifics from MS on the replacement troubleshooting tool. Because of this message and that MS has appeared to pull WUSH in the past, I have started getting used to using an alternate tool; in my case WUMgr.
Also, I feel confident that the good folks at askwoody will have a solution if the new proposed MS tool proves inadequate once it happens.

Reply | Quote

1.  Here’s what I see:
2.  I have no idea where that picture above ( https://www.askwoody.com/forums/topic/comments-on-akb-2000016-guide-for-windows-update-settings-for-windows-10/#post-2624665 or https://www.askwoody.com/wp-content/uploads/2017/06/cu_wushowhide.png ) came from — it’s not what I attached and I don’t even have that at all

Reply | Quote

@Felix –

As both Neil (above) and @PKCano (right below) have pointed out, the tool still works. I use it quite a bit with Windows 10 Pro and I (like probably all others who use it with Win 10) don’t see the warning.

So, it’s very likely limited to being shown to only Windows 11 users. My guess is that MS does indeed plan to sunset the use of most tools/troubleshooters ending in the “.diagcab” suffix within Windows 11 in the near future. My further guess is that they’ll make the tools run from a server somewhere within their site and only be accessibly by certain routines built deep into the Windows 11 ecosystem (very similar to the SaaS concept: Software as a Service).

One way for you to find out just what the warning entails is to click the blue link that says “Learn more” that’s contained within the warning next time you launch wushowhide and see what the page that comes up says. That, I would hope, should remove all doubt about what is meant in that warning, and just may provide some sort of deadline of when wushowhide will be retired for those on Windows 11.

Reply | Quote

In true MS Fashion, the “Learn More” link results in more confusion not less. 😆

Deprecation of Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters – Microsoft Support

For your consideration:

“If you’re running Windows 11 version 22H2 and older, Windows 10, Windows 8.1, Windows 7 or any other earlier OS version, your device will not be affected by the MSDT Troubleshooter retirement. Earlier OS systems will continue to run the legacy inbox troubleshooters.”

True: I am on 22H2 and can still use WUSHOWHIDE. Yippeee!

“In 2023-2024, Microsoft will redirect the following legacy inbox troubleshooters from devices running Windows 11 version 22H2.” 

Everything listed has a link to “Get Help” except Windows Update, which is listed, but not as WUSHOWHIDE (although I am guessing that’s what they mean, but maybe not).

Regardless, did they not just say 22H2 or older would NOT be affected? 😖

“Starting in 2023, if you open one of the legacy inbox troubleshooters, you’ll see an in-product message alerting you to the upcoming retirement and a link to learn more about the process.

Important: If you’re running Windows 11 version 22H2 and older you won’t see this in-product message and the legacy inbox troubleshooters will still work on your device.”

Ummmm, running 22H2, get the message. WUSHOWHIDE still works, however, see above.

So, guess I will hold onto 22H2 for as long as they let me, accelerate my plans to experiment with some of the other Block a Patch tools before they deprecate WUSHOWHIDE without warning, and keep my fingers crossed they don’t try to block the other Block a Patch tools too. 🤞

 

1 user thanked author for this post.

Felix

Reply | Quote

wushowhide still works in Win 10 and Win11 as of a few days ago when I last used it.

Click “Advanced” and UNCHECK “Apply Repairs Automatically” then continue.

1 user thanked author for this post.

Felix

Reply | Quote

That’s very interesting on both points.  On the second point, I’ve actually seen the opposite advice elsewhere, but without any explanation.  It’s actually confusing as to what that option does.

Reply | Quote

It lets YOU choose what you want to do.

1 user thanked author for this post.

Felix

Reply | Quote

Just posted on a possibly related issue here: https://www.askwoody.com/forums/topic/instructions-for-un-hiding-an-update-using-wushowhide/#post-2696506

Reply | Quote

Because the tool is still working and there is currently only a warning message, I infer that the reason no one has responded to that question is that Microsoft has not yet provided any details or information about the alternative diagnostic tool. Owing to this notice and the fact that Microsoft has been known to withdraw WUSH in the past, I’ve started utilizing a different tool—in my instance, WUMgr.
Furthermore, I have no doubt that the kind people at Askwoody will come up with a workaround in the event that the newly recommended MS tool turns out to be sufficient.

spelling bee answers[/url]

Reply | Quote

philip90 wrote:

I have no doubt that the kind people at Askwoody will come up with a workaround in the event that the newly recommended MS tool turns out to be sufficient.

I don’t think that there will be a newly tool.
Stick to WUmgr.

If you run a Pro version set ‘notify=2’ and you won’t need to Meter or pause.

Reply | Quote