Orphaned Apps
An orphaned app is what is left over when software was uninstalled but did not clean up after itself. The program is gone; its traces are not.
O&O AppBuster finds these traces and can remove them. Two types are distinguished: Orphaned App for leftovers of Windows apps, and Orphaned Desktop App for leftovers of classic programs.
Why leftovers matter
They are not merely untidy:
- They take up disk space. An app data folder can hold hundreds of megabytes of caches that nothing will ever read again.
- They can block a reinstallation. A Windows Installer product registration without a matching program makes Windows believe the software is already installed, so a new setup refuses to run or fails with an unhelpful error.
- They keep an entry in your program list. A Programs and Features entry pointing at an uninstaller that no longer exists cannot be removed by Windows itself.
The third case in particular is the classic "I cannot get rid of this entry" problem.
What O&O AppBuster looks for
Orphaned Windows apps
A data folder exists under %LocalAppData%\Packages whose package family does not belong to any installed Windows app. The app is gone; its settings, caches and saved state are still on disk.
Orphaned desktop apps
Either of the following:
- The app's registered install location exists in the registry but the directory is not on disk any more.
- The app has no install location and none of the files it points to — its icon, its uninstall program — can be found.
Ghost installer registrations
A Windows Installer product is registered under HKCR\Installer\Products, but there is no matching uninstall entry, and the product is not among the installed apps. These are the registrations that block reinstallations.
If a ghost registration is found but the program's files are still on disk, the app is not orphaned — it is defect. The app still works; only its installer metadata is broken. O&O AppBuster reclassifies these so they are not treated as harmless leftovers.
Understanding a leftover before removing it
Leftovers rarely have friendly names. What Windows keeps is a technical identifier, so a leftover may appear as something like Microsoft.MicrosoftEdge_8wekyb3d8bbwe or a bare GUID.
For orphaned apps, O&O AppBuster therefore tries to interpret the identifier, and shows the result in the app's properties:
| Field | Meaning |
|---|---|
| Friendly Name | A readable name for what this leftover belonged to |
| Original Identifier | The raw identifier as Windows stored it |
| Original Name | The name recorded in the registration, where one exists |
| Vendor / Product Family | Which manufacturer and product family it appears to come from |
| Likely Purpose | What the component was probably for — a browser sandbox, an Office add-in, a sync component |
| Confidence | High, Medium or Low — how reliable the interpretation is |
| Description | A longer explanation of the interpretation |
If the identifier cannot be interpreted, the friendly name reads Unknown orphaned application entry and the description says that no reliable product mapping could be determined.
A High confidence entry has been recognised as a known leftover. An unknown entry has not — it just looks like one. Read the identifier and the install location before removing anything you cannot place.
Components that belong to a program that is still installed
Some entries look orphaned but are not: they are supplementary components installed by a larger program. A plugin service, an Office add-in, a device-communication helper. They often have no install location of their own, because they install into their parent program's directory — which is exactly the signal O&O AppBuster uses to detect an orphan.
Removing such a component does not clean anything up; it breaks the parent program. Typical examples are a manufacturer's device plugin service, or a meeting add-in for Office.
O&O AppBuster carries a safeguard for known supplementary components and does not classify them as orphaned while their parent is still installed. It cannot know every such component, though, so if an entry's name mentions an add-in, a plugin, a service or a helper for a program you still use, leave it alone.
Cleaning up
Orphaned entries are removed like any other app: select them and click Uninstall. Since there is no program left to uninstall, O&O AppBuster removes the leftover itself:
| Type | What is removed |
|---|---|
| Orphaned Windows app | The data folder under %LocalAppData%\Packages |
| Orphaned desktop app | The stale uninstall entries in the registry (64-bit view, 32-bit view and the current user's hive) and any remaining install directory |
| Ghost installer registration | The Windows Installer product registration and the installer's user-data entries |
If files are locked by a running program, you are offered the same choices as for a normal removal: close the blocking programs, defer the deletion to the next restart, or skip the item.
Removing orphaned entries requires care because no uninstaller is available to verify the cleanup. Create a system restore point first and review the entries one at a time.
When the Orphaned chip does not appear
The Orphaned Smart View chip is only shown when there is something in it. On a PC that has not had much software come and go, you may never see it — which is the good case.