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

# Microsoft RDP licensing protocol error

Microsoft RDP licensing protocol errors in Remote Desktop Manager are fixed by resetting the config folder, switching RDP engines, or adjusting NLA settings.

When you connect to a remote workstation, you receive one of the errors below.

```
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. Close Remote Desktop Manager.
2. Navigate to **%localappdata%\Devolutions**.
3. Move the **RemoteDesktopManager** folder to your desktop.
4. Restart Remote Desktop Manager.

### Solution 2

In ***File – Settings – Types – RDP*** change the RDP engine to ***RDP (FreeRDP Latest)***.

### Solution 3

Try to check/uncheck the ***NLA*** option located under the ***Connection*** tab in the ***Properties*** of the session.

### Solution 4

In some cases, and sometimes depending on the host OS, the ***CredSSP*** setting may interfere. Change its value in ***Session properties – General – Advanced*** Tab.

### Solution 5

Try to check/uncheck the ***Open Console*** option and see if the error message disappear or is still the same in the ***General*** settings of the ***Properties***.


---

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