> 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/rdm/knowledge-base/how-to-articles/configure-a-custom-download-path-for-devolutions-updater.md).

# Configure a custom download path for Devolutions Updater

Set a custom download path for Devolutions Updater in Remote Desktop Manager instead of using the default temp folder location.

Set a custom download path for Devolutions Updater instead of downloading in %TEMP%. It can be configured in two ways.

### Method 1: From the File menu

Go to ***File – Settings – Paths*** and enter a ***Custom download path*** in the field.

### Method 2: Directly in the updater

1. In the ***Help*** tab, click on ***Check for Updates***.
2. If Remote Desktop Manager can be updated, the ***Update Available*** pane will open. From there, click on ***Download***, then select one of these options:
   * ***Download this version and install now***: Devolutions Updater will open right now.
   * ***Download this version and install when application is closed***: Devolutions Updater will open after closing Remote Desktop Manager.
3. When the Devolutions Updater window appears, click on ***Options***.
4. Enter the ***Custom download path*** of your choice, then click ***Close***.
5. Click on ***Update*** and follow the standard update process.


---

# 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/rdm/knowledge-base/how-to-articles/configure-a-custom-download-path-for-devolutions-updater.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.