> 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/third-party-clipboard-issues.md).

# Third-party clipboard issues

Third-party applications such as clipboard managers, remote support tools, screen recorders, accessibility software, and phone companion apps can interfere with Remote Desktop Manager’s clipboard features. Common issues include:

* Copied credentials disappearing before they can be pasted.
* The username pastes correctly, but the clipboard is empty when pasting the password.
* The clipboard is cleared immediately after copying.
* The wrong value is pasted. For example, the clipboard manager’s cached value instead of the live credential.

This article explains how to diagnose the issue and which solution applies to each scenario.

### Diagnose with the Clipboard diagnostic tool

Before changing any settings, use the ***Clipboard diagnostic*** tool to identify which process is consuming the clipboard:

1. Open the ***Help*** menu in Remote Desktop Manager.
2. Click on ***Clipboard diagnostic***.
3. Copy a credential using ***Copy username and password*** (or whichever action is failing).
4. In the ***Status*** tab, review the list of processes that read the clipboard.

Once the interfering process has been identified, apply the appropriate solution.

### Solutions

#### Clipboard managers (CLCL, Ditto, ClipX, etc.)

***Symptom:*** A clipboard manager consumes the `PasteOnce` sequence credentials can be pasted. Both the username and password are captured immediately, leaving nothing for the manual paste.

***Why this happens:*** Clipboard managers monitor the clipboard within milliseconds of any change. They ignore the private clipboard formats that Remote Desktop Manager uses to signal “do not capture this”, so the existing blocklist is ineffective against them.

***Solution (Remote Desktop Manager v2026.1 and later):*** No action required. Remote Desktop Manager automatically detects clipboard managers using time-delta classification:

* Any process that reads the clipboard within ***500 ms*** of a value being copied is classified as a clipboard manager.
* Remote Desktop Manager feeds it a copy of the value (so clipboard history remains intact) without affecting the flow.
* The paste action also receives the value and advances the sequence normally.

This works with multiple clipboard managers running simultaneously. No allowlist or blocklist configuration is required.

If auto-detection is not working (for example, on high-latency virtualized desktops), increase the threshold via the `ClipboardAutoReaderThresholdMs` NoUI option (see Advanced configuration).

***Solution (prior to v2026.1)***: Add the clipboard manager to the ***Blocklist*** in the ***Clipboard diagnostic*** tool. Note that this prevents the manager from capturing Remote Desktop Manager credentials in its history. See Blocklisting a process for instructions.

#### Blocklisting a process

***Symptom:*** A specific application is reading the clipboard and interfering, and it is not a clipboard manager (or Remote Desktop Manager is on an ealier version than 2026.1).

Known problematic applications:

| Application                                  | Notes                                      |
| -------------------------------------------- | ------------------------------------------ |
| ***Phone Link (PhoneExperienceHost.exe)***   | Synchronizes clipboard to mobile devices.  |
| ***Microsoft Azure Storage Explorer***       | Monitors clipboard for connection strings. |
| ***Citrix GoToAssist***                      | Remote support agent.                      |
| ***Microsoft Garage Mouse without Borders*** | Shares clipboard across machines.          |
| ***TeamViewer***                             | Clipboard synchronization feature.         |

1. Open ***Help*** – ***Clipboard diagnostic***.
2. Copy a credential to reproduce the issue.
3. In the ***Status*** tab, identify the interfering process.
4. Right-click it and select ***Add to blocklist***.

The rule is saved permanently. The process is silently denied access whenever Remote Desktop Manager controls the clipboard.

{% hint style="info" %}
Blocklisting prevents the application from reading Remote Desktop Manager-controlled clipboard content only. It does not affect the application’s normal operation outside of Remote Desktop Manager credential copies.
{% endhint %}

#### Add a delay (Chrome, Edge, and Electron apps)

***Symptom:*** The clipboard works sometimes but fails intermittently, particularly with Chrome-based browsers. The browser reads the clipboard multiple times internally before the user pastes.

1. Open ***Help – Clipboard diagnostic***.
2. Select the ***Configuration*** tab.
3. In the ***Delays*** section, add the browser process with a delay of ***150–200 ms***.
4. If the issue persists, increase the delay to ***500 ms***.

The delay makes Remote Desktop Manager wait before advancing the `PasteOnce` sequence, giving the browser time to complete its internal clipboard operations before the value changes.

#### Legacy clipboard method

***Symptom:*** Credentials copy incorrectly regardless of clipboard manager configuration, or a legacy application is fundamentally incompatible with Remote Desktop Manager’s default clipboard mechanism.

{% hint style="success" %}
The Clipboard copy method setting does not affect ***Copy username and password***. That action always uses the ***Paste once (Secure)*** mechanism because it is the only method that supports the sequential username-then-password paste flow. This solution applies to single-value copy actions only (for example, ***Copy password*** or ***Copy username***).
{% endhint %}

1. Go to ***File – Settings – Application – Clipboard – Advanced***.
2. Change ***Clipboard copy method*** from ***Default*** to ***Legacy***.

The legacy method uses a simpler clipboard mechanism that is compatible with a wider range of applications. Use this as a last resort if all the previous solutions do not resolve the issue.

### Advanced configuration

These options are not exposed in the UI. They must be set via XML configuration or the registry. Contact [Devolutions' support team](mailto:%20service@devolutions.net) if you need assistance applying them.

<table><thead><tr><th width="297">Option</th><th width="83.7999267578125">Type</th><th width="99.4000244140625">Default</th><th>When to use</th></tr></thead><tbody><tr><td><strong>ClipboardAutoReaderThresholdMs</strong></td><td>int</td><td><code>500</code></td><td>Increase (for example, to 1000) if clipboard managers are not being auto-detected on high-latency or virtualized desktops. Decrease only if users regularly paste within 500 ms of copying (unlikely).</td></tr><tr><td><em><strong>ClipboardSendSecureClipboardFormatsWithPasteOnceSecure</strong></em></td><td>bool</td><td><code>true</code></td><td>Set to false if a specific application breaks when private clipboard formats are present alongside the credential.</td></tr><tr><td><em><strong>ClipboardSendSecureClipboardFormatsWithLegacy</strong></em></td><td>bool</td><td><code>false</code></td><td>Set to true to include private formats when using the Legacy clipboard method.</td></tr><tr><td><em><strong>EnableClipboardViewerDisabler</strong></em></td><td>bool</td><td><code>false</code></td><td>Restores the pre-2024.3 clipboard viewer blocking behavior. Enable only if asked to by Devolutions' support team.</td></tr></tbody></table>

### Still having issues

If none of the solutions resolve the problem:

1. Open ***Help*** – ***Clipboard diagnostic***.
2. Reproduce the issue (copy a credential and attempt to paste it).
3. Click ***Send*** to transmit the diagnostic report to [Devolutions' support team](mailto:service@devolutions.net).

The report includes the list of processes that accessed the clipboard, the current blocklist and allowlist configuration, and relevant option values. Devolutions' support team can use this information to identify the interfering application and recommend the correct configuration for a specific environment.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/third-party-clipboard-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.