How to fix Error 454 on Windows 11

by

Troubleshooting Guide: Error 454 – “No Capability Authorization Policy on the Device”

Why This Error Happens

Error 454 typically occurs when Windows 11’s capability access management system fails to locate or apply a valid policy that governs app permissions (such as camera, microphone, location, or contacts access) for a specific device or user profile. This is often caused by corruption in the Windows registry keys under CapabilityAccessManager, a misconfigured Group Policy Object (GPO) pushed via Active Directory or Intune, or a failed Windows Update that left privacy/permission databases in an inconsistent state. In enterprise environments, this can also result from a missing or unsynced Mobile Device Management (MDM) policy that hasn’t been properly enrolled or refreshed.

Step-by-Step Resolution Guide

  1. Check Local Group Policy Settings
  • Press Win + R, type gpedit.msc, and press Enter.
  • Navigate to Computer Configuration > Administrative Templates > Windows Components > App Privacy.
  • Ensure “Let Windows apps access…” policies are set to Not Configured or Enabled (not conflicting with system defaults).
  1. Reset the Capability Access Manager Registry Keys
  • Press Win + R, type regedit, and press Enter.
  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager.
  • Right-click the folder, export a backup, then delete the corrupted subkey (e.g., ConsentStore) and restart the PC to force Windows to regenerate it.
  1. Re-sync MDM/Intune Policies (For Managed Devices)
  • Go to Settings > Accounts > Access work or school.
  • Click your organization account, select Info, then click Sync under the Device Sync section.
  • This forces Windows to re-pull the correct capability policies from your management server.
  1. Run the Windows Update Troubleshooter
  • Go to Settings > System > Troubleshoot > Other troubleshooters.
  • Run the Windows Update troubleshooter to repair any policy files corrupted during a failed update cycle.
  1. Perform an SFC and DISM Scan
  • Open Command Prompt as Administrator.
  • Run sfc /scannow, followed by DISM /Online /Cleanup-Image /RestoreHealth to repair corrupted system files that manage app capabilities.

Alternative or Verification Steps

  • Verify the Fix: Open Settings > Privacy & security > App permissions and confirm you can toggle access for Camera/Microphone without an error message appearing.
  • Alternative Fix: If the error persists on a domain-joined machine, run gpupdate /force in an elevated Command Prompt to pull the latest policy directly from the domain controller, bypassing local cache issues.