大网数据广告活动
启动与系统组件

Troubleshoot UWP Apps Failing to Open Due to Registry Permissions

· 52CE 我爱测

Learn how to fix UWP apps that fail to open or close immediately due to registry permission issues. Follow troubleshooting steps to restore functionality.

Summary

Universal Windows Platform (UWP) apps are designed to run on Windows 10 and Windows 11 using a single code base. This article explains how to troubleshoot UWP apps that fail to open or close immediately due to registry permission issues, helping you restore functionality.

Symptoms of UWP app failures

On Windows 10 or Windows 11 devices, built-in UWP apps may fail to open or close immediately after launch. This issue affects all user accounts on the device.

Affected apps may include:

  • Microsoft Store
  • Company Portal
  • Microsoft Entra (Azure AD) Broker Plugin (Token Broker)
  • Microsoft Lock Screen–related components

Additional symptoms may include:

  • Repeated crashes of BackgroundTaskHost.exe
  • Application crash events referencing twinapi.appcore.dll
  • Exception code 0xC0000409
  • Error signatures including FAIL_FAST_FATAL_APP_EXIT_8007000e

Cause of registry permission issues

This issue occurs when required registry permissions are missing on the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

UWP apps run under the ALL APPLICATION PACKAGES security principal (SID: S-1-15-2-1) and require Read access to this key. If this permission is missing or inheritance is disabled, UWP apps cannot read required system configuration data and may fail to start.

In affected environments:

  • The ALL APPLICATION PACKAGES entry is missing the required Read permission.
  • Access control list (ACL) inheritance is blocked on the key.
  • The permission may exist under ControlSet001 but is missing from CurrentControlSet, which is the active control set used at runtime.

Troubleshooting steps for UWP apps

Follow these steps to resolve the issue.

Important: Incorrect changes to the registry can cause serious system problems. Follow these steps carefully and make sure you have a backup before proceeding.

Step 1: Open PowerShell as an administrator

  1. Select Start, and type PowerShell.
  2. Right-click Windows PowerShell, and then select Run as administrator.

Step 2: Set the target registry path

Run the following command in PowerShell to set the target registry path:

$path = "HKLM:\SYSTEM\CurrentControlSet\Control"

Step 3: Enable inheritance

Run the following commands to enable inheritance on the registry key:

$acl = Get-Acl $path
$acl.SetAccessRuleProtection($false, $true)
Set-Acl -Path $path -AclObject $acl

Step 4: Add "ALL APPLICATION PACKAGES" ReadKey permission

Run the following commands to add the required permission:

$acl = Get-Acl $path
$accessRule = New-Object System.Security.AccessControl.RegistryAccessRule(
    "ALL APPLICATION PACKAGES",
    "ReadKey",
    "ContainerInherit,ObjectInherit",
    "None",
    "Allow"
)
$acl.SetAccessRule($accessRule)
Set-Acl -Path $path -AclObject $acl

Step 5: Verify the permissions (optional but recommended)

Run the following command to verify that the ALL APPLICATION PACKAGES permission is correctly applied:

(Get-Acl $path).Access | Where-Object { $_.IdentityReference -like "*ALL APPLICATION PACKAGES*" }

Resolution

After restoring the required permissions:

  • UWP apps should open normally.
  • Microsoft Store, Company Portal, and other affected apps should function as expected.
  • BackgroundTaskHost.exe crash events should no longer occur.

If the issue persists, restart the device and test again.

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Client · Source date 05/07/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。