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

# Svuotare la cache del browser web

Svuoti la cache del browser web in Remote Desktop Manager rinominando o eliminando le cartelle EO.WebBrowser.Cache e WebView2.Cache.

Eliminando una cartella, è possibile svuotare la cache del browser web nella cartella dell'applicazione di Remote Desktop Manager. Vada su ***File – Impostazioni – Avanzate*** e clicchi sulla scheda ***Informazioni*** per accedere alla cartella dell'applicazione. Se il suo Remote Desktop Manager si trova in **Program Files**, dovrebbe trovare le cartelle ***EO.WebBrowser.Cache*** e ***WebView2.Cache*** in **localappdata**.

1. Chiuda l'applicazione Remote Desktop Manager.
2. Nella cartella dell'applicazione, individui le cartelle ***EO.WebBrowser.Cache*** e ***WebView2.Cache***. A seconda della versione di Remote Desktop Manager, potrebbe avere solo una di queste cartelle.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Se non trova nessuna di queste cartelle, la cartella in cui sono archiviati i file di configurazione potrebbe essere stata modificata tramite un file <strong>override.cfg</strong>. Consulti <a href="https://docs.devolutions.net/rdm/it/getting-started/installation/client/configuration-file-location.md#override-the-default-path">Posizione del file di configurazione</a> per maggiori informazioni.</p></div>
3. Rinomini o elimini la o le cartelle. La procedura consigliata è rinominare le cartelle, poiché in questo caso non si perde alcun dato.
4. Riavvii 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/it/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.
