> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/launcher/download-and-installation.md).

# Download and installation

Download and install Devolutions Launcher using the typical, custom, or complete setup type after purchasing a package from the Devolutions store.

Once a [package](https://docs.devolutions.net/resources/getting-started-with-devolutions-packages) offering Devolutions Launcher has been purchased from the [Devolutions store](https://store.devolutions.net/package), you can follow these steps to download and install Devolutions Launcher:

1. Download [Devolutions Launcher](https://devolutions.net/download-center/?product=launcher) from our website and launch the executable file.
2. Click ***Next*** on the welcome page, then select a setup type:
   * ***Typical***: Installs the most common program features. Recommended for most users.
   * ***Custom***: Allows users to choose which program features will be installed and where they will be installed. Recommended for advanced users.
   * ***Complete***: All program features will be installed. (Requires most disk space)
3. Continue through the setup, then click ***Install*** at the end.
4. Once done, click ***Finish*** to complete the installation and launch Devolutions Launcher.

#### See also

* [Licensing issues](https://docs.devolutions.net/resources/other-resources/license/licensing-issues)


---

# 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.devolutions.net/launcher/download-and-installation.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.