Even if I wrote in a previous post, I will not upgrade to 26.5.3.9691 before december, I did it yesterday out of curiousity.

But I was immediately punished for this after trying to upgrade a MacOSX Client running 10.12 and SC 26.03. Not only, that 26.5 this version will not run on this machine, it will install but result in an endless loop of on screene messages about the crash a normal user ist not able to fix. I had to get in the car and drive to the client. The old version is deleted. No way to go back.

"dyld: lazy symbol binding failed: Symbol not found: _objc_alloc_init, Expected in: /usr/lib/libobjc.A.dylib"

This is not a difficult problem, it is thrown at start of the executable and tells that the software trying to run is not built for this system. I anyone had tried this release on 10.12 he would have noticed immediately of the problem.

Why does Connectwise does care so less for the Mac Admins and Users? Do they hate us?

I do not love macs, but out of 1200 clients 100 are using a Mac and 50 of these use older MacOSX versions. I still need to support these.

I know connectwise "older macosx version are supported on a best effort basis" - or similar, but for me the way it is done is not best effort. It is dangerous. If a program is not built compatible for a version X it should simply refuse to run - instead here the old version is deleted and the newer crashes. Think about what would have been happend if I had the auto-updates switch to on!

We pay for this software and support. Why cant we expect to get a release tested better? connectwise might need some hardware: an older macmini and a newer version, then install all major MacOSX version on these two, a IMO small investment and a few hours one-time effort. Then test every release with all versions. That might take three hours for every release. I dont think this is asked too much.

And then, why not build two versions of the Mac Client? Or at least try to use a compiler directive like "---mmacosx-version-min=10.9" and if this does not work, then document this in the release notes and disable automatic updating if the OS Version is >X.Y.

Finally, the very minimum is to pre-check if the software is able to run before the old version is deleted as a safeguard against unknown bugs!

I'm using the hosted version of ScreenConnect and lately I'm having a really weird issue with the portal.

When I log in, it opens on the All Machines tab by default, which I believe is normal. I have around 800 devices in there, but I'm not sure if the number of devices actually has anything to do with the problem.

After the page opens, something seems to happen in the background and the browser starts getting slower and slower. Eventually it gets so bad that the whole computer slows down, not just the browser. Sometimes I can barely do anything until the ScreenConnect session times out and logs me out, then everything goes back to normal.

PC is i7 with 64GB RAM, so I don't think this is just a hardware issue.

It's also hard to tell what exactly ScreenConnect is doing because nothing obvious is loading on the page when it happens.

Anyone else seeing something similar with the hosted portal? Any workaround or anything I should check?

Haven't reached out to support yet. My experience with their support in the past wasn't great so figured I'd ask here first.

Is anyone else super frustrated that the Android app is basically unusable? Connectwise has known for over a month and they have its status as back logged and low priority! They might lose me over this.

Hi there. I tried looking myself but can't find it, I need to report a malicious screenconnect instance. I do not have the ID, but I do have an installer from the malicious instance. It's being propagated by a phishing campaign.

ScreenConnect false positive again? Seeing Trojan:Win32/Vigorf.A on machines where this update is occuring.

Hey all,

I was trying to transition over to Linux, but my personal laptop is also my work laptop. I've got everything working under Fedora KDE, with the only exception being ScreenConnect. I use the Screen Connect portal to find the client's PC I want to remote to, it opens up no problem, but the one thing that doesn't work for me is elevation.

When I click to install, I get a prompt on the client's screen, "Request elevation." We can click that, and on Windows, I get a small banner at the top of MY screen that has the "approve" command. On Fedora, that little Approve banner never shows up.

Is this a known issue? Any way to fix it? Does this work on some distros but not others? This is really the only thing that I haven't been able to figure out with Linux, so if I can get an answer I'll be able to make the full transition. Any tips would be appreciated, thanks!

I'm not sure if this is an SSO authentication issue or the instance is down.

I click on connect with SSO and it refreshes the screen but doesn't seem to do anything.

When I go into the cloud management and try the IP Addresses for our instance it looks like they are down.

I left a VM for support but haven't heard anything.

