> 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/guides/understand/limits.md).

# What UniGetUI doesn't do

The apps and updates UniGetUI can't handle, why, and what to do about each of them instead.

UniGetUI can only manage what a package manager knows about. Most "why isn't this app listed?" questions come down to that one rule. Here are the common cases, so you know where to look instead.

## Most Microsoft Store apps don't show updates

UniGetUI sees Store apps through WinGet. They appear in ***Installed Packages***, and you can install Store apps from ***Discover Packages*** when WinGet's `msstore` source is enabled. But most of them never show up in ***Software Updates***, even when the Store has a newer version.

That's expected. WinGet only reports updates for a small set of Store apps. The rest are updated by the Microsoft Store itself. To update them, open the ***Microsoft Store*** app, go to your library, and get updates there, or turn on automatic app updates in the Store settings.

## Apps no package manager knows

If an app isn't in any catalog, UniGetUI can't find a newer version, so it can't update it. This usually covers:

* **In-house or niche apps**, such as tools made by your company or by very small publishers.
* **Drivers, firmware and hardware utilities**, such as graphics drivers or the tools that come with a printer or a laptop. Use the manufacturer's updater for these.
* **Games from launchers.** On Windows, games installed with Steam, GOG or Ubisoft Connect can appear in ***Installed Packages***, but their launcher keeps them up to date.

On Windows, apps that WinGet detects but can't match to its catalog show ***Local PC*** as their source. You can see and uninstall them, but you won't get updates for them through UniGetUI.

## Operating system updates

On Windows and macOS, UniGetUI doesn't replace Windows Update or macOS Software Update. Keep those turned on.

On Linux, it's different: APT, DNF, Pacman, Snap and Flatpak do manage system packages, so UniGetUI can show and install those updates too.

## Scheduled tasks need UniGetUI running

UniGetUI runs its scheduled update checks, installations and backups itself. It doesn't create tasks in the operating system's scheduler. If UniGetUI isn't running at the scheduled time, nothing happens until it runs again.

Keeping it minimized in the notification area is enough. See [Run updates on a schedule](/unigetui/guides/updates/schedule.md).

## UniGetUI doesn't vet the apps you install

UniGetUI passes your request to the package manager, which downloads the installer from the publisher. It isn't an antivirus and doesn't review apps. Check the publisher before installing something unfamiliar. See [Where packages come from and what to trust](/unigetui/guides/understand/trust-and-security.md).

## Some installers don't stay silent

UniGetUI asks package managers to install and update apps silently, but some installers ignore that. They may show a window, ask a question, or close the app they're updating. Save your work before running large batches of updates.

## If it doesn't work

* An app is installed but not listed at all: see [An app I installed isn't listed](/unigetui/help/troubleshooting/app-not-listed.md).
* A package manager doesn't appear: check its requirements in [Supported package managers](/unigetui/reference/package-managers.md).
* Scheduled updates don't run: see [Scheduled updates don't run](/unigetui/help/troubleshooting/scheduled-updates-dont-run.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/guides/understand/limits.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.
