Why Edge Installed via the Store Lacks Group Policy Support on Windows 11

Microsoft Edge installed from the Microsoft Store on Windows 11 does not show Group Policy settings when you open the Local Group Policy Editor. This happens because the Store version of Edge uses a different update mechanism and registry structure than the system-wide version delivered via Windows Update or Microsoft’s official enterprise channel. The result is that IT administrators cannot enforce browser policies such as startup pages, extension blacklists, or security defaults through Group Policy Objects. This article explains why the Store version lacks Group Policy support, how to verify which version you have, and what steps you must take to restore full policy management.

How the Store Version Differs from the System-Wide Version

Microsoft Edge is available in two primary distribution channels on Windows 11. The first is the Microsoft Store, which delivers a lightweight package using the AppX or MSIX packaging format. The second is the traditional desktop installer, distributed as an .exe or .msi file through the Microsoft Edge for Business portal, Windows Update, or the Volume Licensing Service Center.

The Store version is designed for consumer and small-business scenarios where centralized management is not required. It installs per-user by default and does not register the Edge Group Policy administrative template files in the local policy store. The system-wide version installs machine-wide, registers the .admx and .adml files for Group Policy, and creates the necessary registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge.

Microsoft’s official documentation states that the Microsoft Store version of Edge does not support Group Policy, mobile device management MDM policies, or Windows Information Protection WIP. Only the Stable channel of the system-wide installer includes these capabilities. The Beta, Dev, and Canary channels also lack full policy support unless they are installed from the enterprise download page.

Why Group Policy Administrative Templates Are Missing

Group Policy for Edge relies on administrative template files named msedge.admx and msedge.adml. These files define the policy settings that appear in the Local Group Policy Editor under Computer Configuration > Administrative Templates > Microsoft Edge. The Store version does not include these files because the installer does not run as a system-level setup process. The Store installer uses a sandboxed deployment mechanism that cannot write to the C:\Windows\PolicyDefinitions folder where .admx files reside.

When you open the Local Group Policy Editor after installing the Store version, the Microsoft Edge folder does not appear under Administrative Templates. This is not a bug. It is a deliberate design limitation. The Store version also does not create the corresponding registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge. Without these keys, Group Policy Objects targeting Edge have no effect.

Steps to Verify Your Edge Version and Enable Group Policy

Before you replace the Store version, confirm which Edge installation type is currently on your system. Then uninstall the Store version and install the correct enterprise edition.

1. Open Edge and check the channel
   Launch Microsoft Edge. Click the three-dot menu in the upper-right corner and select Settings. Go to About Microsoft Edge. Look at the version line. If it says Stable and the version number starts with a number like 120.0.2210.91, it may still be the Store version. The Store version shows Microsoft Edge without a channel label in some builds. To be certain, check the installed apps list.
2. Check the installed apps entry
   Open Settings > Apps > Installed apps. Scroll to Microsoft Edge. Click the three-dot menu next to it and select Advanced options. Look at the Version field. If the Package name includes Microsoft.MicrosoftEdge.Stable, it is the Store version. If the entry shows Microsoft Edge without a package prefix, it is the system-wide version.
3. Open the Local Group Policy Editor
   Press Win + R, type gpedit.msc, and press Enter. Navigate to Computer Configuration > Administrative Templates. If you see a folder named Microsoft Edge, Group Policy templates are present. If the folder is missing, the Store version is installed.
4. Uninstall the Store version of Edge
   Go to Settings > Apps > Installed apps. Click the three-dot menu next to Microsoft Edge and select Uninstall. Confirm the prompt. This removes only the Store package. User data such as bookmarks and passwords is preserved in the %LOCALAPPDATA%\Microsoft\Edge folder.
5. Download the enterprise installer
   Open a browser other than Edge, such as Firefox or Chrome. Go to the Microsoft Edge for Business download page at www.microsoft.com/en-us/edge/business/download. Select the Stable channel. Choose the .msi installer for your system architecture x64 or ARM64. Click Download.
6. Install the system-wide version
   Run the downloaded .msi file. Accept the license terms. The installer runs as a system process and places the .admx files in the correct policy folder. After installation, restart the Local Group Policy Editor. The Microsoft Edge folder now appears under Computer Configuration > Administrative Templates.
7. Verify policy registry keys
   Press Win + R, type regedit, and press Enter. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge. If the key exists, Group Policy is active. You can now configure Edge policies using the Local Group Policy Editor or domain-based Group Policy Management.

Common Issues After Switching to the System-Wide Version

Edge Policies Do Not Apply Even After Installing the Enterprise Version

If you installed the enterprise version but policies still do not appear, the administrative template files may be missing or outdated. Download the latest Edge administrative templates from the Microsoft Download Center. Extract the msedge.admx file to C:\Windows\PolicyDefinitions and the msedge.adml file to the corresponding language folder such as en-US. Then run gpupdate /force in an elevated Command Prompt.

Edge Launches as a Different Channel After Reinstallation

If you previously had a Beta or Dev channel installed, the system may launch that version instead of the new Stable channel. Uninstall all Edge channels from Settings > Apps > Installed apps. Then install only the Stable enterprise .msi. Check About Microsoft Edge to confirm the channel is Stable.

User Data Lost After Uninstalling the Store Version

The uninstall process for the Store version removes the per-user Edge profile folder. To preserve bookmarks, passwords, and history, back up the %LOCALAPPDATA%\Microsoft\Edge\User Data folder before uninstalling. After installing the enterprise version, copy the backed-up Default profile folder into the same location. Launch Edge and sign in to sync any remaining data.

Item	Store Version	System-Wide Version
Group Policy support	Not supported	Full support with .admx templates
Installation method	Microsoft Store AppX	.msi or .exe enterprise installer
Registry policy keys	Not created	Created under HKLM\SOFTWARE\Policies\Microsoft\Edge
Update mechanism	Microsoft Store	Microsoft Update or Edge updater
Per-user vs machine-wide	Per-user	Machine-wide

You can now identify the Edge installation type on your Windows 11 system and replace the Store version with the enterprise edition that supports Group Policy. After installing the .msi package, open the Local Group Policy Editor to configure settings such as startup pages, managed favorites, and extension policies. For advanced management, download the latest Edge administrative templates from the Microsoft Download Center and add them to your central policy store.