> 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/install-pos/installation-pos-dot-net.md).
# Install POS for .NET
This topic describes how to install POS for .NET on store computers that are running the POS app.
{% hint style="info" %}
You must install POS for .NET on all computers where POS is installed.
{% endhint %}
1. Go to the location where you extracted the release package files.
2. Double-click **Setup.exe** to open the setup wizard.
{% hint style="info" %}
You must have administrative privileges on the computer to install RMH apps.
{% endhint %}
3. Under **Prerequisites**, click **Install POS for .NET**.
4. Click **Next**.
5. On the **End-User License Agreement** screen select **I accept the terms in the License Agreement** and click **Next**.
6. On the **Customer Experience Improvement Program** screen, select **No thanks** and click **Next**.
7. On the **Destination Folder** screen, select the installation folder and click **Next**.
8. On the **Product Features** screen, accept the defaults and click **Install**.
9. Wait while installation is completed. This may take a few minutes.
10. Click **Finish**.
---
# 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.rmhpos.com/installation/install-pos/installation-pos-dot-net.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.
