> 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/ribbon-menu-bar/file/settings/application/paths.md).

# Paths

Set the folders Remote Desktop Manager uses for screenshots, documents, SSH keys, recordings, logs, and temporary files, and integrated app paths.

Go to ***File*** – ***Settings*** – ***Application*** – ***Paths*** to set the folders that Remote Desktop Manager uses for its files. The installation paths of the external applications it launches are set in ***File*** – ***Settings*** – ***Application*** – ***Integrated applications*** (see [Integrated applications](#configure-installation-path)).

For each folder, leave the field empty to use the default folder, which is displayed in the empty field. Click the button next to a field to browse to a folder.

### Paths

<table><thead><tr><th width="250">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Screenshot</strong></td><td>Folder where screenshots taken in Remote Desktop Manager are saved. Windows only.</td></tr><tr><td><strong>Document</strong></td><td>Default folder proposed when saving or opening documents and attachments. Windows only.</td></tr><tr><td><strong>Default templates</strong></td><td>Folder that contains the default templates of the entry types. Windows and macOS only.</td></tr><tr><td><strong>SSH keys</strong></td><td>Default folder for SSH key files. Windows only.</td></tr><tr><td><strong>Recording</strong></td><td>Default folder proposed when saving session recordings. By default, the <em>Documents</em> folder of the user. Windows and macOS only.</td></tr><tr><td><strong>Update folder</strong></td><td>Folder where the installation packages of Remote Desktop Manager updates are downloaded. Windows only.</td></tr></tbody></table>

On Linux, this section also contains the path to the ***MikroTik Winbox*** and ***ISL Light*** executables, and the ***Smart card PKCS library*** used by terminal sessions (`opensc-pkcs11` by default).

### Advanced

<table><thead><tr><th width="250">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Application log</strong></td><td>Folder where the application log files are written.</td></tr><tr><td><strong>Temporary script folder</strong></td><td>Folder where Remote Desktop Manager creates the temporary script files it runs. Windows and Linux only.</td></tr><tr><td><strong>Temporary folder</strong></td><td>Folder where Remote Desktop Manager creates its temporary files. Windows and Linux only.</td></tr><tr><td><strong>Delete contents of temporary folders when closing application</strong></td><td>Delete the files in the temporary folders when Remote Desktop Manager closes. Enabled by default. Windows only.</td></tr></tbody></table>

### Integrated applications <a href="#configure-installation-path" id="configure-installation-path"></a>

Remote Desktop Manager launches several external applications (VPN clients, web browsers, FTP clients, terminals, viewers, etc.). By default, it looks for each application in its usual installation folder. Use ***Integrated applications*** to see where an application was found, or to point Remote Desktop Manager to another folder when the application is installed in a custom location. Windows only.

1. Go to ***File*** – ***Settings*** – ***Application*** – ***Integrated applications***.
2. Select an application in the list. Its settings are displayed in the same page.
3. Adjust its settings, then click ***Save***.

Click ***Auto-detect all*** to search the computer for every application of the list, and turn on ***Missing only*** to list only the applications that were not found.

{% hint style="info" %}
For a VPN, the same settings are also available from the VPN settings of an entry, under ***Installation path*** – ***Configure***.
{% endhint %}

The list groups the applications under ***Applications***. Use the ***Search*** field to filter it by name. The list contains the applications used by the entry types and add-ons of Remote Desktop Manager, for example:

<table><thead><tr><th width="200">GROUP</th><th>EXAMPLES</th></tr></thead><tbody><tr><td><strong>Ftp</strong></td><td>FileZilla, WinSCP</td></tr><tr><td><strong>Password Manager</strong></td><td>KeePass</td></tr><tr><td><strong>PowerShell</strong></td><td>PowerShell, PowerShell 7</td></tr><tr><td><strong>SQL</strong></td><td>HeidiSQL, SQL Server Management Studio</td></tr><tr><td><strong>Virtualization</strong></td><td>Hyper-V, Oracle VirtualBox, VMware Player, VMware Workstation, VMware Remote Console</td></tr><tr><td><strong>VNC</strong></td><td>RealVNC, TightVNC, UltraVNC</td></tr><tr><td><strong>VPN</strong></td><td>Cisco VPN Client, Cisco AnyConnect, FortiClient, SonicWall Global VPN Client, Tailscale, Cloudflare WARP, OpenVPN, WireGuard</td></tr><tr><td><strong>Web</strong></td><td>Google Chrome, Firefox</td></tr><tr><td><em>(No group)</em></td><td>Microsoft Remote Desktop Client, Windows App, PuTTY, TeamViewer, Radmin Viewer, DameWare Mini Remote Control, Chocolatey, Git, Azure Storage Explorer, PsExec, AutoHotkey, AutoIt</td></tr></tbody></table>

{% hint style="info" %}
The applications of optional add-ons only appear in the list when the add-on is installed.
{% endhint %}

The ***Configuration*** tab contains the installation settings of the selected application:

<table><thead><tr><th width="250">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Installation path</strong></td><td><p>Folder where the application is installed. Enter the folder only, not the executable file name. Leave the field empty to let Remote Desktop Manager use the default path; the path it found is then displayed in the empty field.</p><p>Applications that support multiple versions accept one folder per line. Remote Desktop Manager then prompts you to select the version to use when launching the application.</p></td></tr><tr><td><strong>Browse</strong></td><td>Select the installation folder.</td></tr><tr><td><strong>Auto-Detect</strong></td><td>Search the computer for the application and fill in the installation path with the first valid folder found. A warning is displayed if the application cannot be found.</td></tr><tr><td><strong>Reset to default</strong></td><td>Clear the custom installation path so that Remote Desktop Manager uses the default path.</td></tr><tr><td><strong>Default path</strong></td><td>Read-only list of the folders where Remote Desktop Manager looks for the application when no installation path is set.</td></tr><tr><td><strong>Override default executable</strong></td><td>Available for some applications only. Use another executable file name than the default one, which is displayed in the field. Leave the field blank to use the default executable.</td></tr><tr><td><strong>Download</strong></td><td>Opens the application's download page in your web browser. Only displayed when a download page is known for the application.</td></tr></tbody></table>

A status line at the bottom of the tab confirms whether the configuration is valid:

* ***Application is ready***: The application was found. If it was found through the `PATH` environment variable instead of a default path, the folder is also displayed.
* ***Unable to find the application***: The folder does not exist, or the expected executable file is not in it.
* ***Please don't specify the executable name***: The installation path ends with an `.exe` file name. Enter the folder instead.

The ***Package manager*** tab is only displayed for applications that are available as a package. Select ***Winget*** or ***Chocolatey*** to manage the application with that package manager. The tab shows the ***Current version*** of the installed package, or ***Not installed***, and an ***Update available*** badge when a newer version exists.

<table><thead><tr><th width="250">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Install</strong></td><td>Install the application with the selected package manager. Displayed when the application is not installed.</td></tr><tr><td><strong>Update</strong></td><td>Update the application with the selected package manager. Displayed when an update is available.</td></tr><tr><td><strong>Uninstall</strong></td><td>Uninstall the application with the selected package manager, after confirmation.</td></tr><tr><td><strong>Open in UniGetUI</strong></td><td>Open the application in UniGetUI.</td></tr></tbody></table>

### See also

* [Application](https://docs.devolutions.net/rdm/ribbon-menu-bar/file/settings/application.md)
* [Use multiple versions of a third-party application](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/use-multiple-versions-of-a-third-party-application.md)
* [Portable USB](https://docs.devolutions.net/rdm/getting-started/installation/client/portable-usb.md)


---

# 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/ribbon-menu-bar/file/settings/application/paths.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.
