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

# Unsafe Google Chrome integration in Remote Desktop Manager Windows

Learn about security risks in the deprecated Google Chrome integration in Remote Desktop Manager Windows and why switching to Edge is recommended.

{% hint style="info" %}
This article applies only when the ***Force deprecated Chrome web browser extension*** option is enabled in ***File*** – ***Settings*** – ***Entry types*** – ***Sessions*** – ***Website***, or or when using a version of Remote Desktop Manager Windows earlier than 2024.3.
{% endhint %}

The integration of Google Chrome within Remote Desktop Manager Windows relies on a third-party component. Consequently, we do not control the update frequency of the Chromium versions utilized by this component.

The current integrated version of Chromium is 120, which suffers from several critical vulnerabilities due to the lack of the latest security patches.

For user safety, we issue a warning regarding the use of this integration. If you must use it for compatibility reasons, we strongly advise only browsing trusted websites. For optimal security, we recommend switching to the default browser powered by Microsoft Edge.

We are actively investigating options to transition to an open-source component for this integration. However, implementing this change will take some time.

We appreciate your understanding and patience as we work towards enhancing the security and functionality of 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/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.