How to re-authorize a new target version in WindowsUpdate?

C

ch.b

New Member
I have set the target version of Windows Update to 21H2 using NTLite in an image deployed on many computers.
I would now like to authorize the upgrade to version 22H2.
In the registry I see this: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsUpdate] "ProductVersion"="Windows 10" "TargetReleaseVersion"=dword:00000001 "TargetReleaseVersionInfo"="21H2"
In theory it is enough to change it to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsUpdate] "ProductVersion"="Windows 10" "TargetReleaseVersion"=dword:00000001 "TargetReleaseVersionInfo"="22H2"
But this does not have the expected effect (even after a reboot) Windows update does not detect the 22H2 update...

If someone has an idea?
 
This policy only restricts WU from upgrading your system, but MS still needs to offer your PC the upgrade.

Based on your system configs (HW & installed apps), it might take longer to get around to your PC. MS has been gradually rolling out upgrades so it can stop the process if it learns about compatibility issues.

For troubleshooting, you can always remove the registry keys on a test machine and reboot.
 
And Settings/ Feature Updates safeguards (Upgrade block) is set to default? It have 2 options: Default/ Disabled.
My target release is set to Default too - but blocked via reg as it's easy to pick an updated Win install:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
"BlockFeatureUpdates"=dword:00000001
 
Last edited:
ch.b said:
In theory it is enough to change it to [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsUpdate] "ProductVersion"="Windows 10" "TargetReleaseVersion"=dword:00000001 "TargetReleaseVersionInfo"="22H2"
But this does not have the expected effect (even after a reboot) Windows update does not detect the 22H2 update...

If someone has an idea?
Click to expand...
In theory setting "ProductVersion"="Windows 10" to
"TargetReleaseVersionInfo"="22H2" don't compare.
Maby working when setting "ProductVersion"="Windows 10" to 11 as it's 22H2.
If theory works!
 
You must log in or register to reply here.
Back
Top