> 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/knowledge-base-articles/use-multiple-versions-of-a-third-party-application.md).

# Use multiple versions of a third-party application

Configure Remote Desktop Manager to launch multiple versions of a third-party application by listing several installation paths separated by semicolons.

If you have multiple different versions of an application installed on your workstation and wish to use both versions within Remote Desktop Manager, you can configure this as follows:

***When you configure your Application Installation Path*** In ***File – Settings – Application – Paths***, when configuring the ***Application installation path***, separate each path with a semicolon (;). Remote Desktop Manager will then prompt you with a selection list, allowing you to choose the desired version when launching the application.

Example: To specify two paths, such as `C:\Program Files\Appsv1` and `D:\Program Files\Appsv2`, enter them as follows:

`C:\Program Files\Appsv1;D:\Program Files\Appsv2`


---

# 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/knowledge-base-articles/use-multiple-versions-of-a-third-party-application.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.