> 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/microsoft-rdp-display-issues.md).

# Problemas de visualización de Microsoft RDP

Los problemas de visualización de Microsoft RDP en Remote Desktop Manager, como sesiones borrosas, parpadeos y barras de tareas ocultas, se solucionan mediante los ajustes de la pestaña Experience.

### El contenido de la sesión remota se ve borroso

Desmarque Persistent bitmap caching en la pestaña Experience de las propiedades de su sesión RDP.

### Las sesiones parpadean, se ponen en negro o se reorganizan aleatoriamente mientras trabaja.

Hemos identificado que CA DSM Agent Suite para la gestión de escritorios es el causante en el caso de quienes utilizan este producto. El agente de control remoto de este producto parece interferir con la interfaz gráfica moderna de Remote Desktop Manager. Si detiene el agente, el problema debería desaparecer.

### La barra de tareas remota de su sistema remoto queda oculta por la de su máquina local.

Establezca el Screen sizing mode en las propiedades de su sesión RDP, en la pestaña Display.


---

# 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/microsoft-rdp-display-issues.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.