> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/unigetui/help/troubleshooting/app-not-listed.md).

# An app I installed isn't listed

Find out why an app installed on your computer is missing from UniGetUI or never shows an update, and what you can do about it.

An app you know is installed doesn't appear in ***Installed Packages***, or it's listed but never shows up in ***Software Updates***, even when its publisher has released a new version.

## Why it happens

UniGetUI only knows what package managers tell it (see [How UniGetUI works](/unigetui/guides/understand/how-it-works.md)). An app can be missing or not updatable because:

* **Its package manager is disabled or not installed.** For example, Chocolatey apps don't show if Chocolatey is off.
* **The source isn't added.** The app comes from a bucket, feed or repository that the package manager doesn't know about yet.
* **No package manager knows the app.** UniGetUI may still list it (WinGet detects most installed Windows apps), but with the source ***Local PC***, which means it can't be matched to a package, so there are no updates.
* **It's a Microsoft Store app.** The Store updates its own apps; WinGet only reports updates for a few of them.
* **The update is held back.** It's ignored, skipped, paused, or newer than your ***Minimum age for updates***.
* **The installed version is unknown.** Some installers don't record a version, so the package manager can't compare it with the latest one.

## Fix it

1. **Refresh the list.** Click ***Reload*** on the page, in case the app was installed after UniGetUI loaded it.
2. **Check the package manager.** Click ***Package Managers*** in the navigation menu. Make sure the manager the app comes from is enabled and ***Ready***. If it shows ***Not found***, install it first. See [Supported package managers](/unigetui/reference/package-managers.md).
3. **Check the source.** Look at the app's source in the list:
   * ***Local PC***: no package manager can update this app. Search for it in ***Discover Packages***. If you find it, you can reinstall it from there so UniGetUI can manage it. Otherwise, update it the way the publisher intended.
   * A source you don't have: open the package manager's settings and use ***Add source***.
4. **Check for held-back updates.** In ***Software Updates***, click ***Manage ignored updates***, and remove the app if it's there. Then check ***Minimum age for updates*** in ***Settings*** – ***Package update preferences***. See [Keep an app on a specific version](/unigetui/guides/updates/hold-a-version.md) and [Update safely](/unigetui/guides/updates/update-safely.md).
5. **For Microsoft Store apps,** update them from the Microsoft Store: open ***Library*** and click ***Get updates***.

{% hint style="info" %}
Drivers, firmware, some hardware utilities and apps with their own updater often aren't known to any package manager. That's a limit of the package managers, not something UniGetUI can fix. See [What UniGetUI doesn't do](/unigetui/guides/understand/limits.md).
{% endhint %}

## Still missing?

* All WinGet apps are missing, not just one: see [WinGet is missing or broken](/unigetui/help/troubleshooting/winget-missing-or-broken.md).
* The app is listed by the package manager in a terminal (for example `winget list`) but not in UniGetUI: [send the logs to support](/unigetui/help/troubleshooting/send-logs-to-support.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/unigetui/help/troubleshooting/app-not-listed.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.