> 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/fr/knowledge-base/troubleshooting-articles/access-violation-exception-error-in-rdp-sessions.md).

# Erreur d'exception de violation d'accès dans les sessions RDP

Corrigez l'erreur System.AccessViolationException dans les sessions RDP en désactivant l'accrochage d'API dans les paramètres de Remote Desktop Manager.

Lorsque vous tentez d'ouvrir une entrée de session RDP, vous pourriez rencontrer le message d'erreur "An unexpected error has occurred. Please check the application logs for more information." En consultant les journaux de l'application, l'erreur suivante s'affiche : System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

### Solution

Désactivez l'accrochage d'API RDP dans les paramètres de Remote Desktop Manager :

1. Allez dans ***Fichier – Paramètres – Types – Bureau à distance – Accrochage d'API***.
2. Dans la liste déroulante ***Activer l'accrochage d'API***, sélectionnez ***Désactivé***.
3. Redémarrez Remote Desktop Manager pour appliquer les changements.


---

# 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/fr/knowledge-base/troubleshooting-articles/access-violation-exception-error-in-rdp-sessions.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.