> For the complete documentation index, see [llms.txt](https://support.powerio.com/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.powerio.com/hub/faq/faq-en/powerio-system-faq/beibehalten-von-anwendungen-bei-einem-firmware-update.md).

# Keeping applications during a firmware update

To ensure that Applications are retained during a firmware update, only a few prerequisites must be met.

{% stepper %}
{% step %}

#### Checking the minimum version

* Each Application requires a minimum firmware version.
* The minimum version can be found in the [download area](/hub/downloads/en/user-applications/codesys.md) of the Application.

{% hint style="success" %}
Good to Know!

* If the Application does not meet the minimum version, a firmware update is still possible.
* The Application only needs to be reinstalled afterwards.
  {% endhint %}
  {% endstep %}

{% step %}

#### Ensure that the Application is uploaded and installed

* Navigation "Applications"
* Check whether the installed Application is present **and** whether its version matches the versions in the areas\
  \&#xNAN;**“Uploaded powerIO packages”** and **“Installed powerIO packages”** matches.

{% hint style="info" %}
The versions are displayed directly in the "Applications" overview.\
For [more information on understanding the versions](/hub/faq/faq-en/powerio-system-faq/updates-und-versionen.md#applications-1) there is help available here.
{% endhint %}
{% endstep %}

{% step %}

#### Done!

* The previously installed Application, e.g. "CODESYS", remains present after a firmware update and automatically continues running with the previous settings.
  {% endstep %}
  {% endstepper %}


---

# 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://support.powerio.com/hub/faq/faq-en/powerio-system-faq/beibehalten-von-anwendungen-bei-einem-firmware-update.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.