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

# Faner vises tomme, og Remote Desktop Manager svarer ikke

Ret tomme faner og manglende svar i Remote Desktop Manager efter en ændring af skærmskaleringen ved at justere kompatibilitetsindstillingerne for høj DPI.

Faner i Remote Desktop Manager, der viser integreret webindhold, kan vises tomme, hvis skærmskaleringen ændres, mens programmet kører. I sådanne tilfælde kan programmet holde op med at svare. Problemet opstår typisk, når skærme frakobles, eller når der bruges en dockingstation. Fejlen skyldes begrænsninger i [WebView2](https://crushonme.github.io/2023/05/23/Webview2-stop-working-after-system-DPI-changed), da Remote Desktop Manager i øjeblikket ikke bruger tilstanden for DPI-bevidsthed pr. skærm.

### Ændring af indstillingerne for høj DPI

1. I Windows Stifinder skal De gå til ***%programfiles%\Devolutions\Remote Desktop Manager***.
2. Højreklik på **RemoteDesktopManager.exe**, og vælg ***Egenskaber***.
3. Gå til fanen ***Kompatibilitet***.
4. Klik på ***Skift indstillinger for høj DPI***.
5. I sektionen ***Program-DPI***:
   1. Aktivér ***Brug denne indstilling til at løse skaleringsproblemer for dette program i stedet for den i Indstillinger***.
   2. Sørg for, at den anden indstilling er sat til ***Jeg loggede på Windows***.
6. Klik på ***OK*** for at gemme ændringerne.
7. Genstart 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/da/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.