RDP Files Paste but Text Does Not (or the Reverse)

Remote Desktop has two clipboard channels: text and files. Each has its own checkbox in the RDP client, its own format whitelist, and its own failure modes. When one works and the other does not — files paste but text does not, or text pastes but files do not — the cause is the channel split, not a single broken clipboard. This guide covers why the split exists, how to diagnose which channel is broken, and how to fix the broken channel without disabling the working one.

For the broader RDP clipboard discussion, see remote desktop copy-paste not working. For the related discussion of clipboard sync confusion with Phone Link, see phone link clipboard not working in 2026.

The two channels

RDP exposes two clipboard-related channels:

• Clipboard redirection — relays text, HTML, and bitmap formats between the local and remote clipboards. This is the channel that handles "copy a URL on the local machine, paste it into the remote browser." Controlled by the "Clipboard" checkbox under Local Resources in mstsc.exe, and by the redirectclipboard:i:value flag in the .rdp file.
• Drive redirection — exposes local drives as network shares inside the remote session. This is the channel that handles "copy a file on the local machine, paste it into the remote Explorer." Controlled by the "More" button under Local Resources → Local devices and resources, and by the drivestoredirect:s:value flag in the .rdp file.

The two channels are independent. Clipboard redirection can be on while drive redirection is off, and vice versa. Each channel can also fail independently of the other.

Symptom: files paste but text does not

If you can copy a file on the local machine and paste it into the remote Explorer, but you cannot copy text on the local machine and paste it into the remote Notepad, the cause is a broken clipboard channel with a working drive channel.

Diagnostic steps:

1. In the remote session, open File Explorer and confirm that the local drives are visible under "This PC" as \\tsclient\... network shares. If yes, drive redirection is working.
2. On the local machine, copy a short text string ("text test").
3. In the remote session, open Notepad and press Ctrl+V. If nothing pastes, the clipboard channel is broken.
4. Check the Local Resources → Clipboard checkbox in mstsc.exe. If it is off, turn it on and reconnect.
5. Check the redirectclipboard:i:value flag in the .rdp file. If it is 0, change it to 1 and reconnect.
6. On the remote machine, restart rdpclip.exe (Task Manager → Details → end rdpclip.exe → start it again).
7. Test text copy-paste again.

For most cases, step 4, 5, or 6 resolves the issue. If text still does not paste, the clipboard channel is blocked by Group Policy on the remote — see remote desktop copy-paste not working Step 5.

Symptom: text pastes but files do not

If you can copy text on the local machine and paste it into the remote Notepad, but you cannot copy a file on the local machine and paste it into the remote Explorer, the cause is a broken drive channel with a working clipboard channel.

Diagnostic steps:

1. On the local machine, copy a short text string. In the remote session, paste into Notepad. If the text appears, the clipboard channel is working.
2. On the local machine, copy a file (right-click a file in Explorer → Copy).
3. In the remote session, open File Explorer and press Ctrl+V. If the file does not paste, the drive channel is broken.
4. Check the Local Resources → More → Drives checkbox in mstsc.exe. If no drives are checked, check the drives you want to share and reconnect.
5. Check the drivestoredirect:s:value flag in the .rdp file. If it is empty or does not include the drives you want, add them.
6. In the remote session, open File Explorer → This PC. Look for \\tsclient\... entries. If they are not present, drive redirection is not working.
7. Test file copy-paste again.

The drivestoredirect flag uses a special syntax: drivestoredirect:s:* shares all drives; drivestoredirect:s:C shares only the C drive; drivestoredirect:s:C;D shares C and D. The flag is documented in the Microsoft RDP file reference.

For most cases, step 4 or 5 resolves the issue. If files still do not paste, drive redirection is blocked by Group Policy on the remote — the same policy that blocks clipboard redirection ("Do not allow drive redirection") is a separate setting under the same Group Policy path.

Why the split exists

The split exists because the two channels serve different purposes and have different security implications.

