"Server 2019" RDP Clipboard Copy/Paste or Copy/Replace results in file corruption

Question

On Windows Server 2019 Standard, using RDP Clipboard to copy/paste a file containing XML text and B64-encoded image data to a specific application directory results in loss of the text content of the file. For instance, one of the affected files was 328 KB in size originally, but only 310 KB after pasting into the directory.

This affects both copy/paste and copy/replace. It is possible that the files in that directory are in use by another process. However, copy/paste of the file to a user-specific directory (e.g. Desktop or Downloads), then transferring it to the desired folder path does not result in corruption.

Both of the servers involved in the RDP copy/paste are on the same domain network, with the same folder structure and permissions in the application directories.

There was a similar issue reported on Server 2008 R2 (https://social.technet.microsoft.com/Forums/windowsserver/en-US/41e6414c-b861-4da4-8575-47f1e3d6f530/corrupted-files-when-copying-through-remote-desktop-connection-from-server-2008-r2?forum=winserverTS).

Answer 1

Hello Miriam,

Thank you for your question and for reaching out with your question today.

Here are some steps you can take to troubleshoot and mitigate the issue:

1. Update and Patch: Ensure that both the source and destination servers have the latest Windows updates and patches installed. Microsoft often releases updates to address known issues and improve RDP functionality.
2. Antivirus and Security Software: Check if there are any antivirus or security software running on the servers that might be interfering with the file transfer process. Temporarily disable or adjust the settings of such software to see if it has any impact on the issue.
3. Network Connectivity: Verify the network connectivity between the two servers. Network interruptions or latency can sometimes cause file transfer issues. Ensure that the network connection is stable and not experiencing any problems.
4. File Locking: Confirm if the files in the specific application directory are being actively used or locked by another process. If a process has an exclusive lock on a file, it can prevent proper file copying and lead to corruption. Identify and close any processes that may be accessing the files in the destination directory.
5. File Permissions: Double-check the file and folder permissions in the specific application directory. Ensure that the user account used for RDP has the necessary permissions to copy files into that directory.
6. Use Alternate File Transfer Methods: If the issue persists, consider using alternative methods for transferring the files, such as FTP (File Transfer Protocol) or SCP (Secure Copy Protocol), which may provide more reliable file transfer compared to RDP Clipboard.
7. Test on Different Servers: If possible, try replicating the issue on different server environments to determine if it's specific to the server configuration or if it's a broader issue. This can help identify any server-specific settings or configurations that might be affecting the file transfer process.

It's worth mentioning that the issue you encountered on Server 2008 R2, as mentioned in the forum thread you shared, may not necessarily be the exact same issue you're facing on Windows Server 2019. However, some of the troubleshooting steps and considerations mentioned above can still be relevant in your case.

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.