Copying text or files between your computer and a Windows server over Remote Desktop normally just works — until one day it doesn’t. The clipboard is handled by a small helper process and a few settings on both ends; one of them is usually the culprit.

1. Check the client settings

In the Remote Desktop Connection client (mstsc) → Show Options → Local Resources:

  • Clipboard must be ticked.
  • For copying files, click More… and tick Drives (or specific drives). File copy-paste uses drive redirection behind the scenes.

Reconnect after changing them.

macOS (Windows App / Microsoft Remote Desktop): edit the PC → Devices & Audio → enable Clipboard; for file transfer, use Folders to share a local folder.

iOS / Android: enable clipboard in the connection’s settings; file copy is limited — use a shared folder or cloud storage.

2. Restart rdpclip.exe (the quick fix)

The clipboard is synchronised by rdpclip.exe, which sometimes hangs — especially after copying something large. On the server:

  1. Open Task Manager (Ctrl+Shift+Esc inside the session).
  2. Find RDP Clipboard Monitor (rdpclip.exe) → End task.
  3. File → Run new task → rdpclip.exe.

Or from PowerShell in the session:

Get-Process rdpclip -ErrorAction SilentlyContinue | Stop-Process -Force
Start-Process rdpclip.exe

This fixes most “it worked yesterday” cases without reconnecting.

3. Sign out and reconnect

If rdpclip won’t start or behaves oddly, sign out of the session completely (not just disconnect) and connect again. A fresh session starts a fresh clipboard helper. (On a trading VPS, close your platforms properly first — signing out ends them.)

4. Server-side policy may block it

Administrators (or hardening scripts) can disable redirection. Check Group Policy (gpedit.msc):

Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection:

  • Do not allow Clipboard redirection → should be Not configured or Disabled.
  • Do not allow drive redirection → same, if you need file copy.

Apply with gpupdate /force and reconnect.

Registry equivalents (on the server):

Get-ItemProperty 'HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services' -ErrorAction SilentlyContinue |
  Select-Object fDisableClip, fDisableCdm

fDisableClip = 1 blocks the clipboard; fDisableCdm = 1 blocks drive (file) redirection. Also check HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp for fDisableClip.

5. Client-side policy

Corporate laptops sometimes block clipboard redirection on the client via policy. If copy-paste fails to every server from one computer but works from another, ask your IT department.

6. Security software and RDP gateways

Some antivirus/endpoint tools and RD Gateway policies restrict clipboard or drive redirection for data-loss prevention. Check their logs or policies if the above settings look right.

Copying large files

Clipboard file copy over RDP is slow and fragile for big files, and can hang rdpclip. Better options:

  • Drive redirection: in the session, open This PC → your redirected local drive (C on YOUR-PC) and copy from there.
  • SFTP/SCP with the built-in OpenSSH server on Windows Server — see OpenSSH on Windows Server and scp.
  • Cloud storage or a download link.

See file transfer over RDP for all the options.

Checklist

  1. Clipboard (and Drives) ticked in the client’s Local Resources.
  2. Restart rdpclip.exe.
  3. Sign out and reconnect.
  4. Group Policy / registry: clipboard and drive redirection not disabled.
  5. Client-side policy or security software.
  6. Use drive redirection or SFTP for big files.

Related: connecting to a Windows VPS and RDP black screen fixes. Our Windows VPS plans come with full administrator access to adjust any of these settings.

  • RDP
  • Windows Server
  • Troubleshooting