Remote Desktop Copy-Paste Not Working

Remote Desktop copy-paste breaks in well-understood ways. rdpclip.exe is stuck, clipboard redirection is off in the .rdp file, Group Policy is blocking the channel, the format is not on the redirector's whitelist, or drive redirection is being confused with clipboard redirection. This guide walks through the full diagnostic tree, from the simple fix to the obscure, with the goal of restoring text and file copy-paste between local and remote in under five minutes.

For related troubleshooting entries, see RDP files paste but text does not (or the reverse), fix a dead Win+V shortcut, and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11.

Step 1: Confirm the direction of failure

RDP copy-paste has two directions: local-to-remote and remote-to-local. Confirm which direction is broken before diagnosing further.

Steps:

1. On the local machine, copy a short text string ("local test").
2. In the RDP session, paste into Notepad. If "local test" appears, local-to-remote works.
3. In the RDP session, copy "remote test" from Notepad.
4. On the local machine, paste into Notepad. If "remote test" appears, remote-to-local works.

If both directions are broken, the channel is disabled or rdpclip is stuck. If only one direction is broken, the channel is partially working and the cause is likely a format or size issue.

Step 2: Restart rdpclip.exe on the remote

The most common cause of broken RDP copy-paste is a stuck rdpclip.exe on the remote machine. The process handles the remote side of the clipboard relay; when it gets stuck, neither direction works.

Steps (on the remote machine):

1. Open Task Manager → Details tab.
2. Find rdpclip.exe. Right-click → End task.
3. Open Start → type rdpclip → press Enter. (Or run rdpclip.exe from a command prompt.)
4. Test both directions of copy-paste again.

The command-line equivalent, run on the remote as the user:

taskkill /f /im rdpclip.exe
start rdpclip.exe

If copy-paste works after restarting rdpclip, the process was stuck. This is the single most common fix for RDP clipboard issues.

Step 3: Check the Local Resources clipboard checkbox

The RDP client (mstsc.exe) has a "Clipboard" checkbox under Local Resources. If the checkbox is off, clipboard redirection is disabled for the session, and no copy-paste works in either direction.

Steps (before connecting):

1. Open mstsc.exe (Start → type mstsc → Enter).
2. Click "Show Options."
3. Go to the Local Resources tab.
4. Under "Local devices and resources," confirm "Clipboard" is checked.
5. Connect to the remote machine and test both directions.

If the checkbox was off, this is the cause. The checkbox is per-session; if you connect from a different .rdp file or a different machine, check it again.

Step 4: Check the .rdp file

Saved .rdp files store the connection settings, including the clipboard redirection flag. The flag is redirectclipboard:i:value, where 1 is on and 0 is off. If the file has redirectclipboard:i:0, clipboard redirection is disabled for any session launched from that file.

Steps:

1. Right-click the .rdp file → Open with → Notepad.
2. Search for redirectclipboard.
3. If the value is 0, change it to 1.
4. Save the file and reconnect.

The same file may contain other redirection flags (redirectprinters, redirectsmartcards, redirectcomports, drivestoredirect) that control other RDP channels. For the full discussion of the file-paste-versus-text-paste split, see RDP files paste but text does not (or the reverse).

Step 5: Check Group Policy

On managed remote machines (corporate, school, locked-down jump hosts), Group Policy may disable clipboard redirection. The policy is "Do not allow clipboard redirection" under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection.

Steps (on the remote machine, if you have administrator access):

1. Open gpedit.msc.
2. Navigate to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection.
3. Check "Do not allow clipboard redirection."
4. If set to Enabled, set it to Disabled or Not Configured.
5. Run gpupdate /force in a command prompt.

If the machine is MDM-managed, the same policy may be set via MDM and gpedit.msc will not show it. Contact IT.

For corporate jump hosts, the policy may be intentional — disabling clipboard redirection is a security measure to prevent data exfiltration. In that case, the fix is not to re-enable redirection but to use a side channel (a shared folder, a chat application, a password manager) to move text.

Step 6: Check the format whitelist

