Forum Discussion
TargetReleaseVersion CSP is broken
The TargetReleaseVersion CSP (https://docs.microsoft.com/en-us/windows/client-management/mdm/policy-csp-update#update-targetreleaseversion) is broken for newer versions of Windows 10 due to having characters in the version (i.e. 20H2) instead of just numbers (2004). When will this be fixed? This issue has been in place for nearly 6 months.
1 Reply
- Jason_Sandys
Microsoft
This is a known defect that is addressed in the latest May cumulative update for all versions of Win 10. After this CU is applied using 20H2 (or 21H1) is valid and will work. Prior to applying this CU, you should use 2009 instead of 20H2 for this CSP.
