You copy a password on your laptop, switch to the remote session, press Ctrl+V, and nothing happens. Or it worked fine all morning and then quietly stopped. Remote copy and paste is one of those features you never think about until it breaks, and when it breaks it feels random. It usually is not. There are only a handful of causes, and most take under a minute to clear once you know which one you are looking at.
The thing to understand is that a remote session has two separate clipboards, one on your local machine and one on the remote host. They are not magically shared. A small bridge keeps them in sync, and when paste fails, the bridge is either turned off or has fallen over. Everything below is about checking those two things in order.
First, the thirty-second fix: restart rdpclip
On Windows Remote Desktop (RDP), the bridge is a process called rdpclip.exe. It runs inside the remote session and shuttles the clipboard back and forth. It is also the single most common culprit. When it hangs, copy and paste dies even though everything else in the session keeps working, which is exactly why the failure feels so strange.
Restarting it inside the remote session fixes the majority of cases:
- Open Task Manager in the session with Ctrl+Shift+Esc.
- On the Details tab, find rdpclip.exe, select it, and choose End task.
- Open the Run box with Win+R, type rdpclip, and press Enter to start it again.
You will not be disconnected, and there is no harm in doing this. Try copying again straight away. If text now pastes, you are done. If it does not, the redirection setting is probably off, which is the next thing to check.
Check that clipboard redirection is actually enabled
If restarting rdpclip did nothing, the clipboard is most likely not being shared at all. RDP lets you decide which local resources reach the remote machine, and the clipboard is one of them. It is easy to have it switched off without realising, especially on a connection someone else set up.
In the Remote Desktop Connection app
- Open Remote Desktop Connection and click Show Options.
- Go to the Local Resources tab.
- Make sure Clipboard is ticked under “Local devices and resources”.
- For copying files as well as text, click More and tick your Drives too.
- Reconnect for the change to take effect. Settings only apply to new sessions, not the one you are in.
If you connect through a saved .rdp file, you can open it in a text editor and confirm the line redirectclipboard:i:1 is present. A value of 0 means the clipboard is disabled for that connection.
When the setting is greyed out
In a managed work environment, an administrator may have locked clipboard redirection through Group Policy on the host. That is a deliberate security choice, not a bug, and you will not be able to override it from your side. If copy and paste has never worked on a corporate machine and the checkbox does nothing, this is the likely reason, and the fix is a polite message to your IT team rather than anything you can change yourself.
Other remote tools: Citrix, VMware, AnyDesk and more
The same two-part logic applies everywhere, the bridge can be off, or it can be stuck. Only the names change.
- Citrix Workspace. Clipboard sharing is controlled by the host policy, but the local side can be blocked too. Reconnecting the session, or signing out and back in, clears most stuck states. Like RDP, file and text copying can be allowed separately.
- VMware (Workstation, Fusion, Horizon). Copy and paste needs VMware Tools (or open-vm-tools on Linux) installed and running in the guest. If paste stops, restarting the VMware Tools service inside the guest is the equivalent of the rdpclip restart. Shared clipboard also has to be enabled in the VM settings.
- AnyDesk and TeamViewer. Both have a clipboard permission you can toggle per session, sometimes for text and files separately. Check the permissions or security settings for the connection if paste is silently ignored.
If it still will not paste
A few less common causes are worth ruling out once the basics are covered.
- The clipboard is too large. Very big copies, like a huge spreadsheet selection or a high-resolution image, can overwhelm the redirection channel and fail where plain text works. Copy a smaller chunk to test.
- A second clipboard manager is interfering. Some clipboard tools and security agents hook into the clipboard and can clash with rdpclip. If you run one, try pausing it.
- Nested sessions. Remoting into a machine that is itself remoted into another adds a second bridge, and the clipboard often only survives one hop. Copy in stages if you have to go two levels deep.
- The host needs a real restart. If rdpclip refuses to behave after several restarts, signing out of the remote session fully (not just disconnecting) and back in gives it a clean start.
Why this keeps happening
Remote copy and paste is fragile by design. It depends on a tiny helper process staying healthy across an unstable network link, and on a chain of settings all being right at once. That is the same reason Universal Clipboard fails between Apple devices and why cross-device sync in general is finicky. When the clipboard is something a connection has to carry live, anything that disturbs the connection disturbs the clipboard.
The more reliable pattern is to stop treating the clipboard as a thing that lives on one machine. If you regularly move text between a local machine and a remote one, it is worth reading our guide to copying and pasting between your phone and computer, which covers the built-in tools and the cross-platform options. For sending the odd link or snippet without any setup at all, the Pushbullet alternatives roundup lists tools that push text to wherever you need it. The common thread is keeping a copy somewhere durable, rather than hoping a live bridge holds.