rdpclip.exe) inside the remote session. If the clipboard still fails to synchronize across the connection—or if pasting works for text but fails for files—the issue is caused by disabled client redirection settings in mstsc.exe (or a saved .rdp file), a stalled Windows Explorer clipboard chain, or a Group Policy / Registry restriction (Do not allow Clipboard redirection or fDisableClip) on the remote host. These procedures apply to Windows 10 and Windows 11 (Pro, Enterprise, and Education editions acting as Remote Desktop hosts, and all editions acting as Remote Desktop clients), as well as Windows Server Remote Desktop Session Host environments.
Prerequisites and Scope
Before changing settings, identify whether the failure affects all clipboard data or only file transfers, and verify what access level you have on the remote computer:
- Standard user permissions on the remote PC: Sufficient to restart
rdpclip.exein your own session, restartexplorer.exe, and change client-sidemstsc.exeresource redirection settings. - Administrator permissions on the remote PC: Required to modify Local Group Policy (
gpedit.msc), editHKEY_LOCAL_MACHINEregistry keys, or override organizational policies. - Text vs. File copy behavior: If you can copy and paste plain text across the session but the Paste option is grayed out when copying files, verify both Clipboard and Drives redirection on the client, and check that the file is smaller than 2 GB. Microsoft Remote Desktop Services does not support copying files larger than 2 GB via clipboard redirection and fails silently when that threshold is exceeded.
Restart the Remote Desktop Clipboard Monitor (rdpclip.exe) on the Remote PC
The rdpclip.exe process runs inside the remote user session—not on the local client PC—and manages the virtual channel that synchronizes the clipboard between the two machines. If the clipboard chain locks up after a network drop, session reconnect, or large data copy, restarting rdpclip.exe resets the channel immediately without logging you out.
Using Task Manager (Windows 10 and Windows 11)
- Click inside your active Remote Desktop window so your input goes to the remote computer.
- Open Task Manager inside the remote session by pressing Ctrl + Shift + Esc, or by right-clicking the remote Start button and selecting Task Manager (in Windows 10, you can also right-click an empty area of the remote taskbar and select Task Manager).
- If Task Manager opens in compact view on Windows 10, click More details at the bottom of the window.
- Open the Details tab:
- Windows 11: Click the Details icon (the horizontal lines icon) in the left navigation rail.
- Windows 10: Click the Details tab along the top menu bar.
- Scroll through the alphabetical list and select rdpclip.exe. (You can also find it under the Processes tab listed as RDP Clipboard Monitor under Background processes.)
- End the process:
- Windows 11: Click the End task button in the top command bar, then click End process in the confirmation prompt.
- Windows 10: Click the End task button in the bottom-right corner, then click End process to confirm.
- Start a new instance of
rdpclip.exe: - Windows 11: Click the Run new task button in the top command bar.
- Windows 10: Click File in the top-left menu and select Run new task.
- In the Create new task dialog box, type
rdpclip.exeinto the Open field and click OK (do not check the administrative privileges box, asrdpclip.exemust run in your standard user session context).
Using Command Prompt or PowerShell (Faster Method)
If you prefer a single command inside the remote session to terminate any hung instance and launch a clean one:
- Inside the remote session, press Win + R (or right-click Start and select Run).
- Type
cmdand press Enter to open Command Prompt. - Run the following command to forcefully stop your session's
rdpclip.exeinstance and immediately restart it:
taskkill /F /IM rdpclip.exe & start rdpclip.exe - Confirm that
SUCCESS: The process "rdpclip.exe" with PID ... has been terminated.appears (or, if it had already crashed, that a new instance starts without an error dialog).
Verify Client-Side Clipboard and Drive Redirection (mstsc.exe)
If rdpclip.exe is not running at all when you connect, or restarting it does not allow clipboard data through, the local Remote Desktop Connection client may have disabled resource redirection for that connection.
Warning: Changing local resource redirection settings inmstsc.exerequires disconnecting and reconnecting your session. Save any unsaved work inside the remote session before disconnecting, or simply disconnect without signing out so your remote applications remain open when you reconnect.
- On your local PC, close the Remote Desktop window (click the X on the top connection bar to disconnect while leaving your remote programs running).
- Press Win + R on your local PC, type
mstsc.exe, and press Enter to open Remote Desktop Connection. - Click Show Options in the bottom-left corner of the dialog box.
- Select the Local Resources tab at the top.
- Under the Local devices and resources section at the bottom, verify that the Clipboard checkbox is checked.
- Tip: If Clipboard is already checked, uncheck it, click the General tab, click Save, return to Local Resources, re-check Clipboard, and save again. This clears corrupted redirection flags in cached connection profiles.
- If you also need to copy and paste files or folders (not just text and images), click the More... button under Local devices and resources.
- Check the Drives checkbox (or expand Drives and select at least one local drive) and click OK.
- Switch back to the General tab and click Save under Connection settings so your default
Default.rdpprofile retains the change. - If you launch your remote session from a saved
.rdpshortcut file on your desktop or in a folder, click Save As... and overwrite that specific.rdpfile—or open the.rdpfile in Notepad and verify thatredirectclipboard:i:1is set (a value of0disables the clipboard). - Click Connect to re-establish the session.
Check Group Policy Settings on the Remote Host
Even when the local client requests clipboard redirection, the remote Windows 10, Windows 11, or Windows Server host will reject it if Group Policy blocks clipboard or drive redirection.
- Inside the remote session, sign in with an account that has local Administrator privileges.
- Press Win + R, type
gpedit.msc, and press Enter to open the Local Group Policy Editor. (Note:gpedit.mscis included in Windows 10 and Windows 11 Pro, Enterprise, and Education editions; if you are troubleshooting from a Home client or prefer direct registry configuration, skip to the Registry section below.) - In the left pane, navigate to the following machine policy path:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection - In the right pane, locate and double-click Do not allow Clipboard redirection.
- Check the policy status:
- If it is set to Enabled, clipboard sharing is blocked across all RDP sessions to this machine.
- Change the setting to Disabled (which explicitly permits clipboard redirection) or Not Configured, then click Apply and OK.
- If file copy-and-paste is failing, also check Do not allow drive redirection in the same folder. Set it to Disabled or Not Configured and click OK.
- On Windows 11 (22H2 and later with current cumulative updates) and Windows Server 2022/2025, check two additional directional policies in the same
Device and Resource Redirectionfolder: - Restrict clipboard transfer from server to client
- Restrict clipboard transfer from client to server
Ensure both are set to Not Configured or Disabled unless your organization intentionally restricts copy direction or data formats (such as allowing plain text while blocking files or images). - Check the matching user-level policy path in the left pane to ensure a user policy is not overriding the machine setting:
User Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection
Verify that Do not allow Clipboard redirection is also Disabled or Not Configured here. - Open an elevated Command Prompt on the remote PC (right-click Start, select Terminal (Admin) on Windows 11 or Command Prompt (Admin) / Windows PowerShell (Admin) on Windows 10) and run:
gpupdate /force - Disconnect from the Remote Desktop session and reconnect (or sign out and sign back in to the remote session) for the updated session host policy to initialize the clipboard channel.
Alternate Method: Check and Fix Clipboard Redirection in the Registry
If you prefer not to use gpedit.msc or want to inspect the underlying registry values directly on the remote host, Windows stores Remote Desktop clipboard policies in two HKEY_LOCAL_MACHINE locations: the Group Policy key and the RDP-Tcp WinStation configuration key.
Warning: Editing the Windows Registry incorrectly can break Remote Desktop connectivity or system services. Before modifying values, back up the target key in Registry Editor by right-clicking the key folder in the left pane and selecting Export, or create a system restore point.
- On the remote PC, open an elevated Command Prompt or PowerShell window (Run as administrator).
- Query both the policy key and the active RDP-Tcp station key by running these two commands:
Code:reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDisableClip reg query "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v fDisableClip - Interpret the output:
- If
fDisableClipreturns0x1(1) in either location, clipboard redirection is disabled. - If
fDisableClipreturns0x0(0) orERROR: The system was unable to find the specified registry key or valueunder the Policies path, clipboard redirection is allowed. - To enable clipboard redirection in both locations, run the following commands in the elevated Command Prompt on the remote PC:
Code:reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDisableClip /t REG_DWORD /d 0 /f reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v fDisableClip /t REG_DWORD /d 0 /f - If file copy-and-paste is also blocked at the registry level, check and enable drive redirection (
fDisableCdm) as well:
Code:reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDisableCdm /t REG_DWORD /d 0 /f reg add "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" /v fDisableCdm /t REG_DWORD /d 0 /f - Disconnect and reconnect your Remote Desktop session (or sign out and back in) so the
RDP-Tcplistener applies the new0value to your session.
Rollback Steps for Policy and Registry Changes
If your security policy requires re-blocking clipboard redirection after completing a maintenance task:
- In Local Group Policy (
gpedit.msc): Return toComputer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection, set Do not allow Clipboard redirection back to Enabled, and rungpupdate /force. - In the Registry: Run
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services" /v fDisableClip /t REG_DWORD /d 1 /ffrom an elevated prompt on the remote host, or double-click the.regbackup file you exported prior to making changes.
Verification of Success
After restarting rdpclip.exe or reconnecting after a policy/client change, verify both directions and data types:
- Confirm
rdpclip.exeis running in your session: Open Command Prompt inside the remote session and run:
tasklist /FI "IMAGENAME eq rdpclip.exe"
Verify thatrdpclip.exeis listed with your current session ID (RDP-Tcp#...). - Test bidirectional plain text:
- On your local PC, open Notepad, type
Local-to-Remote Test, select it, and press Ctrl + C. - Inside the remote session, open Notepad and press Ctrl + V.
- Type
Remote-to-Local Testin the remote Notepad, press Ctrl + C, switch back to the local Notepad, and press Ctrl + V. - Test small file transfer: Create a small text file on your local desktop, right-click it and select Copy (or press Ctrl + C), right-click the remote desktop inside the RDP window, and confirm that Paste is active and transfers the file.
Troubleshooting Common Failure Modes
If the clipboard still fails after restarting rdpclip.exe and verifying policies, match your symptom to the specific cause below:
- Symptom: Text copies and pastes normally, but copying and pasting a large file does nothing and shows no error message.
- Cause: Microsoft Remote Desktop Services has a hard 2 GB file size limit for clipboard redirection (
Ctrl + C/Ctrl + V). Any single file exceeding 2 GB fails silently when pasted over the RDP clipboard channel. - Fix: Enable Drives under
mstsc.exe > Show Options > Local Resources > More...before connecting. Inside the remote session, open File Explorer, go to This PC, and open your redirected local drive (listed as<DriveLetter> on <LocalPCName>) to copy the file directly, or use a command-line tool inside the remote session targeting the\\tsclient\<DriveLetter>\path:
robocopy "\\tsclient\c\Users\YourName\Downloads" "C:\Temp" "LargeFile.iso" - Symptom: Restarting
rdpclip.exedoes not fix file pasting, or the clipboard freezes again immediately when using File Explorer. - Cause: The Windows shell (
explorer.exe) on either the remote PC or the local PC has a locked clipboard viewer chain. - Fix: Inside the remote session, open Task Manager, find Windows Explorer (
explorer.exe) under the Processes tab, right-click it, and select Restart. Then restartrdpclip.exeonce more. If the issue persists, also restart Windows Explorer on your local PC. - Symptom:
fDisableClipresets to1after runninggpupdate /forceor rebooting the remote PC. - Cause: The remote computer is joined to an Active Directory domain or managed by Microsoft Intune / Windows 365 / Azure Virtual Desktop, and a central policy is overwriting local settings.
- Fix: Run
gpresult /h C:\gporeport.htmlin an elevated Command Prompt on the remote machine and openC:\gporeport.htmlto identify which domain GPO sets Do not allow Clipboard redirection. In Azure Virtual Desktop or Windows 365 environments, the administrator must also enable clipboard redirection in the Host pool > RDP Properties > Device redirection tab in the Azure portal or Intune configuration profile. - Symptom: Clipboard breaks mid-session when a third-party clipboard manager, password manager, or security suite is running.
- Cause: Utilities that continuously poll or lock the Windows clipboard API—or endpoint protection tools blocking
rdpclip.exe—can interrupt the RDP virtual channel. - Fix: Check whether Windows Clipboard History (
Win + V) or a third-party clipboard utility is holding the clipboard open. Temporarily clear the local and remote clipboards by runningcmd /c "echo off | clip"on both machines, then restartrdpclip.exeon the remote host. If you use third-party application control or antivirus software on the remote host, verify thatC:\Windows\System32\rdpclip.exeis not blocked.