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

# Problemi di visualizzazione di Microsoft RDP

I problemi di visualizzazione di Microsoft RDP in Remote Desktop Manager, come sessioni sfocate, sfarfallio e barre delle applicazioni nascoste, si risolvono tramite le impostazioni della scheda Exper

### Il contenuto della sessione remota è sfocato

Deselezioni Persistent bitmap caching nella scheda Experience nelle proprietà della sessione RDP.

### Le sessioni sfarfallano, diventano nere o si riordinano in modo casuale durante il lavoro.

Abbiamo individuato in CA DSM Agent Suite per la gestione dei desktop la causa del problema per chi utilizza questo prodotto. L'agente di controllo remoto di questo prodotto sembra interferire con la GUI moderna di Remote Desktop Manager. Se arresta l'agente, il problema dovrebbe scomparire.

### La barra delle applicazioni remota sul sistema remoto è nascosta da quella della macchina locale.

Imposti la Screen sizing mode nelle proprietà della sessione RDP nella scheda 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/it/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.