This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 89%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBW%3C/text%3E%3C/svg%3E)
Hi There,
I have set the TargetReleaseVersionInfo via GPO yesterday, to our new Feature update we are going to (22H2) however when checking for updates in Windows update it does not allow the 22H2 update to be found and says i am up to date yet still only on 20H2.
Is there any logs i can check to find out why this is happening? I can clear down SoftwareDistribution folder but would like to see if there is a way i can look into logs before just deleting and trying again.
Kind regards,
Ben
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 17%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETS%3C/text%3E%3C/svg%3E)
I am experiencing the same problem. We have recently rolled out 21H2 to one of our customers, by setting target version to 21H2, however, when setting to 22H2 the feature update is not appearing as available.
Hi,
Found that the issue is that a new ProductVersion registry entry is now required with "Windows 10" as the value.
As soon as I set this, the update pulled through.
Hi Tim,
Thanks for this, just to confirm is this done through GPO? Or did you just create a new REG_DWORD called ProductVersion with the value 'Windows 10' then gave it some time and the 22H2 feature update came through Windows update?
Did you just put it in the location below or any area specific in the registry:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
Kind regards,
Ben
Hi Ben,
I did this via a remote script instead of through a GPO (due to the remote nature of the devices I'm working with), But I have no doubt you could deploy via GPO too.
Yes, same location as the targetrelease keys. Just needs to be a REG_SZ.
For reference I added using the below script deployed via our remote management tool.
reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate /f /v ProductVersion /t REG_SZ /d "Windows 10"
Hi Tim,
Perfect that worked!!
Kind regards,
Ben
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
1 deleted commentComments have been turned off. Learn more