> 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/tabs-appear-blank-and-remote-desktop-manager-becomes-unresponsive.md).

# Tabs appear blank and Remote Desktop Manager becomes unresponsive

Fix blank tabs and unresponsiveness in Remote Desktop Manager after a display scaling change by adjusting the high DPI compatibility settings.

In Remote Desktop Manager tabs displaying embedded web content may appear blank if the display scaling changes while the application is running. In such cases the application may become unresponsive. The issue usually happens when disconnecting displays or using a docking station. This bug arises from limitations within [WebView2](https://crushonme.github.io/2023/05/23/Webview2-stop-working-after-system-DPI-changed), as Remote Desktop Manager does not currently use the per-monitor DPI awareness mode.

### Changing the high DPI settings

1. In the Windows File Explorer, navigate to ***%programfiles%\Devolutions\Remote Desktop Manager***.
2. Right-click on **RemoteDesktopManager.exe** and select ***Properties***.
3. Go to the ***Compatibility*** tab.
4. Click on ***Change high DPI settings***.
5. In the ***Program DPI*** section:
   1. Enable ***Use this setting to fix scaling problems for this program instead of the one in Settings***.
   2. Ensure the second setting is configured to ***I signed in to Windows***.
6. Click ***OK*** to save the changes.
7. Restart Remote Desktop Manager.


---

# 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/tabs-appear-blank-and-remote-desktop-manager-becomes-unresponsive.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.