We use SC extensively—every day, all day—and it’s become an essential tool in our workflow. Unfortunately, the copy-and-paste functionality has recently started causing significant issues. While this problem is relatively new for us, discussions in the forums suggest it may have been a long-standing concern.
Is there a plan to address this issue? Or are we facing the possibility that SC may no longer meet our needs?
The on premise build is now available, version number is 26.1.25
Please note that prior to upgrading you should review this bulletin for important information regarding the upgrade: ScreenConnect 26.1 Azure code-signing certificate issue - ConnectWise
Note that while this build has resolved the crash issue we are still working on other clipboard issues:
- Unable to transfer copied folder
- Clipboard copy paste between 2 open guest clients fails
- Copy/Paste of special and non-english characters fails (workaround would be to copy to a file or use Send Keyboard Clipstrokes [only recommended for 100 or less characters])
Has it been confirmed that 26.1.24.9579 (Cloud-only release) fixes the Windows 7/2k8 compatibility and the copy-and-paste crashing?
Hi Colin and Doug,
Thank you all for the candid feedback and apologies on the delay of this response.
We recognize the need for timely, reliable updates.
Today, our official communication channels are:
Immediate actions in progress:
We recognize that these channels alone have not provided the level of visibility or timeliness you’re looking for.
Here is what you can expect going forward:ConnectWise Home will remain the primary source of truth for product-related updates, announcements, and known issues
We also understand that beyond providing patches, releases, updates and enhancements, bringing systems back to expected performance levels is critical. Our teams are actively working on this.
We appreciate your feedback as we work through this. Please continue to raise concerns and share input. We are listening and adjusting. Thank you.
-Jessica Koehn
Director, Brand Voice & Communities
ConnectWise
Sean,
Appreciate all your efforts. Is there any official channel that this stuff is being communicated over? There are a lot of partners dealing with major stability and productivity issues. I'm hoping I'm ignorant of some channel through which to get updates as to status, but at the moment I'm watching Discord, Reddit and watching the output stream and download sites. Surely there is a better and more official way?
Fully understand the need to fix the vulnerability - but unforutnately doing so has caused a lot of fallout. We need CW/SC management to communicate with us as to when baseline functionality and stability will be restored.
Thanks again
Colin, I echo this. Here and Reddit have been my primary sources of information, and I received the security alert from BleepingComputer.com. Unlike the issues last summer requiring the certificate change, I received zero communication from Connectwise regarding what is considered to be a vulnerability with a CVSS score of 9.0, and Sean, while I know that's not on your end, I'm unsure why I received no e-mails regarding this vulnerability or other notifications. Communication is key to us, and lack of communication does not go unnoticed either, be it for the actual vulnerabilities, or the issues in the product and the timeline to fix.
Sean, I appreciate your following up with me here, just as I appreciate when someone from Connectwise follows up with me on the ScreenConnect subreddit, but unless there's an official channel I'm not in that sent out notices, the communication regarding this is of real concern.
I was expecting a build yesterday; however, we ran into some testing issues. We have been working to resolve those and have tested 2 builds today. One more build is in the works and if final testing goes well, we will release tomorrow.
Thanks everyone for patience and understanding and rest assured that our team is literally working 24/7 to get this pushed.
Sean,
Appreciate all your efforts. Is there any official channel that this stuff is being communicated over? There are a lot of partners dealing with major stability and productivity issues. I'm hoping I'm ignorant of some channel through which to get updates as to status, but at the moment I'm watching Discord, Reddit and watching the output stream and download sites. Surely there is a better and more official way?
Fully understand the need to fix the vulnerability - but unforutnately doing so has caused a lot of fallout. We need CW/SC management to communicate with us as to when baseline functionality and stability will be restored.
Thanks again
I was expecting a build yesterday; however, we ran into some testing issues. We have been working to resolve those and have tested 2 builds today. One more build is in the works and if final testing goes well, we will release tomorrow.
Thanks everyone for patience and understanding and rest assured that our team is literally working 24/7 to get this pushed.
It's looking like Wednesday for on premise; I'll be sure to update this thread when it is available.
Sean,
Any update on this for an expected on-premise release date? The issues with 26.1 are killing us; sessions just crash in the middle of file transfers or the file transfers fail, and we're really losing productivity across our staff as they need to repeat tasks. I'm actually contemplating rolling us back to previous release despite the security risk, as this is preventing everyone from doing their job well.
To everyone in the cloud...has the latest cloud update resolved your issues?
The on premise build is now available, version number is 26.1.25
Please note that prior to upgrading you should review this bulletin for important information regarding the upgrade: ScreenConnect 26.1 Azure code-signing certificate issue - ConnectWise
Note that while this build has resolved the crash issue we are still working on other clipboard issues:
- Unable to transfer copied folder
- Clipboard copy paste between 2 open guest clients fails
- Copy/Paste of special and non-english characters fails (workaround would be to copy to a file or use Send Keyboard Clipstrokes [only recommended for 100 or less characters])
Sean,
FYI that we are using on-prem 26.1.25.9592 and are still "crashing" (locking up the local interface and having to task manager kill screenconnect) quite often when copying from the remote computer. We have placed a ticket and as of yesterday, the tech said this is still a known bug.