mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #1023] Clipboard synchronization suddenly stopped working (cannot copy text from remote to local) #1771
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#1771
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @1525337861 on GitHub (Nov 13, 2025).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/1023
Originally assigned to: @VShawn on GitHub.
Yesterday I was still able to copy text/code from the remote machine (including PyCharm) to my local computer through 1Remote without any issues.
However, starting from today, clipboard synchronization stopped working completely.
Even simple text copied from Notepad on the remote side cannot be pasted on the local side.
Local clipboard works normally (local-to-local copy/paste has no problem), so this issue seems specific to 1Remote’s remote-to-local clipboard channel.
No configuration changes were made on either machine. The issue appeared suddenly.
Environment:
Local OS: Windows
Remote OS: Windows
Application: 1Remote
Clipboard Sync: Enabled on both sides
Both machines restarted
Reconnecting the session does not fix the problem
Expected behavior:
Copying text from the remote machine should sync to the local clipboard normally (as it did yesterday).
Actual behavior:
Copying any text (e.g., from Notepad, PyCharm) on the remote machine does not appear in the local clipboard.
The paste operation on the local machine always results in empty content.
Additional notes:
Local clipboard is functioning correctly
The issue affects all applications on the remote side
Suspected that 1Remote clipboard synchronization channel fails to initialize
@VShawn commented on GitHub (Nov 13, 2025):
I occasionally encounter clipboard malfunctions when using RDP. After investigating, I found that the issue lies with the rdpclip.exe process on the server side. In such cases, simply killing the rdpclip.exe process from the Task Manager and then restarting it resolves the problem.
However, my situation differs from yours, as restarting the machines actually fixes the issue.
@Joly0 commented on GitHub (Nov 24, 2025):
Hey, i have updated to version 1.2.1 recently and now notice the same problem with the clipboard. What i also noticed is, that when clipboard bugs out, other things dont work either anymore, like proper mouse "transfer", so functions like click and hold or scrolling are no longer working, which is insanely annoying, if i am no longer able to scroll or resize windows in a remote rdp session.
@VShawn commented on GitHub (Nov 25, 2025):
@Joly0 Actually, I have no idea what causes the clipboard to stop working.
In the MSTSC.DLL provided by Microsoft, a single
rdpClient.AdvancedSettings9.RedirectClipboard = trueenables the clipboard feature, and this part of the code hasn’t changed since version 1.0.The occasional clipboard failure makes me think it’s related to the system. e.t. there was a period when my clipboard frequently stopped working, but it hasn’t happened for a long time now. During that time, I only kept the system’s automatic updates enabled and didn’t make any other changes.
@github-actions[bot] commented on GitHub (Dec 25, 2025):
This issue is stale because it has been open for 30 days with no activity.
@github-actions[bot] commented on GitHub (Jan 8, 2026):
This issue was closed because it has been inactive for 14 days since being marked as stale.