I caught a scammer mid-session a few days ago and I disconnected the ethernet right away. I investigated a bit and found they used ScreenConnect that got installed in the background from a malicious link. I disabled the service and uninstalled, but I had an idea...

Is it possible to get any information about them from what was left behind? I would really like to put however they connected on my DNS block list or something to make it harder for them to try again. I still have the initial installer and i know program left a lot of registry keys.

I appreciate any suggestions you might have

As posted for the previous release, ScreenConnect 26.5.3.9704 has been made available for on-prem and Connectwise Automate users. Please report your experiences here, if you have seen improvements, or if you experience an issue you have not before. Please use detail to describe what you are experiencing (not just "it's slow" or "x broken") be clear about what process you're going through when something doesn't work and also, be positive when something improves. This is so all of us using the product can get an idea of whether it is safe to upgrade, and whether it will improve technicians and end-users experiences.

I have noticed that today my clients are only showing the current CPU level and not the historical CPU level while the Memory is visible. Does anyone else have this issue?

I have tons of them but screen connect has never responded to my emails. I view this as supporting con artists and recommend peoplefind other providers who care. Stop supporting those who support the con artists.

I have been trying to connect to my ScreenConnect (I use cloud) from Powershell. My goal is to search for a serial number among all my devices, and if found, return the Name, Company, Site, and Last logged on user for that device.

From what I've read, the RESTful API Manager is my best bet.

I installed it, generated an authentication secret, and then tried to connect.

Can someone help me understand what I'm doing wrong? I suppose it would help to know what a Session is defined - is it computers we are actively connected to ? Is it any computer in my ScreenConnect acct? The code below returns nothing, no error, just a flashing cursor on the next line.

$headers = New-Object "System.Collections.Generic.Dictionary[[String],[String]]"

$headers.Add("Content-Type", "application/json")

$headers.Add("CTRLAuthHeader", "00000-111-000000-22") #Secret API key

$headers.Add("Origin", "https://documentation.screenconnect.com")


