Sept. update changes GP Target Feature Update Version settings

Topic

New Reply

After running the Sept updates on 20H1 today, I noticed the settings for the GP “Target Feature Update Version” had changed.  First, it was changed to 20H2 (I had it at 20H1), and second there is now another entry “Which Windows product version would you like to receive feature updates for?”  Eg, Windows 10, Windows 11.  That entry was blank, so I don’t know if I’d have been updated to Win10 20H2 or Win11 20H2 next month [if this PC qualified for Win11, which it doesn’t].  Either way, MS seems to be messing around with update settings, again.

Reply | Quote

Replies

Microsoft updates won’t change that value. Are you sure you didn’t use one of my registry keys?

If your computer isn’t compatible with Windows 11, you won’t get Windows 11.

Remember the registry keys I’ve got set up:

https://www.askwoodylounge.com/wl/?id=S63lP8jgrdZ76SwFbMmrcef58RSrbA98  <<< that sets it for Windows 10, 21H1

In anticipation of Windows 11, yes these settings are getting updated.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

No way I would have put in 20H2 at this time.  Nope – didn’t use any of your reg keys.  So yes I won’t get Win11 [don’t want it], but I would have got Win10-20H2 sooner than planned.  It really does seem like 20H1 got changed to 20H2 after the Sept. Update, altho I can’t prove it.

For those PCs that *are* Win11 compatible, what do we get for 20H2 when the “Product Version” is blank like shown in my example screenshot?  10 or 11?

Reply | Quote

If you put in Windows 11, you’ll get offered up 11.  If you put in 10, you won’t see the offering to 11.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

But what happened to me, on 21H1, was that the “Product Version” was blank like shown in my example screenshot.  I suppose that might be because that PC is not Win-11 capable.  I’d expect / hope that Win-10 would be filled in there to avoid confusion, but this is Microsoft after all.  Avoiding / minimizing confusion does not seem to be part of their biz model.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Because it’s brand new in the September updates. It’s there for you to put in Windows 10 if you want to keep it on Windows 10.  PK has posted about it in the Windows 10/Windows 11 section and I’ve written about it in the Plus newsletter for sure.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

georgea wrote:

After running the Sept updates on 20H1 today

Windows 10 20H1 (2004) EOL in 3 months so Microsoft can force you into 20H2 (2009) regardless of TRV.

It is advised to upgrade to 21H1.

Set the new field in TRV for Windows version to ‘Windows 10’ and 21H1.

Check ‘about’ in settings for your current version or run ‘winver’.

Reply | Quote

Oops.  Typo in all my posts for this thread – it’s on 21H1.  Trying to avoid 21H2.

Reply | Quote

Makes more sense.  To be sure, open Start Menu, find RUN, open that and enter winver.  A box will open with the OS version.

I’m not completely sure if that target version thing can’t be changed by MS somehow.  They shouldn’t be able to change it; it used to work.  And yeah, MS has made it so you have to be a SuperAdmin to change all scheduled tasks for updates.

Additionally, if you do updates offline from the catalog, you’ll get far less glopware (edge won’t install, etc) than if you do them online.  Same “security” less interference.  MS is messing with Pro more and more.  I have two Enterprise licenses and they leave that version alone.  Considering buying a Server Essentials license to maybe avoid the Phone Culture Kids at MS altogether.

With half finished Win 11 about to wreck computers worldwide, I pushed updates out 3 years by moving the end dates out here:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings

Use at your own risk, pull them back in for updates to work again and note this somewhere; in 6 months, you won’t remember.

1 user thanked author for this post.

wavy

Reply | Quote

Susan Bradley wrote:

Because it’s brand new in the September updates. It’s there for you to put in Windows 10 if you want to keep it on Windows 10.

W10 Pro 21H1.  Just installed the September Update okay (19043.1237).  Then I updated TRV to show “Windows 10” (new field) and 21H1.  Question: once done, does this change the registry, and, if so, what key?

Postscript: to answer my own question, I found the TargetProductVersion (and TRV) here:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UpdatePolicy\PolicyState\TargetProductVersion

 

Reply | Quote

What if I just put in Windows 10 in the first box and don’t specify a target version in the second box, will that block Windows 11 without tying me to a particular Win10 release.

Reply | Quote

What if I just put in Windows 10 in the first box and don’t specify a target version in the second box, will that block Windows 11 without tying me to a particular Win10 release.

To answer the question, I believe that if you specify Windows 10 without specifying a version number in the box below it, such as 21H1 or 21H2 for example, MS will then give you the latest Feature Update after the number of days or after the specific date you have set in Group Policy, albeit the Feature Update for Windows 10 not for Windows 11. In other words, if you’re currently on Windows 10 version 21H1 (or any other earlier version probably), you’ll be pushed to Windows 10 version 21H2 after the number of days or after the specific date you have set in Group Policy, but you WILL stay on Windows 10, you won’t be pushed to Windows 11. This setting is located in Group Policy under Computer Configuration>Administrative Templates>Windows Components>Windows Update>Windows Update for Business. Once you double click on the Windows Update for Business folder, look for the item labeled “Select when Preview Builds and Feature Updates are received”. Double clicking on that will show you the settings currently in effect.

That second box is used to help you stay on your current version until YOU are ready for your computer to receive the latest Feature Update, NOT when MS thinks you should receive it. Many times the latest Feature Updates have had problems due to poor or incomplete code in some aspects which then would bring computers to their knees in the worst cases, or cause the computer to slow way down in many other cases. This is why most folks here don’t usually install the Feature Update on the day it’s released.

Reply | Quote

I’m running Windows 10, and my CPU is not worthy of Windows 11. (Ryzen 5 1600). After updating to 21H1 (build 19043.1257) or perhaps more recently, on checking for updates. I see that my Windows now reports “Some settings are managed by your organization.” (This is a homebuilt computer used for my personal use, and not part of a domain.) On further drilling down, this means “Target release version for feature updates” has been set.

Although I’m running Win10 Pro, I have NEVER set anything to do with TRV in the registry. Also, I have NEVER used WUMgr or WUShowHide to regulate updates. All I have ever used is the Advanced Settings to delay updates until DEFCON 4.

I’m not (currently) too worried about this, but just thought I would add to the discussion.

Thanx,

Zig

Reply | Quote

Zig wrote:

“Some settings are managed by your organization…Advanced Settings to delay updates until DEFCON 4”

Click the link under the notice ‘view configured update policies’ to display the changes you have made with GPedit/Windows update (pause, deferrals..) or 3rd party registry hacks software.

Reply | Quote

Alex,

Click the link under the notice ‘view configured update policies

That’s exactly what I did when I said “On further drilling down.” But I have NOT set any such value manually with GPedit or 3rd party registry hacks. I’ve only used Advanced Options to defer updates.

Zig

Reply | Quote

Zig wrote:

I’ve only used Advanced Options to defer updates.

Any change to Windows Update settings including deferral will bring up that notice.
You are not suppose to interfere with Windows Updates. 🙂

Reply | Quote