Fix Cut And Paste Problems With Remote Desktop


Remote Desktop is one of the best features of Windows. Unfortunately all the different Windows version of Remote Desktop seem to have a copy and paste bug. Pasting from the local machine to the remote machine in Remote Desktop will just randomly stop working.

I’ve been plagued with this problem for a long time but I never found a way to fix it. Now I found a simple method that works: On the remote machine kill the rdpclip.exe task and restart it. Pasting will immediately start working again!

Kill the rdpclip.exe task whichever way you want. You can use Task Manager, or you can use this one line command to kill and restart it automatically.

taskkill.exe /im rdpclip.exe & rdpclip.exe

  1. #1 by martin on May 28, 2008 - 10:35 am

    Thank you for this tip.

    regards

    ML

  2. #2 by bo on July 10, 2008 - 7:31 am

    nope. doesnt help

  3. #3 by Brad on October 30, 2008 - 4:33 am

    rdpclip task stop / restart doesn’t work for me either.

    SOLUTION:

    in my XP environments, if you end the remote desktop session and then restart it, the problem goes away and you can paste from the clipboard to a remote target app.

    see:

    http://kb.mozillazine.org/Clipboard_not_working

  4. #4 by ALbert on March 4, 2009 - 2:36 pm

    hmm…

    After first rdp login…

    copy only text to the clipboard and then
    paste it work for me.

  5. #5 by Simone Licini on May 22, 2009 - 12:38 am

    Very good solution!!!
    Thank you patrick, you solve me lot of trouble!!!

  6. #6 by tony on May 31, 2009 - 8:31 pm

    mad props, this was driving me crazy!

  7. #7 by BromleyJohn on June 10, 2009 - 7:14 am

    Excellent. Thanks.

  8. #8 by mark on September 9, 2009 - 4:56 am

    make sure the c drive is also checked in local resources

  9. #9 by chris on November 6, 2009 - 6:47 am

    Thsi did not work for me on server 2003. This problem wastes so much time I finally have to find a solution

  10. #10 by jen on December 17, 2009 - 11:13 am

    worked for me – thanks

  11. #11 by Eric on March 3, 2010 - 8:32 am

    When pasting from remote desktop to Excel I was having a similar problem in XP/Office 2007, I found the problem was with the clipboard in Excel. I closed Excel are reopened Excel to fix.

    Thanks.

  12. #12 by Peter on March 5, 2010 - 6:03 am

    Thank you saved so much time!

  13. #13 by Chuck on June 23, 2010 - 2:50 pm

    Thanks! It worked when killing rdpclip.exe via the task manager (i.e. Start -> Run -> “taskmgr’) and restarting it using the command line (i.e. Start -> Run -> “rdpclip.exe’)

  14. #14 by nram on July 12, 2010 - 7:54 am

    Wondeful. Saved my day.

  15. #15 by RJ on July 22, 2010 - 1:11 pm

    I found that using Remote Desktop copy/paste file function was extremely slow.

    Solution: click start>>run>> type %temp%
    delete all files . Do this on both pc’s and next thing you know you are back to normal.

  16. #16 by Harry Yeh on August 16, 2010 - 3:28 pm

    You are awesome! This has been driving me crazy on my computer! Bookmarking this site!

    Harry Yeh
    CEO / CTO
    Ooolalashop.com


    When you think thong think of Ooolalashop.com!

  17. #17 by LM on September 11, 2010 - 11:06 am

    Tried restarting RDPclip and it didn’t fix my problem. This is what fixed it:

    Finally I found this post that describes if the HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp registry key has the fDisableClip value set to 1, rdpclip.exe will terminate because clipboard mapping is disabled. I compared the registry and found that on the server I could successfully copy/paste to and from, this value was 0. On the problem server, this value was set to 1.

    found it on this website: http://thebackroomtech.com/2009/05/14/fix-rdpclip-exe-wont-run-on-windows-server-2003/

    Hope this help some of you!

  18. #18 by Sohel Rana on October 10, 2010 - 5:49 am

    Wow! it was really helpful. Thanks for sharing.

  19. #19 by Philip Murphy on December 15, 2010 - 1:59 pm

    Guys,

    Just in case Patrick’s solution doesn’t work… For me, the solution was to stop the IE6 Test Virtual Machine that I had running on the remote desktpo. Bizarre, I know, but thought I’d share in case some other poor chap has the same problem.

    Cheers,

    Philip

  20. #20 by alka on February 21, 2011 - 9:24 am

    THANKSSSS!!! This had been driving me crazy too. Soo helpful!!

  21. #21 by skj on March 9, 2011 - 12:28 pm

    #17’s solution worked like magic.

  22. #22 by Selun on March 16, 2011 - 7:21 am

    #13 worked for me. ty for starting this great discution anyway.

  23. #23 by nicolas on May 2, 2011 - 5:31 am

    thanks you save my day :p

  24. #24 by Francois on June 21, 2011 - 5:54 am

    Works sometime. Thanks for info.

  25. #25 by jens frandsen on July 6, 2011 - 5:36 am

    worked for me – thanks for sharing.

  26. #26 by Adnan on July 14, 2011 - 5:45 am

    On Windows 2003, the only way I could get copy/paste of files to work was to first enable drive mapping from the client side.

  27. #27 by pam on November 23, 2011 - 6:14 am

    i have an hp laptop with microsoft office 2007 operating system windows sytem vista home. the problem i am having is this (this is copied from an email i recieved from a friend thrying to fiqure out what was happening with my cut and paste code) when i cut and paste some code from amazon to my squidoo module that whatever program i am using to copy the code from the text file and paste it into the lens module is inserting quotation marks that are not really quotation marks(this happens with word or notepad and potentially somde other program s when pasted directly from one source to another) or some other character that is not really what it appears to be. Can someone help me fix this problem?

  28. #28 by Walker Rowe on January 24, 2012 - 7:46 am

    My experience in Windows 2008 is that killing the task does not work neither does restarting remote desktop (XP) session. When you start rdpclip.exe from the command line it starts to as a run away task consuming increasing amounts of memory. So for me this issue remains unsolved. Even restarting the entire Windows 2008 server does not fix the problem.

(will not be published)