If copy-paste is not working in Remote Desktop on Windows Server 2019, the most common fix is to restart the “rdpclip.exe” process, which handles clipboard sharing between the local computer and the remote session. To do this, open Task Manager on the remote server, find and end the rdpclip.exe process, then go to Run → type rdpclip → press Enter to restart it. This usually restores copy-paste functionality, but if the issue persists, you may need to check Remote Desktop Connection settings or Group Policy configurations.
Why Copy-Paste May Not Work in Windows Server 2019 RDP
RDP uses a feature called the “Clipboard Redirection” to allow copy-paste functionality between remote and local devices. When this feature fails, it can be due to various reasons:
- Clipboard Redirection is Disabled: The most common reason is that the clipboard redirection feature might be disabled in the RDP settings.
- RDP Configuration Issues: The RDP client or server configuration might be preventing clipboard operations.
- Group Policy Restrictions: Group Policy settings on the server may block clipboard redirection for security reasons.
- Process Issues: The rdpclip.exe process, responsible for handling clipboard operations in an RDP session, might not be functioning properly.
- Software Conflicts: Third-party software installed on the server or client machine can interfere with clipboard functionality.
Troubleshooting Steps for Windows Server 2019 RDP Copy Paste Issues
To resolve the issue, you can follow a systematic approach. This includes checking the clipboard settings, verifying configurations, restarting processes, and adjusting group policies.
1. Check the Clipboard Settings in Remote Desktop Client
Before troubleshooting on the server side, ensure that clipboard functionality is enabled in your RDP client.
- Open the Remote Desktop Connection client (usually named mstsc).
- Click on the Show Options button.
- Navigate to the Local Resources tab.
- Under Local devices & resources, ensure that Clipboard is checked.
If the Clipboard option is disabled, you won’t be able to use copy-paste functionality during your RDP session.
2. Restart the Clipboard Process on the Remote Server
Sometimes, restarting the clipboard process can resolve the issue. The process responsible for clipboard operations is rdpclip.exe. If this process stops or malfunctions, it can result in failed clipboard redirection.
- Log in to the Windows Server 2019 using RDP.
- The Open the Task Manager by pressing Ctrl + Shift + Esc.
- Look for the rdpclip.exe process under the Processes tab.
- If rdpclip.exe is running, right-click on it and select End Task.
- Go to the File menu in Task Manager and click Run new task.
- Type rdpclip.exe & press Enter to restart the process.
This should reinitialize the clipboard functionality for your current RDP session.
3. Verify Group Policy Settings
Group Policy can control clipboard redirection. If you’re an administrator, you can verify and adjust the settings using the Group Policy Management Console (GPMC).
- Press Windows + R and type gpedit.msc, then press Enter.
- Navigate to the following path:
Copy code Personal Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device & Resource Redirection - Look for the policy named Do not allow Clipboard redirection.
- If this policy is qualified, set it to Not Configured or Disabled.
After making these changes, either restart the server or run the command gpupdate /force in Command Prompt to apply the new policy settings.
4. Check Remote Desktop Session Host Configuration
The Remote Desktop Session Host Configuration tool can also restrict clipboard redirection.
- Open the Server Manager on the Windows Server 2019.
- Go to Remote Desktop Services and then click on Remote Desktop Session Host Configuration.
- Look for the RDP-Tcp connection under the Connections section.
- Right-click and choose Properties.
- Go to the Client Settings tab.
- Make sure the Clipboard box under Disable the following section is unchecked.
Apply the changes and restart the RDP session to see if the issue is resolved.
5. Use the Windows Registry to Enable Clipboard Redirection
If the above solutions don’t work, you use the Windows Registry Editor to ensure clipboard redirection enabled.
- Press Windows + R, type regedit, and press Enter to open the Registry Editor.
- Navigate to the following key:
Copy code HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services Look for a DWORD value named fDisableClipboardRedirection.
- If it exists & is set to 1, changing its value to 0.
- If it doesn’t exist, make a new DWORD value named fDisableClipboardRedirection and set its value to 0.
Close the Registry Editor & restart the server for changes to take effect.
6. Update or Reinstall RDP Client Software
If you’re still experiencing issues, consider updating your RDP client software to the latest version. Bugs in older versions can sometimes cause clipboard redirection problems.
- Visit the Microsoft Download Center to download the latest Remote Desktop Client.
- Install the new version and restart your system.
Alternatively, you can try uninstalling and reinstalling the RDP client software.
Additional Tips and Considerations
Check for Software Conflicts: Disable or uninstall third-party software that could interfere with clipboard functionality, such as security programs or clipboard managers.
Restart the Server: In some cases, a server restart can resolve temporary issues related to clipboard redirection.
Enable Drive Redirection: If you want to copy files instead of text, make sure drive redirection enabled in the RDP settings.
Conclusion
Clipboard redirection issues in RDP sessions on Windows Server 2019 can be frustrating, but they are typically straightforward to resolve with the right troubleshooting steps. By checking clipboard settings, restarting processes, and verifying configurations, you can restore copy-paste functionality and ensure a smooth RDP experience. If you continue to face problems, consider seeking support from the Microsoft community or consulting with your IT department for additional assistance.



