WindowsStore.admx — Inverted semantics for "Disable all apps from Microsoft Store"

Question

WindowsStore.admx — Inverted semantics for "Disable all apps from Microsoft Store"

Terrusltime 20

The Group Policy setting "Disable all apps from Microsoft Store" defined in WindowsStore.admx has inverted Enabled / Disabled semantics compared to its display name.

Current behavior:

Enabled → DisableStoreApps = 0 → Microsoft Store applications are allowed to launch.
Disabled → DisableStoreApps = 1 → Microsoft Store applications are prevented from launching.

The policy help text correctly documents this behavior, so the issue is not an implementation or documentation mismatch. The problem is that the policy name implies that enabling the policy should disable Microsoft Store applications, while the actual behavior is the opposite.

This can easily lead administrators to apply the wrong configuration, especially when reviewing or deploying large numbers of Group Policy settings.

The issue is also present in the English Administrative Template and is therefore not specific to the French localization.

Because changing the existing registry mapping could affect compatibility with existing deployments, a possible solution would be to rename the policy using positive semantics while preserving its current registry behavior.

Could Microsoft confirm whether this is a known issue in WindowsStore.admx and route it to the Windows Group Policy / Administrative Templates team? If this is not the appropriate channel for reporting an ADMX defect, what is the supported escalation channel?

Full technical report, reproduction steps, ADMX/ADML excerpts, screenshots, file hashes, and tested environments: https://github.com/Terrusltime/windows-admx-policies-issues/tree/main/WindowsStore/DisableStoreApps-inverted-semantics

Feedback Hub link : https://aka.ms/AA13byhu

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Terrusltime, this registry logic has been established in production environments for years, Microsoft cannot alter the underlying registry mapping. Doing so would instantly reverse the Microsoft Store access configurations for existing domain deployments worldwide. Your suggested approach of renaming the display string in the ADML file to reflect positive semantics is the safest and most practical fix.

Regarding your question about the escalation channel, the link you provided is the officially supported avenue for reporting ADMX logic errors and non-security defects directly to the Windows Engineering teams. Public support forums do not have a backend routing mechanism to forward external GitHub repositories to internal product groups. Your detailed documentation has been submitted to the correct triage queue. Moving forward, you will need to wait for Microsoft to release an updated ADML file via a future update, and administrators should be advised to rely on the accurate policy help text in the interim.

Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VPHAN