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

# Erreur du protocole de licence Microsoft RDP

Les erreurs de protocole de licence Microsoft RDP dans Remote Desktop Manager se corrigent en réinitialisant le dossier de configuration, en changeant de moteur RDP ou en ajustant les paramètres NLA.

Lorsque vous vous connectez à un poste de travail distant, vous recevez l'une des erreurs ci-dessous.

```
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.
```

### Solution 1

1. Fermez Remote Desktop Manager.
2. Naviguez vers **%localappdata%\Devolutions**.
3. Déplacez le dossier **RemoteDesktopManager** vers votre bureau.
4. Redémarrez Remote Desktop Manager.

### Solution 2

Dans ***Fichier – Paramètres – Types – RDP***, changez le moteur RDP pour ***RDP (FreeRDP Latest)***.

### Solution 3

Essayez de cocher/décocher l'option ***NLA*** située sous l'onglet ***Connexion*** dans les ***Propriétés*** de la session.

### Solution 4

Dans certains cas, et parfois selon le système d'exploitation de l'hôte, le paramètre ***CredSSP*** peut interférer. Changez sa valeur dans l'onglet ***Propriétés de la session – Général – Avancé***.

### Solution 5

Essayez de cocher/décocher l'option ***Ouvrir la console*** et voyez si le message d'erreur disparaît ou demeure le même dans les paramètres ***Général*** des ***Propriétés***.


---

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