en-US windows computer

Allowed package family names for non-admin user install

Verified with Windows 11 25H2 — updated on July 30, 2026

Windows 11 25H2

Supported on: At least Windows 11 Version 22H2

Path in the GPO console

Computer Configuration\Administrative Templates\Windows Components\App Package Deployment

Description

Allowed package family names for non-Administrator user Windows app package installation. If you enable this policy, you can enter a list of Windows app packages non-Administrators will be able to initiate installation of regardless of the configured "Prevent non-admin users from installing packaged Windows apps" policy. The values provided will be treated as regular expressions (ECMA Script). A package family name like Contoso.ContosoApp_8wekyb3d8bbwe is itself a valid regular expression that will match all packages in that family. A regular expression like ^Contoso.*_8wekyb3d8bbwe$ will also match Contoso.ContosoApp_8wekyb3d8bbwe If the package family name of an installing Windows app package matches any rule it will not be blocked by the "Prevent non-admin users from installing packaged Windows apps" policy. Installation may still be blocked by other policy or settings. If you disable or do not configure this policy, all Windows app packages will be subject to the configured "Prevent non-admin users from installing packaged Windows apps" policy. Default is 'disabled' (key not present).

Registry

HKLM Software\Policies\Microsoft\Windows\Appx\AllowedNonAdminPackageFamilyNameRules

More options available

Options

Allowed package family names for non-admin user install
List (registry values) list

MDM / Intune (CSP)

./Device/Vendor/MSFT/Policy/Config/ApplicationManagement/AllowedNonAdminPackageFamilyNameRules
Device Since Windows Insider Preview Official mapping (Microsoft Learn)

Microsoft Learn documentation Mapping data: Microsoft Learn (CC BY 4.0)

Export Builder

BETA

Configure the state, scope and options, then generate .reg, PowerShell, Intune and SCCM outputs — or add the setting to a multi-setting collection.

These exports write the registry — this is not a managed GPO.

.reg file

Windows Registry Editor Version 5.00

; Exported from gporais.com
; Policy: Allowed package family names for non-admin user install
; State: Enabled
; Supported on: At least Windows 11 Version 22H2

[HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Appx\AllowedNonAdminPackageFamilyNameRules]
; List values: enter one value per line in the builder UI.
More formats (PowerShell, Intune, SCCM)

PowerShell

# Exported from gporais.com
# Policy: Allowed package family names for non-admin user install
# State: Enabled
# Supported on: At least Windows 11 Version 22H2

$path = 'HKLM:\Software\Policies\Microsoft\Windows\Appx\AllowedNonAdminPackageFamilyNameRules'
New-Item -Path $path -Force | Out-Null
# List values: enter one value per line in the builder UI.

Building a multi-setting collection? Add this setting and generate combined .reg / PowerShell / GPO scripts.

Open the Builder

Embed this policy on your site

What to embed
Theme

Adds one script line: the theme follows your site’s appearance and the height fits the content. If your site blocks scripts, the embed follows the visitor’s system theme.

Preview