Clipboard redirection is low-risk: it relays small text and image content, which is the bread and butter of cross-session copy-paste. The risk is data exfiltration — an attacker who gains access to the remote session could copy data out via the clipboard — but the data is small and the exfiltration is visible.

Drive redirection is higher-risk: it exposes the entire local filesystem to the remote session. An attacker who gains access to the remote session could read or write any file on the local machine's shared drives. For this reason, drive redirection is more commonly disabled by Group Policy, and the disable is intentional.

The split lets administrators enable the low-risk channel (clipboard) while disabling the high-risk channel (drives). This is the configuration on most corporate jump hosts: text copy-paste works, file copy-paste does not, and the user is expected to use a side channel (a shared folder, a chat application) to move files.

Workarounds when files do not paste

If drive redirection is disabled and you need to move a file between local and remote, three workarounds exist:

• Side channel. Upload the file to a shared folder (OneDrive, a network share, a chat application) on the local machine, then download it on the remote. This is the IT-blessed pattern on most corporate networks.
• Copy the file path as text. If the file is on a network share accessible from both local and remote, copy the UNC path (e.g., \\server\share\file.txt) as text via the clipboard channel, then paste the path into the remote Explorer's address bar. The file does not actually move; you are just navigating to it.
• Email the file to yourself. This is clumsy but works on networks where email is allowed but file sharing is restricted. The file is attached to an email, sent, and downloaded on the other side.

None of these workarounds is as convenient as drive redirection, but they are the right answer when redirection is intentionally disabled.

Workarounds when text does not paste

If clipboard redirection is disabled and you need to move text between local and remote, the workarounds are similar:

• Side channel. Paste the text into a shared document (OneNote, a shared text file) on the local machine, then open the document on the remote.
• Type it. For short strings (a URL, a password), typing is faster than any workaround. For longer strings, this is impractical.
• Email the text to yourself. Same as for files.

For passwords specifically, the right answer is a password manager that is accessible from both local and remote, not clipboard copy-paste. See password managers and clipboard monitors: who should win for the discussion.

Phone Link and other sync confusions

A related "split-brain" clipboard problem occurs with Phone Link, which syncs the clipboard between a Windows PC and an Android phone. Phone Link uses a different sync mechanism than RDP, and the two can be confused — users expect Phone Link to behave like RDP, but it does not. For the full discussion, see phone link clipboard not working in 2026 and android to Windows clipboard sync failed.

The key distinction: RDP clipboard is a per-session relay between two Windows machines on the same network. Phone Link clipboard is a per-device sync between a Windows PC and an Android phone, mediated by Microsoft's cloud. The two have different failure modes and different fixes.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, is a local tool and does not directly interact with RDP's two clipboard channels. The shelf sees whatever is on the local clipboard, which includes items that RDP has relayed from the remote session via the clipboard channel. The shelf does not see items that are on the remote session's local drives, because drive redirection is a separate channel and the shelf does not access \\tsclient\... shares. For users who need to move files between local and remote, the right answer is to enable drive redirection (if permitted) or to use a side channel; a local clipboard shelf is not a substitute for either. For the full discussion of RDP and local shelves, see remote desktop fullscreen vs a local shelf.

A short summary

The split is the diagnostic. Knowing which channel is broken tells you which checkbox to check and which Group Policy to look for.

Related reading

• Phone Link Clipboard Not Working in 2026
• Android to Windows Clipboard Sync Failed
• 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 clipboard channel and its format whitelist
• Microsoft Learn — RDP file settings — official documentation of the .rdp file format, including the redirectclipboard and drivestoredirect flags
• Microsoft Support — Copy and paste between local and remote desktop — official guidance on enabling clipboard redirection in mstsc.exe
• Microsoft Learn — Drive redirection — official documentation of drive redirection and the tsclient share mechanism
• Microsoft Learn — RDP Group Policy settings — official reference for the "Do not allow clipboard redirection" and "Do not allow drive redirection" policies, which are separate settings

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