> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/installation/upgrade-rmh/upgrading-rmh.md).

# Upgrade RMH

## **Plan for the upgrade**

* Download the latest release of RMH.
* Review the release notes and readme. Determine if there are any known issues that could potentially impact on business operations. Ensure that all store computers and registers meet or exceed the minimum system requirements.
* If the business uses any third-party add-ins or extensions, contact the vendor to confirm they will work with the latest version of RMH. If necessary, work with the vendor to obtain a version of the add-in or extension that is compatible with the latest version of RMH.
* Ensure you have the installation package for the store’s current version of RMH on hand in case you are unable to complete the upgrade and you need to roll back the changes.
* Schedule the upgrade for a day when the store is closed and you have sufficient time to perform the upgrade and roll back if necessary.
* Work with the business owners to develop test scripts that are pertinent to the store’s operations.
* If possible, test the upgrade in a lab environment before performing the upgrade in the store.

## **Prepare for the upgrade**

* Perform a Z report on every register.
* Back up any custom reports, receipt templates, purchase order templates, etc. that have been saved to store computers or registers.
* Exit all RMH applications and any third-party add-ins or extensions.
* Perform any required Windows updates and ensure that all store computers and registers are configured with the latest service packs and hot fixes.
* Restart all store computers and registers.
* Back up the store database.

## **Uninstall the old version**

On each store computer and register:

1. Log in with Administrator privileges.
2. Open **Control Panel**.
3. Under **Programs**, click **Uninstall a program**.
4. Uninstall all RMH applications.
5. Uninstall any add-ins or extensions.
6. Go to **C:\Program Files\Retail Hero\\** and delete any files remaining in that folder.
7. Restart the computer.

## **Install the new version**

On each store computer and register:

1. Log in with Administrator privileges.
2. Copy the installation package to a local folder, e.g., C:\ RMH.

{% hint style="warning" %}
Accessing the application package from a UNC network path, e.g., \xyz\RMH , is not recommended.
{% endhint %}

3. Extract all of the files from the installation package.
4. Right-click **Setup.exe** and select **Run as Administrator**.
   * If you receive a user account control prompt, click **Yes**.
   * Click **Accept** or **OK** for any other warnings, as required.
5. Install the RMH applications in the following order:
   1. Store Manager
   2. POS
   3. Any add-ins or extensions d. Loyalty
6. If necessary, enable RMH desktop shortcuts to open the applications with Administrator privileges to ensure users who do not have Administrator privileges can start and access the applicable RMH applications:
   1. Right-click the RMH desktop shortcut and select **Properties**.
   2. Click **Advanced**.
   3. Select **Run as administrator**.
   4. Click **OK**.
   5. Click **Apply**.
   6. Click **OK**.
7. Install any add-ins or extensions.
8. Restart the computer.

## **Pre-start checks**

1. Start **Store Administrator**.
2. Click **Configuration**.
3. On the **Database** tab, confirm that Store Manager is connected to the correct store database.
4. On the **Register** tab, confirm that the register **Number** and **Language** are correct.
5. If you make any changes, click **Save And Close**.
6. Click **Connect**.
7. Confirm that the **Database** is the correct store database.
8. Enter the **Password** for **SQL Server Authentication**.
9. Click **Connect**.
10. Click **Database**.
11. Click **Reindex** to reindex the database. Click **Yes** to continue.
12. Click **Change Collation** and confirm that the **Server** and **Database** are correct.
13. If you make any changes, click **Change**. Otherwise, click **Cancel**.

## **Test the installation**

1. Log in to **Store Manager**.
2. Perform a smoke test to ensure all key functions are accessible and functioning as expected.
3. Check that custom reports, receipt templates, purchase order templates, etc. are accessible and functioning as expected.
4. Log in to **POS**.
5. Enter a test transaction.
6. Refund or void the transaction.
7. Ask business owners to run additional tests as required to confirm that the system is fully functional. Run through any test scripts that the business owners have developed.
8. Confirm that the following are accessible and functioning as expected:
   * All custom POS buttons;
   * Credit card processing;
   * All add-ins and extensions; and
   * Stock Take, if the business uses it.
9. Review any known issues from the release notes and confirm they have no material impact on the store operations.
10. If this version of RMH contains enhancement requests or fixes to issues the business had reported, test these and confirm they address the needs of the business owners.
11. Provide training on new functionality, as required.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rmhpos.com/installation/upgrade-rmh/upgrading-rmh.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.