Action1 simplifies many patch management tasks, including upgrades to Windows 11. However, some of our customers still want to keep Windows 10 for several good reasons, such as compatibility with certain line-of-business applications or to utilize a staggered approach to upgrading large enterprise environments. You don’t want to get 1000 calls from frustrated users on your busy Monday morning complaining about this new unknown Windows version on their PCs.
The following script updates a set of TargetReleaseVersionInfo registry values to force the system to stay on a certain version of Windows. You can use it with your favorite RMM or utilize Action1 to configure multiple endpoints from the cloud.
################
$win_product = ‘Windows 10′
$win_version = ’22H2’ # update this to the desired version, such as 22H1 or 23H1
Set-ItemProperty -Path ‘HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\’ -Name ‘TargetReleaseVersion’ -Value 1 -Type DWord
Set-ItemProperty -Path ‘HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\’ -Name ‘TargetReleaseVersionInfo’ -Value $win_version
Set-ItemProperty -Path ‘HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate\’ -Name ‘ProductVersion’ -Value $win_product
##################
P.S. If you don’t automate patch management and endpoint configuration yet, look at Action1. It is free forever for your first 100 endpoints – with no strings attached!
