> 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/reinstall-remote-desktop-manager.md).

# Reinstall Remote Desktop Manager

Reinstall Remote Desktop Manager and restore your configuration files and data after backing them up beforehand.

{% hint style="success" %}
Before reinstalling Remote Desktop Manager, a backup will be required.
{% endhint %}

Refer to [Installation Overview](/rdm/getting-started/installation/client.md) for details on the installation of Remote Desktop Manager.

### Settings

After Remote Desktop Manager has been reinstalled on your computer, you need to copy your **RemoteDesktopManager.cfg**, **RemoteDesktopManager.enc**, and **RemoteDesktopManager.stv** (that you had backed up) to the **%LocalAppData%\Devolutions\RemoteDesktopManager** folder This is the default path. I f you have not installed with the default settings, please consult [Configuration File Location](/rdm/getting-started/installation/client/configuration-file-location.md) for instructions on locating your configuration folder.

### Data

If you have moved the file based workspace to another relative path, you will have to edit the workspace definitions to fix the paths.


---

# 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/reinstall-remote-desktop-manager.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.