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

# Upgrade Status Window

If the site is running Commander Site Controller feature set 37 or above, the Auto Upgrade process is split into two phases:

•Phase One: System Upgrade

•Phase Two: Historic Data Restore

After all Phase One tasks are complete, the site is fully functional to perform sales and other operations.

Phase Two tasks will run in the background and do not interrupt any site operations. A typical phase two task is restoring previously closed totals data.

The POS terminal displays the Upgrade Status Window with progress bars indicating the status of the executing task and overall installation progress.

Along with the current task information, the status window also includes the status of previously executed tasks. ***The message, “Please wait,*** ***server reboot in progress...”*** appears in the progress bar area during stages of the Commander Site Controller reboot.

After all Phase One tasks ***show “Completed”,** the* overall status shows 100% completed and the status *message **“Auto Upgrade*** ***Phase 1 Completed” is*** displayed.

*When the system message displays **“Auto Upgrade Phase 1 Completed. Phase 2 in*** ***progress (restoring previously closed totals)”,** do one of the following:*

•Click **\[OK]** to dismiss the overlay message and continue with Sales or other site operations.

•Perform no action until upgrade phase two is complete; the upgrade status window will continue to be displayed on the POS terminal.

*During Phase Two, a **“Restore (Stage 2)”** status message is displayed on the POS* terminal.

At any point during Phase Two, tasks can be monitored on any POS terminal by selecting **CSR Func > Maintenance > Show Upgrade Status**.

If the site is running Commander Site Controller feature set 38.15 or above, the Auto Upgrade Phase Two activity, restore historic totals, will have a timeout of 2 hours 30 minutes.

Historic data for reporting is restored in reverse chronological order. That is, the latest period’s data is restored first followed by the previous period’s data and so on; this process repeats until the oldest available period data is restored.

If the time taken to restore historic data exceeds the specified timeout, the restore process terminates. In case of termination due to timeout, the Upgrade Summary Report will include details about the range of restored report periods.

After the upgrade is complete, a message ***window displays confirming the “Upgrade*** ***Completed Successfully.”***

Click **\[OK]** to close the window\*\*.\*\*

During the Auto Upgrade process, the following succession of messages are displayed in the Upgrade Status window of the POS terminal:

* •Preparing for Upgrade
* •File Download (Stage1)
* •Comm Check (Stage1)
* •Software version check
* •Upgrade of upgrade engine
* •Upgrade of upgrade engine Completed
* •Update Upgrade Status
* •Backup (Stage1-12)
* •SC Application Installation
* •Application Installation (Stage2)
* •Restore (Stage1-11)
* •Payload Update
* •Site Initialization
* •Clean up
* •Client Restart / Lookup (Stage1)
* •Restore (Stage2)
* •Clean up


---

# 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.verifone.com/feature-references/features-and-products-references/auto-upgrade/using-auto-upgrade/upgrade-status-window.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.
