> 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/passwords-not-working-for-devolutions-cloud-workspace-entries.md).

# Passwords not working for Devolutions Cloud workspace entries

Unreadable Devolutions Cloud entry passwords in Remote Desktop Manager, from a version-specific bug, are fixed by updating and running vault health repairs.

An issue affecting Remote Desktop Manager may render unreadable the passwords of certain Devolutions Cloud entries in RDM. While the issue only affects entries on which certain specific actions were performed, Devolutions recommends that organizations using Remote Desktop Manager with Devolutions Cloud as a workspace take these remedial actions:

* ​Update Remote Desktop Manager to the fixed version for your platform:
  * Windows: affected versions 2026.2.1 through 2026.2.12 — update to **2026.2.13** or later.
  * macOS: affected versions 2026.2.1 through 2026.2.3.1 — update to **2026.2.3.2** or later.
  * Linux: affected versions 2026.2.1 through 2026.2.1.3 — update to **2026.2.1.4** or later.
* ​Notify your team.

#### How to check if you are affected and attempt to fix entries

1. ​Open Devolutions Cloud web interface.
2. ​Head to ***Reports*** – ***Vault health***.
3. ​Select the vault you wish to check and set the ***Problem*** coloum’s filter to ***Password or sensitive key is invalid**.* The report should then list all the entries affected by the issue within the vault.
4. Click the ***Fix all*** button or the ***Fix*** button next to each entry to attempt automatic repair. Entries that could not be repaired will have to be reconfigured manually.
5. Repeat for all the vaults that could have been affected.


---

# 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/knowledge-base/troubleshooting-articles/passwords-not-working-for-devolutions-cloud-workspace-entries.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.