Why Broken Entries Appear
When an application is uninstalled, Windows removes most files but sometimes leaves behind specific registry values under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. If the installation process was interrupted, corrupted, or forced closed via Task Manager, the entry remains visible even though the program files are gone. Additionally, some modern apps (UWP) store data in the Appx packages folder, which can become orphaned if the manifest file is damaged.
These broken entries typically display as generic icons or show "Not available" when clicked. They do not appear in the Control Panel legacy view but are prominent in the Settings app. Ignoring them can lead to confusion during software management and may interfere with system updates that check for existing components.
Method 1: Using PowerShell to Remove Orphaned Packages
For modern Windows Store apps or UWP applications that leave broken entries, PowerShell offers a clean removal command. This method targets the package catalog directly rather than relying on the GUI installer.
- Right-click the Start button and select Terminal (Admin) or PowerShell (Admin).
- Run the following command to list all installed packages:
Get-AppxPackage | Select Name, PackageFullName- Identify the
PackageFullNameof the broken entry from the output. - Execute the removal command, replacing the placeholder with the actual full name:
Remove-AppxPackage -Package "PackageFullName"If the package is system-protected, this command may fail. In such cases, proceed to Method 2. Note that this approach only affects app packages and does not remove traditional desktop applications registered in the registry.
Method 2: Manual Registry Cleanup for Desktop Apps
Traditional Win32 applications store their uninstall information in the Windows Registry. Removing these keys manually eliminates the broken entry from the Apps & Features list. Exercise extreme caution when editing the registry, as incorrect changes can destabilize the operating system.
- Press
Win + R, typeregedit, and press Enter to launch the Registry Editor. - Navigate to the following path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall- Expand the folders and subfolders until you locate the key corresponding to the broken application. You can identify it by checking the
DisplayNamevalue on the right pane. - Right-click the identified key and select Delete.
- Repeat this process for any other orphaned entries found in this location.
After deleting the keys, restart your computer. The broken entries should no longer appear in the Settings app. If the entry persists, check the HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall path as well, as some user-specific installations may reside there.
Method 3: Using Microsoft Troubleshooter
Microsoft provides an official troubleshooter tool designed specifically to fix problems that prevent programs from installing or being removed. This utility can automatically detect and repair corrupted uninstall strings without manual registry intervention.
Download the Program Install and Uninstall Troubleshooter from the Microsoft Support website. Run the executable and select Uninstalling when prompted. Choose the problematic application from the list provided. If the app does not appear, select Not Listed and enter the exact name of the broken entry. The tool will scan the registry, identify the corrupt uninstall string, and replace it with a dummy entry that allows the system to clear the reference. Once completed, restart your PC to apply the changes.
Preventing Future Issues
To minimize the risk of creating broken entries, always use the standard uninstallation process through Settings or Control Panel. Avoid force-quitting uninstallers via Task Manager unless absolutely necessary. Keep your system updated, as patches often include fixes for known uninstall bugs. For complex applications, consider using dedicated uninstaller software like Revo Uninstaller, which scans for leftover files and registry keys after the standard removal process completes.
If you are experiencing broader application issues alongside these broken entries, such as apps failing to launch entirely, refer to our guide on Windows Apps Won't Start: Troubleshooting a 12th Gen Intel Core i5 System for deeper diagnostic steps related to hardware compatibility.
Frequently Asked Questions
Will removing registry keys delete my actual files?
No, deleting the uninstall registry key does not remove the application's program files from your hard drive. It only removes the record that tells Windows how to uninstall the app. You should manually delete the remaining program folders in Program Files after ensuring the entry is gone.
Can I recover a deleted registry entry if I made a mistake?
If you accidentally delete a valid key, you can restore it by reinstalling the application. The installation process will recreate the necessary registry entries. Alternatively, if you have a recent System Restore point, you can revert the registry to its previous state before the deletion occurred.
Why does the broken entry still show after deleting the registry key?
This usually happens because the entry exists in multiple locations. Check both HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER under the Uninstall path. Additionally, some modern apps cache their presence in the AppX manifest, requiring the PowerShell method described above for complete removal.
Is it safe to use third-party uninstallers for this problem?
Yes, reputable third-party uninstallers are generally safe and often more thorough than manual methods. They automatically search for leftover files, folders, and registry entries. However, always download these tools from official vendor websites to avoid malware, and create a system restore point before performing deep scans.
What should I do if the Troubleshooter fails to find the app?
If the troubleshooter cannot locate the broken entry, it indicates the uninstall string is completely missing or corrupted beyond automatic repair. In this case, manual registry deletion (Method 2) is the most reliable solution. Ensure you are looking at the correct DisplayName value to avoid deleting unrelated system components.