> 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/update-all-duo-apps-and-clients-by-february-2-2026-to-avoid-service-disruption.md).

# Update all Duo apps and clients by February 2, 2026 to avoid service disruption

Update Remote Desktop Manager and Devolutions Server to stay compatible with Duo new CA pinning bundle and avoid authentication disruption.

On February 2, 2026, Duo switched to a new certificate authority (CA) pinning bundle. As a result, Remote Desktop Manager and Devolutions Server users leveraging Duo authentication may experience compatibility errors.

{% hint style="info" %}
See [Duo's documentation](https://help.duo.com/s/article/9451?language=en_US) for more details.
{% endhint %}

### Solution

To ensure service continuity, update to the following versions:

* Remote Desktop Manager Windows: 2025.3.29.0 or later
* Remote Desktop Manager macOS: 2025.3.29.0 or later
* Devolutions Server: 2025.3.14.0 or later. To stay on Devolutions Server version 2025.2, update to 2025.2.22.0 to get the Duo fix.

Doing so will also remove the warning displayed in the ***Reports*** – ***Unsupported Clients Log*** section of the Duo portal.


---

# 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/update-all-duo-apps-and-clients-by-february-2-2026-to-avoid-service-disruption.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.