FIXED: copy paste on remote desktop not working

The Immediate Solution: Restarting rdpclip.exe

Okay, lets get straight to it. You are here because you tried to copy text or a file on your main PC, went to paste it into the Remote Desktop (RDP) window, and absolutely nothing happened. It is super annoying.

The problem is almost always a small program called rdpclip.exe. This is the process responsible for managing the shared clipboard between your local machine (the client) and the remote machine (the server/host). Sometimes, usually due to a network blip or just Windows being Windows, this process gets confused and stops talking to the clipboard chain.

Here is the step-by-step to fix it without rebooting the whole server:

1. Click inside your Remote Desktop window (the computer you are remoting INTO).
2. Open the Task Manager. You can do this by right-clicking the taskbar and selecting Task Manager, or by pressing Ctrl + Shift + Esc. Note: If you press Ctrl+Alt+Delete, it might trigger on your local PC instead, so stick to the other shortcuts.
3. Click on the Details tab (or the "Processes" tab in older Windows versions).
4. Scroll down until you find a process named rdpclip.exe.
5. Right-click on it and select End Task. Confirm it if it asks.
6. Now, don't close Task Manager yet. Click on File at the top left, and choose Run new task.
7. Type rdpclip.exe into the box and hit Enter.

That is it. Go try to copy and paste something now. It should work instantly.

I’ve used RDP for years to manage servers, and honestly, I have to do this at least once a week. It’s just one of those quirks of the protocol that Microsoft hasn't fully ironed out yet.

Solution 2: Check Your Connection Settings

If the restart method above didn't work, or if the process wasn't there to begin with, the issue might be your settings. Sometimes, we update the Remote Desktop Client or change a saved connection file, and the permissions get reset.

You need to make sure your computer is actually allowed to send clipboard data to the server. Here is how you check that.

Steps to enable Clipboard Redirection:

1. Disconnect from your current remote session. You have to be logged off (or at least disconnected) to change this.
2. Open the Remote Desktop Connection app on your local PC.
3. Before you hit Connect, click the little arrow or button that says Show Options at the bottom left.
4. Go to the Local Resources tab.
5. Look at the section labeled "Local devices and resources".
6. Make sure the Clipboard checkbox is ticked.

If that box was empty, that was your problem. Check it, save your connection settings on the General tab so you don't have to do this again, and reconnect.

Pro Tip regarding Drives: If you are trying to copy files (not just text) and it’s failing, you also need to click the "More..." button in that same section and check Drives. File copy-paste basically works by creating a temporary network tunnel to your local hard drive, so if "Drives" is disabled, file copy won't work even if text copy does.

Solution 3: Using the Command Prompt (The Ninja Way)

If you prefer using the keyboard or you have a stubborn interface, you can kill the process using the command line. This does the exact same thing as the Task Manager method but it can be faster if you have a lot of windows open.

Open the Command Prompt (CMD) or PowerShell inside your Remote Desktop session and run these two commands:

taskkill /IM rdpclip.exe /f

Wait a second for it to say "SUCCESS", and then type:

rdpclip.exe

This just kills the task forcefully and starts it up again. I usually keep a little batch file on my desktop with these commands so I can just double-click it whenever the clipboard stops working. It saves a lot of time.

Solution 4: Group Policy Settings (For Admin Environments)

If you are on a work computer or connecting to a corporate server, the "Clipboard" checkbox might be grayed out, or the fix just wont stick. This usually means a system administrator has set a Group Policy Object (GPO) to disable clipboard sharing for security reasons.

However, if you are the admin and it’s still not working, you might need to check the policy settings on the remote machine (the server).

Here is how to check the GPO:

1. On the remote computer, press Win + R, type gpedit.msc, and hit Enter.
2. Navigate through the file tree: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection.
3. Look for the setting called Do not allow Clipboard redirection.

If this is set to "Enabled," that’s your blocker. Change it to Disabled or Not Configured.

After you change this, you usually need to force the policy to update. Open a command prompt and type gpupdate /force. Then, log off and log back on. According to Microsoft documentation, GPO changes sometimes require a full session reset to take effect properly.

Why Does This Even Happen?

You might be wondering why this is such a common headache. It seems like such a basic function, right?

Basically, Windows uses a "Clipboard Viewer Chain." When you copy something on your local PC, RDP has to intercept that data, package it up, send it over the network, and inject it into the clipboard on the remote server. The rdpclip.exe process acts as the bridge.

