> 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/de/knowledge-base/troubleshooting-articles/slow-dashboard-after-application-update.md).

# Langsames Dashboard nach Anwendungsupdate

Beheben Sie ein langsames Dashboard nach der Aktualisierung von Remote Desktop Manager, indem Sie die neueste WebView2-Runtime installieren oder das eingebettete Edge-Überblicksfenster deaktivieren.

### Problem

Das Dashboard ist nach dem Upgrade von Remote Desktop Manager sehr langsam.

### Lösung 1

Installieren Sie die [neueste Version von Webview2](https://developer.microsoft.com/en-us/microsoft-edge/webview2/) manuell, indem Sie auf ***Als Administrator ausführen*** klicken. Stellen Sie sicher, dass sie für alle Benutzer installiert wird, nicht nur für den aktuellen Benutzer.

### Lösung 2

Gehen Sie in Remote Desktop Manager zu ***Datei*** – ***Einstellungen*** – ***Erweitert*** und deaktivieren Sie ***Eingebettetes Microsoft Edge für Überblicksfenster verwenden***. Speichern Sie und starten Sie Remote Desktop Manager neu.

Kontaktieren Sie uns bitte unter <service@devolutions.net>, wenn diese Lösungen Ihr Problem nicht beheben.


---

# 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/de/knowledge-base/troubleshooting-articles/slow-dashboard-after-application-update.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.