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

# Actualice todas las aplicaciones y clientes de Duo antes del 2 de febrero de 2026 para evitar interrupciones del servicio

Actualice Remote Desktop Manager y Devolutions Server para mantener la compatibilidad con el nuevo paquete de fijación de CA de Duo y evitar interrupciones en la autenticación.

El 2 de febrero de 2026, Duo cambió a un nuevo paquete de fijación de autoridad de certificación (CA). Como resultado, los usuarios de Remote Desktop Manager y Devolutions Server que utilizan la autenticación de Duo pueden experimentar errores de compatibilidad.

{% hint style="info" %}
Consulte la [documentación de Duo](https://help.duo.com/s/article/9451?language=en_US) para obtener más detalles.
{% endhint %}

### Solución

Para garantizar la continuidad del servicio, actualice a las siguientes versiones:

* Remote Desktop Manager Windows: 2025.3.29.0 o posterior
* Remote Desktop Manager macOS: 2025.3.29.0 o posterior
* Devolutions Server: 2025.3.14.0 o posterior. Para permanecer en la versión 2025.2 de Devolutions Server, actualice a 2025.2.22.0 para obtener la corrección de Duo.

Al hacerlo, también se eliminará la advertencia que se muestra en la sección ***Reports*** – ***Unsupported Clients Log*** del portal de Duo.


---

# 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/es/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.