Set TargetReleaseVersion to 20H2 (or newer)

What’s going on?

Since the release of Windows 10 20H2 setting the TargetReleaseVersion through CSP doesn’t work anymore because of the “H” in the version.
But there is a way around this issue, at least with Workspace ONE.

Because the regkeys we need to set are located under the Policy hive, we can’t use a normal configuration profile to set them through CSP.

So, we will use PowerShell to solve this.

The Profile

Create a new device profile for Windows Desktop.
Head down to the Custom Settings.
Select “Workspace ONE Intelligent Hub” as the target and uncheck “Make Commands Atomic”.

In the text area for the “Install Settings” enter:

<wap-provisioningdoc id="37d2b624-8b51-4904-aaa5-1783d9874d66" name="customprofile">
  <characteristic type="com.airwatch.winrt.powershellcommand" uuid="bd71b32e-9d0b-4871-ade3-9054ea01fb63">
    <parm name="PowershellCommand" value="Invoke-Command -ScriptBlock { if (-not (Test-Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate')) { New-Item 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' }}"/>
  </characteristic>
<characteristic type="com.airwatch.winrt.powershellcommand" uuid="98624590-5521-4f01-887d-a1e956d04374">
    <parm name="PowershellCommand" value="Invoke-Command -ScriptBlock { Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name TargetReleaseVersion -value '00000001' -Type DWord -Force }"/>
  </characteristic>
<characteristic type="com.airwatch.winrt.powershellcommand" uuid="7e84c2ee-b9cc-4fed-9f22-d9cf218e5f33">
    <parm name="PowershellCommand" value="Invoke-Command -ScriptBlock { Set-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name TargetReleaseVersionInfo -value '20H2' -Type String -Force }"/>
  </characteristic>
</wap-provisioningdoc>

And for the “Remove Settings”:

<wap-provisioningdoc id="37d2b624-8b51-4904-aaa5-1783d9874d66" name="customprofile">
<characteristic type="com.airwatch.winrt.powershellcommand" uuid="bd71b32e-9d0b-4871-ade3-9054ea01fb63">
    <parm name="PowershellCommand" value="Invoke-Command -ScriptBlock { Remove-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name TargetReleaseVersion -Force }"/>
  </characteristic>
<characteristic type="com.airwatch.winrt.powershellcommand" uuid="7e84c2ee-b9cc-4fed-9f22-d9cf218e5f33">
    <parm name="PowershellCommand" value="Invoke-Command -ScriptBlock { Remove-ItemProperty -Path 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate' -Name TargetReleaseVersionInfo -Force }"/>
  </characteristic>
</wap-provisioningdoc>

You can replace the two GUIDs with your own ones (PowerShell: New-Guid).

Save, publish and assign the profile.
VoilĂ , that’s it.

Was this helpful?

0 / 0

Leave a Reply 0

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.