> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/auto-upgrade/using-auto-upgrade/manual-applied-upgrade.md).

# Manual Applied Upgrade

{% hint style="warning" %}
*Prior to initiating the auto upgrade process, confirm all POS* *terminals are logged out of sales and all fuel pumps are idle.* *Do not start the auto upgrade process if the Advanced* *Preparation section has not been reviewed.*
{% endhint %}

After the software upgrade download has been transferred by one of the above methods:

1. The Commander Site Controller will display an alarm message on all POS ***terminals: “ X.XX.XX Available”.***
2. From a POS terminal, go to: CSR Func > Maintenance.

The Register Maintenance Function Menu will display.

3. Click **\[Apply Upgrade].** When applying the upgrade package, the error message "PMC Not Ready" indicates that the site controller is not communicating with the payment network.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FcT0nCQopSaNHa2v1D4j5%2Fimage.png?alt=media&amp;token=06d94775-5158-44af-ad30-02e1e7e66b67" alt=""><figcaption></figcaption></figure>

The system will initiate the Auto Upgrade process ***and begin “Checking for upgrades.”***

4. When prompted to ***“Print Instructions?”,*** select **\[Yes]** to print the Auto Upgrade Instructions.

Sample of Printed Auto Upgrade Instructions:

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/jenyoEY1SAlU81IhKf57/Unknown%20image)

5. Select **\[Yes]** when prompted to **“Apply Upgrade Now?”** and begin the Auto Upgrade process.


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/auto-upgrade/using-auto-upgrade/manual-applied-upgrade.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.
