> For the complete documentation index, see [llms.txt](https://wiki.retrobat.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.retrobat.org/get-started/installation-and-first-startup.md).
# Installation & First Startup
Let's get started!
## Installation
* Download the latest RetroBat installer from the [RetroBat website](https://www.retrobat.org/download/).
* Run the installer and click **Next**.
* Read and accept the license agreement, then click **Next**.
* Select the missing prerequisites to install, then click **Next**.
{% hint style="info" %}
The installer automatically installs the required prerequisites (Visual C++ Redistributables, DirectX). If they are already installed, this page will not appear.
{% endhint %}
* Choose the installation folder and click \*\*Install\*\*.
{% hint style="danger" %}
**Where to install RetroBat**
Install RetroBat in a short path, inside a folder, for example `C:\RetroBat` or `D:\Games\RetroBat`.
Avoid:
* Installing directly at the root of a drive (RetroBat files would end up mixed with everything else in `D:\`). Always use a folder.
* Spaces, accents or special characters in the path.
* Long paths or deeply nested folders: they cause issues with some emulators (e.g. the MAME libretro core).
* `C:\Program Files` or `C:\Program Files (x86)`: Windows restricts write access, so settings and saves may not be stored.
* Folders synchronized with OneDrive (Desktop, Documents, Pictures are often synchronized by default).
{% endhint %}
* Wait until the installation completes, then click **Finish**.
To learn what each RetroBat folder contains, see [RetroBat Folder Structure](/get-started/retrobat-folder-structure.md).
## First startup
Double-click the `RetroBat.exe` file in your RetroBat folder, or use the desktop shortcut.
After the intro video, the **System View** is displayed.
{% hint style="info" %}
At first startup, RetroBat uses your Windows language if it is supported: English, French, Japanese, Spanish, German, Italian, Dutch, Portuguese, Russian, Korean, Chinese, Polish and Arabic.
{% endhint %}
You can navigate with the keyboard or with a controller (see [Navigation Keys](/navigation/navigation-keys.md)).
If your controller is not configured automatically:
* Press any button: the **CONFIGURE INPUT** screen appears.
* Press and hold any button on the controller you want to configure: the **CONFIGURING** screen appears.
* Press the corresponding button on your controller for each input. If your controller does not have a given button, press and hold any button to skip it.
{% hint style="info" %}
We recommend using **SELECT** (or **Back**/**View** on Xbox controllers) as the **hotkey**. The hotkey is combined with other buttons to trigger shortcuts, such as exiting a game or saving a state. See [Hotkeys](/navigation/hotkeys.md).
{% endhint %}
**Congratulations!** RetroBat is installed and running. Next step: Adding a game.
---
# 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://wiki.retrobat.org/get-started/installation-and-first-startup.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.
