> 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/how-to-articles/clear-web-browser-cache.md).

# Ryd webbrowserens cache

Ryd webbrowserens cache i Remote Desktop Manager ved at omdøbe eller slette mapperne EO.WebBrowser.Cache og WebView2.Cache.

Ved at slette en mappe kan De rydde webbrowserens cache i programmappen for Remote Desktop Manager. Gå til ***Fil – Indstillinger – Avanceret***, og klik på fanen ***Information*** for at få adgang til programmappen. Hvis Remote Desktop Manager ligger i **Program Files**, bør De finde mapperne ***EO.WebBrowser.Cache*** og ***WebView2.Cache*** i **localappdata**.

1. Luk programmet Remote Desktop Manager.
2. Find mapperne ***EO.WebBrowser.Cache*** og ***WebView2.Cache*** i programmappen. Afhængigt af Deres version af Remote Desktop Manager har De muligvis kun én af mapperne.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Hvis De ikke finder nogen af mapperne, kan den mappe, hvor konfigurationsfilerne er gemt, være ændret ved hjælp af en fil af typen <strong>override.cfg</strong>. Se <a href="/rdm/da/getting-started/installation/client/configuration-file-location.md#override-the-default-path">Placering af konfigurationsfilen</a> for at få flere oplysninger.</p></div>
3. Omdøb eller slet mappen eller mapperne. Den bedste praksis er at omdøbe mapperne, da De i så fald ikke mister nogen data.
4. 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/how-to-articles/clear-web-browser-cache.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.