> 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

### 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.

<figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB6160.png" alt=""><figcaption></figcaption></figure>

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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/rdm/de/knowledge-base/troubleshooting-articles/slow-dashboard-after-application-update.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.