> 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/updates/update-safely.md).

# Update safely

Wait a few days before installing new releases, get warned about suspicious download changes, and don't update on battery or metered connections.

Most bad releases, whether buggy or compromised, are caught and pulled within a few days. By waiting a little before you update, you let others find the problems first. UniGetUI can also keep automatic updates from draining your battery or your mobile data.

All these options are in ***Settings*** – ***Package update preferences***.

## Wait before installing new versions

1. Go to ***Settings*** – ***Package update preferences***.
2. In ***Minimum age for updates***, choose how many days a version must have been out before UniGetUI offers it, for example 7 days. Choose ***Custom...*** to enter your own number in ***Custom minimum age (days)***.

Newer versions simply don't appear in ***Software Updates*** until they're old enough, so neither you nor automatic updates install them early.

{% hint style="info" %}
A few days is a good balance for most people. For apps exposed to the internet, like browsers, don't wait too long: security fixes matter too.
{% endhint %}

This only works with package managers that publish release dates. The ***Release date support per package manager*** table on the same page shows ***Yes***, ***Partial*** or ***No*** for each one. Where it says ***No***, updates appear right away.

**Different rule for one package manager?** Open ***Package Managers*** in the menu on the left, select the manager, and change ***Minimum age for updates*** under ***Update security***. ***Use global setting*** follows the value above.

## Get warned when the download source changes (WinGet)

***Warn me when the installer URL host changes between the installed version and the new version (WinGet only)*** is on by default. When a new version downloads from a completely different server than the version you have, ***Software Updates*** shows an orange warning icon next to the new version. Hover it to see the old and new hosts.

This is usually harmless: the publisher moved to a new host. But it can also mean the package entry was tampered with. Before updating, check that the new host belongs to the publisher, for example in ***Package details*** – ***Installer URL***. If in doubt, [skip this version](/unigetui/guides/updates/hold-a-version.md).

## Don't update on battery or metered connections

These options apply only to updates installed automatically, so they're unavailable until you turn on ***Install available updates*** in ***Scheduled maintenance***.

* ***Do not automatically install updates when the device runs on battery***
* ***Do not automatically install updates when the battery saver is on***
* ***Do not automatically install updates when the network connection is metered***, for example a phone hotspot

The updates aren't lost. UniGetUI notifies you that updates are available instead, and tries again later.

{% hint style="info" %}
UniGetUI can only detect the battery and metered connections on Windows. On macOS and Linux, these options have no effect.
{% endhint %}

## Good to know

* Updates don't show up or don't install? A minimum age or a battery rule is often the reason. See [Scheduled updates don't run](/unigetui/help/troubleshooting/scheduled-updates-dont-run.md).
* All these settings, with their defaults, are in [All settings](/unigetui/reference/settings.md).

## Next

* [Choose which apps update automatically](/unigetui/guides/updates/automatic-updates.md)
* [Where packages come from and what to trust](/unigetui/guides/understand/trust-and-security.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/updates/update-safely.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.