Hi all,

Has anyone had issues with a feature update showing for a device in Automox after setting the target release version in registry?

This is the second time I’ve had this issue.

I set the target release version to 23h2, enabling it with the value of 1, and specifying the product version of win 11. Once I set those values, I rescan the machine and usually the update is showing as a patch for the device in Automox, but in this case, it isn’t. The device is win 11 ready.

Any ideas?

This is the PS script I’m using to push out the reg keys. I’ve ran this on 20+ devices and the update shows up with no issues.

#># Define Values in this section
#############################################
$rValue = '1' #Enable Target Release Version 0 = Disabled, 1 = Enabled
$rInfoValue = '23h2' #Specify Windows 11 Target Release Version. Select the preferred version from https://docs.microsoft.com/en-us/windows/release-information/
$rWindows = 'Windows 11' #Specify Windows 11
#############################################
$rPath = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate'
$rKeyPath = 'HKLM:\Software\Policies\Microsoft\Windows'
$rVersion = 'TargetReleaseVersion'
$rVersionInfo = 'TargetReleaseVersionInfo'
$rVersionWindows = 'ProductVersion'
try {
if(-not(Test-Path -path $rPath)){
New-Item -Path $rPath -Force -ErrorAction Stop | Out-Null
}
Write-Output "SUCCESS: Target Release Version keys set`t"
New-ItemProperty -Path $rPath -Name $rVersion -PropertyType DWord -Value $rValue -Force -ErrorAction Stop | Out-Null
Write-Output "$rpath exists`t"
New-ItemProperty -Path $rPath -Name $rVersionInfo -PropertyType String -Value $rInfoValue -Force -ErrorAction Stop | Out-Null
New-ItemProperty -Path $rPath -Name $rVersionWindows -PropertyType String -Value $rWindows -Force -ErrorAction Stop | Out-Null
Write-Output "$rVersion = $rvalue and $rVersionInfo = $rInfoValue`t" Exit 0
} catch { $Exception = $error=0].Exception.Message + "`nAt Line " + $error+0].InvocationInfo.ScriptLineNumber
Write-Error $Exception
Exit 90
}