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

# Error de excepción de infracción de acceso en sesiones RDP

Corrija el error System.AccessViolationException en sesiones RDP desactivando el enlace de API (API hooking) en la configuración de Remote Desktop Manager.

Al intentar abrir una entrada de sesión RDP, puede aparecer el mensaje de error "An unexpected error has occurred. Please check the application logs for more information." Al consultar los registros de la aplicación, se muestra el siguiente error: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

### Solución

Desactive el enlace de API (API hooking) de RDP en la configuración de Remote Desktop Manager:

1. Vaya a ***Archivo – Configuración – Tipos – Escritorio remoto – API Hooking***.
2. En la lista desplegable ***Habilitar el enlace de API***, seleccione ***Desactivado***.
3. Reinicie Remote Desktop Manager para aplicar los cambios.


---

# 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/es/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.