How to fix Error 460 on Windows 11

by

Why This Error Happens

Error 460 occurs when an application declares custom capabilities in its AppxManifest.xml (or provisioning package) that are not registered in the System Capability Configuration Database (SCCD) on the Windows 11 device. This mismatch typically happens because the OEM/IT-provisioned capability list was never updated to include the new custom capability GUIDs, the SCCD registry hive has become corrupted, or a Windows Update/feature update reset the capability store to its default state without re-importing custom entries. It can also occur if the provisioning package used to deploy the capabilities failed silently during OOBE or MDM enrollment.

Step-by-Step Resolution Guide

  1. Verify the capability declaration — Open the app’s AppxManifest.xml and confirm the custom capability name/GUID under <Capabilities> matches exactly what was registered on the device (case-sensitive, no typos).

  2. Check the SCCD registry entries — Open regedit.exe and navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\CapabilityAccessManager\CustomCapabilities
    Confirm each declared custom capability has a corresponding key. If entries are missing or malformed, this confirms the SCCD is out of sync.

  3. Re-import the capability definitions using Windows Configuration Designer (WCD):

  • Open Windows Configuration Designer → create/edit a provisioning package.
  • Under Runtime settings > Policies > CustomCapabilities, re-add the missing capability names/GUIDs.
  • Export the package (.ppkg) and apply it via Settings > Accounts > Access work or school > Add or remove a provisioning package, or push it through Intune/MDM.
  1. Repair the system image and capability store — Run the following in an elevated PowerShell/Command Prompt to rule out corruption:
   DISM /Online /Cleanup-Image /RestoreHealth
   sfc /scannow

Reboot after completion.

  1. Restart the Capability Access Manager service — In services.msc, locate State Repository Service and AppXSvc, restart both (or restart the PC) so the SCCD is reloaded from the updated registry/provisioning data.

Alternative or Verification Steps

  • After applying the fix, reinstall or relaunch the affected app and check Event Viewer > Applications and Services Logs > Microsoft > Windows > CapabilityAccessManager-Broker to confirm Error 460 no longer appears.
  • If the issue persists, use Get-AppxPackage -Name <PackageName> | Select Name, PackageFullName in PowerShell to confirm the manifest is correctly installed, then manually re-provision the device using a fresh .ppkg built from a known-good WCD project as a fallback.