> 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/troubleshooting-articles/invalid-certificate-error-when-updating-remote-desktop-manager.md).

# Invalid certificate error when updating Remote Desktop Manager

Fix the Invalid certificate error when updating Remote Desktop Manager from versions before 2023.2.34 by downloading the update manually.

Remote Desktop Manager shows an "Invalid certificate" error message when attempting to update from a version earlier than 2023.2.34.

As a security precaution, Remote Desktop Manager includes a list of accepted certificates to ensure the updates are distributed by Devolutions (a method named certificate pinning).

### Solution

To solve this issue, manually download ans install the update via your browser.

1. In the Remote Desktop Manager ribbon, go to ***Help – Check for updates***.
2. In the ***Update available*** tab that opens, click ***Download***, then ***Download update using your default browser***. You browser opens and the download should start.
3. When the download is complete, click on the downloaded file and follow the installation 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/troubleshooting-articles/invalid-certificate-error-when-updating-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.