Share via

How to interperet the ambiguity of what OS a group policy setting supports?

Shawn McKinnon 20 Reputation points
2025-11-29T15:19:23.54+00:00

For example, the policy "Always open All Control Panel Items when opening Control Panel" claims to support "At least Windows Server 2003 operating systems or Windows XP Professional", which by itself is pretty self explanitory. But when compared to a policy such as "Turn off Application Compatibility Engine", which supports "At least Windows Server 2003", does the latter imply the former or does it strictly mean all Windows Server type OSs since Windows Server 2003? But from what I understand, the Application Compatibility Engine is implemented on Client Editions too? Maybe it has to be a Server OS in order to disable it, and Client OSs (at least through Group Policy) can't disable it.

Another "inconsistency" is the "SUPPORTED_Windows_10_0_22H2" claim. Why is it expressed as such, when other policies simply say something like "Windows 10 22H2 only". Of course thats if the intended meaning is so. Does it actually mean "At least Windows 10 22H2".

Furthermore, why even continue to provide the option for admx files specific to Windows 11 2XH2, for policies that supposedly support "Windows Server 2003, Windows XP, and Windows 2000 only". Also, with the CSP Policy reference on Microsoft Learn, Every policy -- which probably mirrors the same policies previously talked about -- practically supports Windows 10 and later (though uses the term "Applicable" rather than "supports"). Which does not align with other documentation on the matter. So should I disregard what's in the spreadsheet and follow that?

Maybe I'm missing something (very good possibility) but I can't understand it, and haven't found any discussion on it either. Anyhow, hopefully this information is known, and thanks for any insight.

Windows for business | Windows Client for IT Pros | Devices and deployment | System management components
0 comments
Answer accepted by question author
  1. Jason Nguyen Tran 5,025 Reputation points Independent Advisor
    2025-11-29T17:25:19.2866667+00:00

    Hi Shawn McKinnon,

    In general, when a policy says “At least Windows Server 2003”, it means the setting was introduced in Server 2003 but is also available on any later OS that includes the same subsystem. And this often includes client editions, even when the text does not explicitly say so. Older policies were written in a time when server and client documentation were separated, which is why “Windows Server” appears even when the underlying component (like the Application Compatibility Engine) also exists on client builds.

    For newer policies, strings like “SUPPORTED_Windows_10_0_22H2” come from an internal metadata schema used for ADMX packaging. They indicate the minimum supported build, not “only this build,” so yes, it essentially means “Windows 10 22H2 or later.” This differs from older human-written descriptions, which is why the formats do not match. Regarding ADMX files for Windows 11 still containing policies marked for Windows XP/2000: that is expected. ADMX files are cumulative and include legacy definitions so environments with mixed OS versions or older domain controllers can still interpret them even if modern clients ignore unsupported entries.

    As for CSP policy references, they apply only to MDM-managed configurations and do not always align 1:1 with Group Policy because CSPs map to different configuration channels. When in doubt, always rely on:

    • The ADMX “supported” metadata (minimum OS build), and
    • Your client’s actual behavior when applying the setting (gpresult /h).

    I hope this helps clarify the situation. If you find this answer useful, please consider clicking “Accept Answer” to support others in the community 😊.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.