> 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/de/knowledge-base/troubleshooting-articles/status-409-wrong-key-hash-please-update-or-contact-support.md).

# Status 409 Wrong Key Hash - Please Update or contact support

Beheben Sie den Fehler „Status 409 Wrong Key Hash“ in Remote Desktop Manager, indem Sie auf die mindestens erforderliche Devolutions Cloud-Version aktualisieren.

Der Statusfehler 409 "Wrong Key Hash - Please Update or contact support" kann beim Verbinden mit Devolutions Cloud in Remote Desktop Manager auftreten, wenn die Anwendungsversion nicht aktuell ist.

#### Lösung

Aktualisieren Sie die Anwendung, wenn eine älteren Version installiert ist. Die mindestens erforderlichen Versionen sind:

* Devolutions Password Manager: 2026.2
* Remote Desktop Manager, Launcher, Devolutions.PowerShell: 2025.3

Wenn der Fehler weiterhin besteht, kontaktieren Sie unser Support-Team unter <service@devolutions.net>.


---

# 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 dynamically 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/de/knowledge-base/troubleshooting-articles/status-409-wrong-key-hash-please-update-or-contact-support.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 `build a script that syncs our docs to a CMS` 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.