> 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/microsoft-rdp-licensing-protocol-error.md).

# Error del protocolo de licencias de Microsoft RDP

Los errores del protocolo de licencias de Microsoft RDP en Remote Desktop Manager se solucionan restableciendo la carpeta de configuración, cambiando los motores RDP o ajustando la configuración de NL

Cuando se conecta a una estación de trabajo remota, recibe uno de los errores siguientes.

```
The remote computer disconnected the session because of an error in the licensing protocol.
Please try connecting to the remote computer again or contact your server administrator.
```

```
The remote session was disconnected because license store creation failed with access denied.
Please run remote desktop client with elevated privileges.
```

### Solución 1

1. Cierre Remote Desktop Manager.
2. Navegue hasta **%localappdata%\Devolutions**.
3. Mueva la carpeta **RemoteDesktopManager** a su escritorio.
4. Reinicie Remote Desktop Manager.

### Solución 2

En ***Archivo – Configuración – Tipos – RDP***, cambie el motor RDP a ***RDP (FreeRDP Latest)***.

### Solución 3

Pruebe a marcar/desmarcar la opción ***NLA*** situada en la pestaña ***Conexión*** de las ***Propiedades*** de la sesión.

### Solución 4

En algunos casos, y a veces según el sistema operativo del host, la configuración ***CredSSP*** puede interferir. Cambie su valor en la pestaña ***Propiedades de la sesión – General – Avanzado***.

### Solución 5

Pruebe a marcar/desmarcar la opción ***Abrir consola*** y compruebe si el mensaje de error desaparece o sigue siendo el mismo en la configuración ***General*** de las ***Propiedades***.


---

# 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/microsoft-rdp-licensing-protocol-error.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.