The problem is that this bridge is surprisingly fragile. If your internet connection drops a few packets, or if you copy a massive file that times out the request, the chain breaks. The rdpclip.exe process assumes the connection is lost or corrupted and stops listening. That is why killing it and restarting it works-it forces it to re-establish the handshake with your local computer.

Advanced Troubleshooting: The Registry Fix

Alright, if you have tried the Task Manager fix, checked the settings, and looked at the Group Policy, and it is still broken, we have to go deeper. We are going into the Registry.

Warning: Be careful in the Registry. If you delete the wrong thing, you can mess up Windows. Maybe do a backup first.

Sometimes the specific RDP file configuration gets corrupted in the registry. Here is a fix that has worked for me on Windows Server 2016 and 2019 machines.

1. On the remote machine, open regedit.
2. Navigate to: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWds dpwd
3. Look for a value named fDisableClip. Make sure it is set to 0. (0 means "don't disable," which is a double negative, meaning "enable").
4. Next, navigate to: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp
5. Check for fDisableClip here as well. Ensure it is set to 0.

If you had to change these from 1 to 0, you will definitely need to restart the Remote Desktop service or just reboot the computer for it to take effect.

Copying Files vs. Copying Text

There is a distinct difference between copying "Text" and copying "Files."

If you can copy text (like a sentence from Notepad) but you cant copy a file (like a PDF from your desktop), the issue isn't rdpclip.exe. The issue is Drive Redirection.

When you copy a file (Ctrl+C) on your PC and paste it (Ctrl+V) onto the server, RDP doesn't actually "paste" the file immediately. It tells the server, "Hey, I have a file located at Client/C:/Users/Name/File.pdf, go get it."

If the server cannot see your local C: drive, the paste fails silently.

To fix this, go back to Solution 2 and ensure "Drives" is checked under the "More" button. Once connected, open "This PC" or "My Computer" on the remote server. You should see your local drives listed there as network locations (e.g., "C on DESKTOP-123"). If you don't see them, file copy paste will never work.

Network Stability and Bandwidth

Another thing people overlook is the network quality. RDP is smart; it tries to optimize your experience. If you are on a slow connection, RDP might prioritize showing you the screen updates (pixels) over background data transfer (clipboard).

If you are on a weak WiFi connection or a strict VPN, the clipboard channel is often the first thing to get dropped when the bandwidth gets tight.

A quick test: Try copying a very small word, like "test". If that works, but copying a large block of text or an image fails, your issue is likely network latency or packet loss, not a software bug. In this case, try lowering the "Experience" settings in your RDP client (turn off menu animations, desktop backgrounds, etc.) to free up bandwidth for the clipboard.

Alternative Tools

If RDP is just giving you a hard time and you need to move a file right now, don't bang your head against the wall. Use a workaround.

• Cloud Storage: Drop the file in Google Drive, Dropbox, or OneDrive. Open the browser on the remote server and download it. It’s often faster than RDP transfer anyway.
• Shared Network Drive: If you are on the same VPN, just map a network drive. It’s way more reliable for moving big files.
• Powershell Copy: If you are technical, you can use PowerShell Copy-Item over a PSSession, completely bypassing the RDP clipboard.

Frequently Asked Questions

Why does rdpclip.exe stop working?

It’s usually a memory management issue or a conflict in the clipboard chain. If another app on your local PC (like a password manager or a screenshot tool) is aggressively monitoring the clipboard, it can interfere with the RDP handshake, causing rdpclip.exe to crash or freeze silently.

Do I need to restart the server to fix this?

Rarely. 99% of the time, restarting the rdpclip.exe process as described in Solution 1 is enough. If you change Registry keys or Group Policy settings, then yes, a reboot or a log-off/log-on is usually required.

Is this a virus?

No, not at all. It looks suspicious because a system process is "acting up," but rdpclip.exe is a legitimate, built-in Windows component. It just happens to be a buggy one.

I fixed it but it broke again 10 minutes later. Why?

This implies something on your local machine is breaking the chain. Do you have a "Clipboard Manager" app installed? Or maybe a remote access tool like TeamViewer running at the same time? Try closing other background apps that might be accessing the clipboard.

Can I automate the fix?

Yes! You can create a simple batch file on the remote desktop. Open Notepad, paste the following lines, and save it as "FixClipboard.bat":

taskkill /f /im rdpclip.exe
start rdpclip.exe

Whenever copy-paste stops working, just double-click that file.

---

Hopefully, this saved you some frustration. I know the feeling of hitting Ctrl+V and staring at the screen waiting for something to happen is the absolute worst. If the rdpclip trick worked for you, you're good to go!