> 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/knowledge-base-articles/unsafe-google-chrome-integration-in-remote-desktop-manager-windows.md).

# Usikker Google Chrome-integration i Remote Desktop Manager Windows

Få mere at vide om sikkerhedsrisici i den forældede Google Chrome-integration i Remote Desktop Manager Windows, og hvorfor det anbefales at skifte til Edge.

{% hint style="info" %}
Denne artikel gælder kun, når indstillingen ***Tving forældet Chrome-webbrowserudvidelse*** er aktiveret under ***Fil*** – ***Indstillinger*** – ***Posttyper*** – ***Sessioner*** – ***Websted***, eller når der bruges en version af Remote Desktop Manager Windows tidligere end 2024.3.
{% endhint %}

Integrationen af Google Chrome i Remote Desktop Manager Windows bygger på en tredjepartskomponent. Derfor styrer vi ikke opdateringshyppigheden for de Chromium-versioner, som denne komponent bruger.

Den aktuelle integrerede version af Chromium er 120, som har flere kritiske sårbarheder, fordi de nyeste sikkerhedsrettelser mangler.

Af hensyn til brugernes sikkerhed udsender vi en advarsel om brugen af denne integration. Hvis De er nødt til at bruge den af kompatibilitetshensyn, anbefaler vi på det kraftigste kun at besøge websteder, De har tillid til. For optimal sikkerhed anbefaler vi at skifte til standardbrowseren, der drives af Microsoft Edge.

Vi undersøger aktivt muligheder for at skifte til en open source-komponent til denne integration. Det tager dog noget tid at gennemføre denne ændring.

Vi sætter pris på Deres forståelse og tålmodighed, mens vi arbejder på at forbedre sikkerheden og funktionaliteten i Remote Desktop Manager Windows.


---

# 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/knowledge-base-articles/unsafe-google-chrome-integration-in-remote-desktop-manager-windows.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.