Fix copy-paste not working in RDP by checking the local Remote Desktop setting, restarting the remote clipboard process, and removing policy blocks. These checks take about 10 minutes and cover Windows 10, Windows 11, and common Windows Server VPS sessions.
Prerequisites
- A Windows 10 or Windows 11 computer running the built-in Remote Desktop Connection client (
mstsc.exe). - A remote Windows 10, Windows 11, or Windows Server VPS with an active RDP session.
- Administrator access on the remote computer if you need to edit Local Group Policy or restart Remote Desktop Services. You only need access to your own session to restart
rdpclip.exe. - No extra RAM, disk space, domain, or firewall port is required for ordinary clipboard text transfer. File copy also needs client-drive redirection to be permitted.
- If you need a Windows desktop to manage remotely, VPSLake Windows RDP hosting provides a suitable server environment.
Step 1: Enable clipboard redirection in the RDP client
The local RDP client must request clipboard redirection when it creates the session; changing the option after you connect does not repair the current session.
On the computer you connect from, press Windows key + R, enter the command below, and select OK:
mstsc.exeIn Remote Desktop Connection, select Show Options → Local Resources. Under Local devices and resources, make sure Clipboard is checked. Select Connect, sign in again, and test a short line of plain text.
If you normally connect with a saved .rdp file, open it through mstsc.exe, change the same setting, and save the file before reconnecting. Microsoft lists mstsc.exe and its connection options in the Remote Desktop Connection command reference.
Step 2: Restart rdpclip.exe inside the remote session
The RDP clipboard process can become stuck even when the client setting is correct, so restarting it is the quickest server-side repair.
Inside the remote desktop, open Start → Windows PowerShell. You do not normally need Run as administrator when restarting the clipboard process belonging to your own session. Run:
taskkill.exe /IM rdpclip.exe /F
Start-Process -FilePath "$env:WINDIR\System32\rdpclip.exe"
Get-Process -Name rdpclip -ErrorAction SilentlyContinue | Select-Object Name,Id,PathThe first command may say that no process was found; that is harmless because the next command starts a fresh one. A successful check shows a running process similar to:
Name Id Path
---- -- ----
rdpclip 4820 C:\Windows\System32\rdpclip.exeTry copying plain text in both directions before changing system policy. If text now works, the fault was limited to the clipboard process in the earlier session.
Step 3: Remove a Group Policy block
Server policy overrides the checkbox in the RDP client, so a disabled client option cannot restore clipboard access when the host is configured to reject it.
On the remote computer, open the local policy editor:
gpedit.mscGo to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection. Open Do not allow Clipboard redirection and choose Disabled or Not Configured, then select Apply → OK.
Apply the policy and reconnect:
gpupdate /forceExpected output includes:
Updating policy...
Computer Policy update has completed successfully.
User Policy update has completed successfully.Microsoft’s TerminalServer policy reference identifies this setting and its fDisableClip policy value. If the server is joined to a domain, a domain policy or security baseline may apply again at the next refresh; the domain administrator must change that policy.
Step 4: Check Remote Desktop services
The clipboard process depends on a healthy RDP session, so confirm the core services are running before restarting the whole RDP service.
In an elevated PowerShell window on the remote computer, run:
Get-Service -Name TermService,UmRdpService | Format-Table Name,Status,StartTypeExpected output is:
Name Status StartType
---- ------ ---------
TermService Running Automatic
UmRdpService Running ManualIf either service is stopped, open Services → Remote Desktop Services or Remote Desktop Services UserMode Port Redirector, select Start, and reconnect. Do not restart TermService casually from the same RDP window because doing so will end the session.
If the previous steps fail, use the VPS control panel’s Virtualizor → VNC console or another local administrator session, then run:
Restart-Service -Name TermService -ForceWait for the RDP listener to return, reconnect from mstsc.exe, and repeat Step 2. A service restart can disconnect every active RDP session on the server.
Step 5: Allow drive redirection when files fail but text works
Text clipboard and file transfer are related but not identical; a policy that blocks client drives can leave text working while file copy fails.
In the local RDP client, open Show Options → Local Resources → More. Expand Drives, select the local drive that should be available, choose OK, and reconnect. On the server, check Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Device and Resource Redirection → Do not allow drive redirection. It must be Disabled or Not Configured if you need to copy files through a redirected drive.
Do not enable drive redirection just to solve a text-only problem. Redirected drives expose local files to the remote session, so allow only the drive and direction your work requires.
Verify RDP clipboard transfer
Use a harmless marker instead of a password or production data. First copy RDP-CLIPBOARD-TEST from the local computer and paste it into Notepad in the remote session. Then run this on the remote computer:
Set-Clipboard -Value "RDP-CLIPBOARD-TEST"
Get-ClipboardThe expected output is:
RDP-CLIPBOARD-TESTPaste into a local Notepad window to confirm the remote-to-local direction too. If you enabled drive redirection, copy a small non-sensitive text file through the selected redirected drive and open it on both sides. Both text directions and the file test should work without an additional firewall rule.
Troubleshooting
Clipboard is checked, but paste still does nothing
The existing session may have been created before the setting was enabled, or rdpclip.exe may be frozen. Disconnect fully rather than just closing a minimized window, reconnect, and repeat Step 2 inside the new session.
Text works, but copying files does not
The local drive is not redirected, or Do not allow drive redirection is enabled by policy. Select the needed drive under Local Resources → More, clear the blocking policy on a server you administer, and reconnect. For a managed server, ask the administrator whether file transfer is intentionally restricted.
gpedit.msc is not available or the setting changes back
Some client editions do not include the Local Group Policy Editor, and a domain policy can overwrite a local change. On a managed VPS, have an administrator inspect the applied domain policy; do not work around an intentional clipboard restriction by editing unrelated registry values.
Restarting Remote Desktop Services disconnected me
That is expected because TermService owns the RDP listener and active sessions can be terminated when it restarts. Reconnect after the service is running, or use the VPS control panel’s Virtualizor → VNC console if the RDP client cannot connect again.
FAQ
Does RDP clipboard redirection require a new firewall rule?
No. Clipboard data travels inside the established RDP connection, so repairing redirection does not require opening another inbound port. Keep the existing Windows Defender Firewall and RDP access restricted to the sources you trust.
Why does copy work from the remote server but not to it?
The client and server can apply different direction or content restrictions, especially on managed Windows 11 and Windows Server environments. Check the client Clipboard option first, then review both user and computer policies under Device and Resource Redirection.
Is rdpclip.exe a Windows service?
No. It is a per-session process that handles clipboard integration for the interactive RDP session. That is why ending and starting the process can fix the problem without rebooting Windows.
Is it safe to leave clipboard redirection enabled?
Clipboard redirection is convenient, but anything copied in one session can be exposed to the other side. Disable it for untrusted users or sensitive administrative servers, and use a controlled file-transfer method when you need stronger separation.
