> 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.md). # Keep your apps up to date Update all your apps at once, choose what updates by itself, and hold back what shouldn't change. UniGetUI checks every hour for newer versions of your apps and lists them in ***Software Updates***. From there, you decide how hands-on you want to be: update in one click, let some apps update on their own, or hold an app on the version you need.


Update everything in one click	Review what's outdated and update it all, or just a few apps.	Update everything in one click
Choose which apps update automatically	Let trusted apps update on their own and keep the others for review.	Choose which apps update automatically
Keep an app on a specific version	Skip a version, pause updates, or ignore them for good.	Keep an app on a specific version
Run updates on a schedule	Pick when UniGetUI checks for updates and when it installs them.	Run updates on a schedule
Avoid brand-new releases	Wait a few days before installing new versions, and don't update on battery or metered connections.	Update safely

--- # 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.md?ask=&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.