> 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/it/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

Risolva l'errore status 409 Wrong Key Hash in Remote Desktop Manager aggiornando alla versione minima richiesta di Devolutions Cloud.

L'errore status 409 "Wrong Key Hash - Please Update or contact support" può comparire durante la connessione a Devolutions Cloud in Remote Desktop Manager se la versione dell'applicazione non è aggiornata.

#### Soluzione

Aggiorni l'applicazione se è installata una versione precedente. Le versioni minime richieste sono:

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

Se l'errore persiste, contatti il nostro team di supporto all'indirizzo <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 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/it/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 `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.