> For the complete documentation index, see [llms.txt](https://docs.engagevr.io/engage/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.engagevr.io/engage/getting-started/installing-engage/installing-engage-on-microsoft-windows.md).
# Installing ENGAGE on Microsoft Windows
First, check that your computer meets the following minimum requirements:
* Microsoft® Windows® 10 operating system
* Intel® Core™ i5 processor or better
* 8 GB RAM
* NVIDIA® GeForce® GTX 970 graphics card or better
* 9 GB of available disk space
If your computer meets the minimum requirements, use one of the following options to install ENGAGE:
### Option 1: ENGAGE Windows Installer
1. To download the ENGAGE Windows Installer, go to , select **Windows PC**.
2. After you download the installation file, run it as an administrator. For example, right-click the installation file, and then select **Run as administrator**.
3. If you see the error shown in the following image, or you see a **User Account Control** window that doesn't accept your credentials, then you don't have administrator rights on your computer. Sign in as a user that has administrator rights, and then repeat from step 1.
### Option 2: Steam
If you have Steam installed on your computer, open the Steam Client, browse to the store, search for ENGAGE, and then add it to your library.
---
# 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.engagevr.io/engage/getting-started/installing-engage/installing-engage-on-microsoft-windows.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.