Why Get-AppxPackage Reports an Orphaned Family Name on Windows 11

When you run the Get-AppxPackage PowerShell cmdlet on Windows 11, the output may show a package with a FamilyName value that does not match any installed app. This orphaned entry often appears after a failed app update, a manual package removal, or a corrupted user profile. The orphaned family name does not affect system stability but can clutter package lists and break scripts that rely on clean output. This article explains why the orphaned entry persists and how to remove it safely.

Why an Orphaned Family Name Appears in Get-AppxPackage Output

An orphaned family name occurs when the package registration in the Windows AppX deployment system remains after the actual package files are removed. The FamilyName property in Get-AppxPackage output identifies the package publisher and name, such as Microsoft.WindowsStore_8wekyb3d8bbwe. When a package is partially uninstalled or an update fails, the registration entry persists even though the app cannot launch.

Common causes include:

• Failed app updates: Windows Update or the Microsoft Store may leave a stale entry when an update does not complete.
• Manual package removal: Using Remove-AppxPackage without the -AllUsers parameter may leave orphaned entries for other accounts.
• Corrupted user profile: A damaged profile can cause the package manager to lose track of installed apps while retaining their registered names.
• Third-party uninstallers: Tools that remove apps outside of the standard AppX APIs often leave residual registrations.

The orphaned family name does not consume disk space but can cause scripts that iterate over Get-AppxPackage output to fail or produce incorrect results. For example, a script that checks for the presence of Microsoft Teams may incorrectly report it as installed.

Steps to Identify and Remove an Orphaned Appx Package

Follow these steps to locate the orphaned package and remove it from your user account. Run PowerShell as an administrator for full access.

1. Open PowerShell as administrator
   Press the Windows key, type PowerShell, right-click Windows PowerShell in the search results, and select Run as administrator. Confirm the User Account Control prompt.
2. List all Appx packages for the current user
   Run the command Get-AppxPackage | Select-Object Name, PackageFullName, PublisherId. Review the output for any package with a Name or PublisherId that does not correspond to an app you recognize or use.
3. Check for packages installed for all users
   Run Get-AppxPackage -AllUsers | Select-Object Name, PackageFullName, PublisherId. This command shows packages provisioned for every user account on the device. An orphaned entry may appear here even if it does not show under the current user alone.
4. Identify the orphaned package
   Compare the output of the two commands. If a package appears only in the -AllUsers list and not in the current user list, it is likely orphaned. Note the PackageFullName value, which looks like Microsoft.WindowsStore_22110.1401.1.0_x64__8wekyb3d8bbwe.
5. Remove the orphaned package from the current user
   Run Remove-AppxPackage -Package "FullNameHere", replacing FullNameHere with the PackageFullName value from step 4. For example: Remove-AppxPackage -Package "Microsoft.WindowsStore_22110.1401.1.0_x64__8wekyb3d8bbwe". If the command succeeds, the orphaned entry is removed from the current user profile.
6. Remove the orphaned package for all users if needed
   If the package still appears in the -AllUsers list after the previous step, run Remove-AppxPackage -Package "FullNameHere" -AllUsers. This removes the registration for every user account on the device. Restart PowerShell and run Get-AppxPackage -AllUsers | Select-Object Name to confirm the entry is gone.

What to Do If the Orphaned Package Cannot Be Removed

Remove-AppxPackage Returns an Access Denied Error

This error occurs when the package is provisioned for the system or protected by Windows. Run the command in an elevated PowerShell session. If the error persists, the package may be part of the Windows base image. Use the Deployment Image Servicing and Management tool to remove it. Run DISM /Online /Remove-ProvisionedAppxPackage /PackageName:"FullNameHere".

Orphaned Entry Reappears After a System Restart

A reappearing orphaned family name indicates that the package is being re-registered by a scheduled task or a Group Policy. Check Task Scheduler under Microsoft > Windows > Appx for tasks related to package deployment. Look for policies under Computer Configuration > Administrative Templates > Windows Components > App Package Deployment in the Local Group Policy Editor. Disable any policy that forces app reinstallation.

Get-AppxPackage Still Shows the Orphaned Entry for a Different User

Switch to the affected user account by signing out and signing in as that user. Repeat the removal steps from within that user session. If you cannot sign in as that user, use the Get-AppxPackage -User "Domain\Username" and Remove-AppxPackage -User "Domain\Username" -Package "FullNameHere" commands from an elevated PowerShell session.

Get-AppxPackage Output: Orphaned Entry vs Normal Package

Item	Orphaned Package	Normal Package
PackageFamilyName	Present and valid	Present and valid
IsDevelopmentMode	False	False
IsFramework	May be false	May be false
IsResourcePackage	False	May be false
SignatureKind	May be Store or System	Store or System
Can launch the app	No	Yes
Appears in Start menu	No	Yes

An orphaned package often has a valid PackageFamilyName but cannot launch the app. The PackageFullName for an orphaned entry may have a version number that does not match any installed app. Use the Can launch the app check to confirm whether a package is orphaned.

To verify that the orphaned entry is gone, run Get-AppxPackage -Name "OrphanName" after removal. If the command returns no output, the package is successfully removed. You can now run scripts that depend on Get-AppxPackage output without false positives. For persistent orphaned entries, consider using the DISM command with the /Remove-ProvisionedAppxPackage option to clean the system image.