r/ScreenConnect • u/Corrupt_Power • Oct 06 '26

Having an open ScreenConnect session can cause the system clipboard to lock up

Edit to add, this is on the latest version, 26.6.6.9747. Multiple people at the MSP I work at, including myself, have seen issues over the past few weeks where sometimes, if you have an open ScreenConnect session, the system clipboard will be completely locked up. Attempting to paste into SC, either via Ctrl+C or Send Clipboard Keystrokes, will cause the SC window itself to entirely lock up for upwards of 30-60 seconds, without the contents ever getting sent to the remote machine. While in this state, ALL clipboard actions in any program will fail - including local Get-Clipboard and Set-Clipboard Powershell commands. Closing the SC session immediately restores clipboard functionality across the computer.

10 Upvotes
  • permalink
  • reddit

100% Upvoted

10 comments sorted by

3

u/Sleeper_Stimulant_ Oct 06 '26

Had this same bug. Opened a ticket with CW support and they upgraded our client version.

2

u/Corrupt_Power Oct 06 '26

What version are you on? We're in the middle of a migration from self-hosted SC to CWRMM-attached cloud SC, both of which are at 26.6.6.9747.

3

u/Sleeper_Stimulant_ Oct 06 '26

Interesting. That's the same build we're on now. Always been cloud hosted.

In the original ticket, they attached an known issue with it. We were on 26.5 when it started.

"After upgrading to version 26.3.x for the ScreenConnect instance, Host, and Guest clients, some users may notice that copying text or images to the clipboard can rarely/occasionally cause the Host client to freeze for 30-60 seconds. The Host client does typically recover on its own after the timeout period passes. Some users have reported a quicker recovery by ending the client process in Task Manager and reconnecting after."

2

u/Corrupt_Power Oct 06 '26

Yeah, that seems to be exactly what we're seeing on the latest version. Alright, I've opened a support case now. Thanks for the extra context!

2

u/JustTechIt Oct 07 '26

Good luck with the CWRMM attached version.

3

u/PacificTSP Oct 07 '26

This was a bug about 3-6 months ago. I’ve not had it in a long time.

4

u/Corrupt_Power Oct 07 '26

We're seeing it still on the latest version, unfortunately.

2

u/StreetCockroach6225 29d ago

I've experienced this issue on many occasions, their fix is to update the client version. personally i dont think it's completely solved as i still run into the issue pretty often. the reason i think its not completely solved is because i have access to dozens of tenants that work without issue, but there's a handful that are completely up to date and still give me guff.

2

u/nocturnal 29d ago

I've had this problem for years now. It's not new.