> 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/disable-udp-usage-in-remote-desktop-manager.md).

# Disable UDP usage in Remote Desktop Manager

Disable UDP transport in Remote Desktop Manager or via the registry to fix RDP sessions hanging during the log-off process.

Disabling UDP usage can sometimes resolve issues, notably those related to Remote Desktop Manager hanging during the log-off process of an RDP session. You can disable it via Remote Desktop Manager or via the registry.

### Disable UDP usage via Remote Desktop Manager

#### On all sessions

1. Run Remote Desktop Manager as an administrator.
2. In the ribbon, go to ***Tools – All tools***.
3. Select ***Local RDP/RemoteApp Manager*** from the tools list.
4. In the ***UDP Settings*** section, click ***Disable***. The status then shows ***UDP is Disabled***.

{% hint style="info" %}
This method sets the machine-wide `fClientDisableUDP` registry value under `HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client`. It requires administrator rights and also affects the Microsoft Remote Desktop client (mstsc) on this workstation. To turn UDP back on, click ***Enable*** in the same section.
{% endhint %}

#### On a per-session basis

1. In Remote Desktop Manager, ensure RDP API hooking is enabled in ***File – Settings – Entry types – Sessions – Remote Desktop (RDP)***, under ***API hooking – Enable API hooking***. Save your changes if applicable.
2. Select your RDP entry and go to its properties.
3. In the ***General*** section, go to the ***Advanced*** tab and set ***Disable UDP transport*** to ***Yes***.
4. Click ***Update*** to save your changes.

{% hint style="info" %}
***Disable UDP transport*** only applies when API hooking is enabled. The setting is unavailable when the entry uses FreeRDP.
{% endhint %}

### Disable UDP usage via the registry on the client workstation

1. In the Registry Editor, navigate to `HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client`, creating the `Client` key if it does not exist.
2. Create a DWORD named `fClientDisableUDP` and assign it a value of `1`.

{% hint style="info" %}
Consult this Microsoft article for more information on editing the registry: [Windows registry for advanced users](https://learn.microsoft.com/en-us/troubleshoot/windows-server/performance/windows-registry-advanced-users).
{% endhint %}

### See also

* [Devolutions Academy – Disable UDP usage in Remote Desktop Manager](https://academy.devolutions.net/student/activity/3291238-disable-udp-usage-in-remote-desktop-manager)


---

# 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/disable-udp-usage-in-remote-desktop-manager.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.