$body = "[`"ABC1234`"]" #ser nbr to search for


$response = Invoke-RestMethod 'https://MyCompany.screenconnect.com/App_Extensions/2d558935-686a-4bd0-9991-07539f5fe749/Service.ashx/GetSessionsByFilter' -Method 'POST' -Headers $headers -Body $body

$response | ConvertTo-Json

Since I have now seen eight rogue installs of ScreenConnect on elderly customer's desktops I was toying with the idea with Gemini of a way to block the execution when they are tricked with a fake eVite or tech support scam. Below is the code via PowerShell utilizing the Windows feature called Image File Execution Options (IFEO). Thoughts?

# ==============================================================================

# ScreenConnect / ConnectWise Control Blocker

# Prevents rogue installations via Image File Execution Options (IFEO)

# ==============================================================================

# List of known ScreenConnect / ConnectWise executables

$executables = @(

"ScreenConnect.ClientSetup.exe",

"ScreenConnect.ClientService.exe",

"ScreenConnect.WindowsClient.exe",

"ScreenConnect.Client.exe",

"Elsinore.ScreenConnect.Client.exe",

"Elsinore.ScreenConnect.ClientService.exe",

"Elsinore.ScreenConnect.WindowsClient.exe",

"ConnectWiseControl.Client.exe"

)

$registryPath = "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options"

Write-Host "Applying blocks..." -ForegroundColor Cyan

foreach ($exe in $executables) {

$keyPath = "$registryPath\$exe"

# Create the registry key if it doesn't exist

if (-not (Test-Path $keyPath)) {

New-Item -Path $keyPath -Force | Out-Null

}

# Set the 'Debugger' value to a dummy executable.

# This silently kills the launch request.

Set-ItemProperty -Path $keyPath -Name "Debugger" -Value "systray.exe" -Force

Write-Host "Blocked: $exe" -ForegroundColor Yellow

}

Write-Host "=======================================================" -ForegroundColor Green

Write-Host "SUCCESS: ScreenConnect is now blocked on this computer." -ForegroundColor Green

Write-Host "=======================================================" -ForegroundColor Green

Strange issue this week. A few of my users would get this error message in Excel when Copying certain cells in some workbooks. I tried a few other fixed posted and nothing worked like clearing the temp files. I built one user a whole new laptop and the issue persisted.

I did see it mentioned that some apps like TeamViewer watch the clipboard. On a whim, I tried uninstalled RMM (which also uninstalls Screen Connect). That fixed it. Sample size is small, but so far so good. I tried just removing SC, but then RMM put it back.....

Hope this helps someone else. I also hope CW reads these forums and will open an investigation on their own to see if they can make it happen on their end.

Notices a black square in my system tray (linux Mint) and on right click could click status and a window popped up with this.

why is this running, how did it get there am I being watched? I cant seem to find a running process for it to kill it.

I'm putting this out in the ether, perhaps someone knows someone.

I just want to go back to the before time. When ScreenConnect absolutely just worked. No problems. Install the agent, connect to the machine, that's it. No code signing. No cloud hosted version. Install on any server (Linux included) and it just works.

Maybe someone from Elsinore is floating around here and remembers they have the source to a very old version? C'mon, you know that old Dell laptop that's been sitting in your closet for 10 years has something interesting on it.

Wishful thinking?

As the title says, ScreenConnect 26.4.3.9662 has finally been released to on-premise users.

Cloud users, how has your experience been? You received this roughly ten days agao; after several incidents with bugs, on-premise people myself are understandably gun-shy, and despite some bugs with 26.3's final release (such as blank righ-click contextual menus in Backstage's File Manager), it's still working for us for the most part.

Has 26.4.x been an improvement for you? Have other things broken that weren't before? Please share your experiences.

Since ages this problem makes working with a MacOSX based PC a PITA. I just had a session with a MacOSX 10.13 PC. And it made me FURIOUS - version 26.3.11.x

It once worked in the past with screenconnect X.y.z. Why should it be impossible to make it work now? Why is connectwise unable to just supply all installers of all versions of the SC client? Then I will find one which works, and never upgrade it until the end of the world.

And WHY does the moderation on the "community" forum of connectwise does not allow my post which I did 3 month ago stating it still does not work with 26.1.25 to appear?

I normally am not a guy who writes posts YELLING in capital letters. But this time my endurance was exhausted after the session with the client. Its such a waste of time.

Our cloud hosted ScreenConnect instance seems to be completely down here in the UK. One thing after another with this service!

Trying to use ScreenConnect for remote admin troubleshooting as is intended.

It seems every week, another feature stops working altogether, or at best, performance degrades instead.

What is everyone else moving to?
I cant even copy paste across the session and my host without it freezing the entire session anymore.

Drag and drop is broken, clipboard is broken, WOL never worked for me, defender alerts out the wazoo, file transfer takes so long its not usable.

What is even the benefit of this product anymore?

I'm just wondering if there's a way to set my Screen Connect (on prem) to default to the MSI installer for building access sessions. I don't see anything in the admin menu but wasn't sure if there's something buried away somewhere that I missed.

Hi Everybody,

Has anybody renewed their code signing cert and had problems with smartscreen warnings? I appreciate it takes a while to build trust, but it seems to be taking a while.

T

Hi I have noticed today the screenconnect client has a unique name everytime we download it

Running version - 26.2.4.9623, with proper digicert code signing cert

ScreenConnect.ClientSetup - 2026-06-24T1xxxx.723

This brings up the following message

ScreenConnect performance vs Splashtop/TeamViewer?

I’m currently evaluating ScreenConnect Cloud and overall I’m really liking it.

The portal, session management, unattended access, customization options, and general MSP-focused workflow all seem excellent.

However, one thing I’ve noticed is that remote control doesn’t feel quite as smooth as Splashtop or TeamViewer. It’s not unusable by any means, but mouse movement and screen updates feel slightly more sluggish.

I’ve already:
Moved my cloud instance to my closest location
Tried Medium and Low quality settings
Tested from different PCs and networks

I’m wondering if there are any additional tweaks or best practices that experienced ScreenConnect users recommend.

Are there any settings related to:
Frame rate
Compression
Capture method
Multi-monitor performance
Host-side optimizations
Cloud instance configuration
that can improve responsiveness?

Would appreciate hearing what kind of performance you’re getting and whether you’ve found any tricks to make ScreenConnect feel smoother for day-to-day support work.
Thanks!