RDP clipboard redirection supports a whitelist of formats. The default whitelist includes plain text, HTML, bitmap, and a handful of private Office formats. Files are not on the clipboard whitelist; they are redirected through drive redirection, which is a separate channel.

If you are trying to copy a file (right-click a file in Explorer → Copy, then paste in the remote session), the file does not go through the clipboard channel. To copy files between local and remote, you need drive redirection enabled (Local Resources → More → check the local drives you want to share).

For the full discussion of the file-versus-text split, see RDP files paste but text does not (or the reverse).

Step 7: Check the size limit

RDP clipboard redirection has a per-item size limit, separate from the Windows clipboard history's 4 MB cap. The RDP limit is configurable but defaults to a few MB. Large items (big screenshots, long logs) may fail to redirect without an error message; the copy appears to succeed on the source, but the paste on the target produces nothing.

To verify, copy a small text string. If the small string redirects but a large image does not, the size limit is the cause.

The fix is to copy smaller items, or to transfer large items via drive redirection (copy the file to a shared drive, then open it on the other side).

Step 8: Check for conflicting clipboard managers

A third-party clipboard manager on either the local or the remote machine can interfere with RDP clipboard redirection. The manager may consume the clipboard event before the redirector sees it, or it may write to the clipboard in a format the redirector does not whitelist.

Steps:

1. Quit any third-party clipboard manager on the local machine.
2. Quit any third-party clipboard manager on the remote machine (you may need to do this via Task Manager if the remote session is unresponsive to the tray).
3. Test both directions of copy-paste again.

If copy-paste works after quitting the managers, one of them was interfering. For the related discussion, see win+v vs a clipboard manager: honest split.

Step 9: Check for a stuck RDP channel

The RDP clipboard channel can become stuck without rdpclip.exe itself crashing. The channel is a virtual channel between the RDP client and the RDP server, and it can be reset by disconnecting and reconnecting the session.

Steps:

1. Disconnect the RDP session (do not sign out; just disconnect).
2. Wait 10 seconds.
3. Reconnect to the same session.
4. Test both directions of copy-paste again.

If copy-paste works after reconnecting, the channel was stuck. This is a transient issue and may recur; if it recurs frequently, the underlying cause is likely a network instability or an RDP client bug.

When to escalate

If none of the above steps restore RDP copy-paste, the cause is likely at the RDP server or the network level. Escalate to IT, with the following information:

• The direction of failure (local-to-remote, remote-to-local, or both).
• The format of the failed copy (text, image, file).
• The size of the failed copy.
• Whether the issue is reproducible or intermittent.
• The Windows version on both the local and remote machines.
• Whether Group Policy is in force on the remote.

IT can check the RDP server logs, the Group Policy result, and the network path in ways that are not available to the end user.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, is a local tool and does not directly interact with RDP clipboard redirection. The shelf sees whatever is on the local clipboard, which includes items that RDP has relayed from the remote session. The shelf cannot see items that are on the remote session's clipboard but have not been relayed — for example, if rdpclip is stuck or if redirection is disabled. For users who spend most of their day in RDP, the right answer is to run a clipboard manager inside the remote session, not to try to use a local shelf through the RDP boundary. See remote desktop fullscreen vs a local shelf for the full discussion.

A short summary

Work through in order. Stop at the first step that resolves the issue. For most outages, Step 2 or Step 3 is the fix.

Related reading

• RDP Files Paste but Text Does Not (or the Reverse)
• Phone Link Clipboard Not Working in 2026
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Learn — Remote Desktop Services clipboard redirection — official documentation of the RDP clipboard redirection channel and its format whitelist
• Microsoft Support — Copy and paste between local and remote desktop — official guidance on enabling clipboard redirection in mstsc.exe
• Microsoft Learn — RDP Group Policy settings — official reference for the "Do not allow clipboard redirection" policy and its scope
• Microsoft Learn — rdpclip.exe — Microsoft reference for the rdpclip process that handles clipboard relay on the remote side
• Microsoft Learn — RDP file settings — official documentation of the .rdp file format, including the redirectclipboard flag

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support