For the past seven days, hosts running on Windows 7 or older have been unreachable.
Specifically, the process is running, the service is active, and the agent responds to commands, but no image is displayed upon connection. This issue is caused by the latest host client being installed. If the new version is uninstalled and an older version is installed instead, the connection works normally and the image is displayed correctly.
Hi Todd,
I saw on the releases page there is now info about 26.3 showing.
One of the fixes is a .NET error on older Windows Servers with screen flickering (and artefacts i guess).
Maybe that version fixes your problems.
Hi,
We have an on-prem instance of ScreenConnect running version: 26.1.25.9592
We are still experiencing screen rendering issues on Windows Server 2008 R2 and Windows Server 2012 R2.
I think the last 2 revisions were supposed to address the issue, but I don't think either of them have fully fixed the issue.
Does anyone know if this is still being worked on by ConnectWise?
I installed the new 26.1.25.9592 version and still having problems with 2 windows xp machines. Anyone else?
We are on version 26.1.24.9579 and Win7 and XP are reachable again
I installed the new 26.1.25.9592 version and still having problems with 2 windows xp machines. Anyone else?
I think the fix is a cloud only release. All on Premise Customers still have 9573 as latest version. I dont understand why they dont release the fix for onpremise aswell. It's already 3 weeks since the release of this buggy version.
Where is the this revised build? I still see only the version which is not windows7 compatible in the downloads portal (9573)
It took one direct call to get the answer: push the revised build through the admin portal. I’m testing now and systems are coming back online.
The process should have been posted here from the start. Instead, customers were left waiting while production environments were impacted.
Clients expect clear guidance when a release breaks core functionality. This forum should be part of the solution, not another obstacle.
A fix is available for cloud and can be applied at any time.
A fix for on premises will be released next week.
You can track release status here:
ScreenConnect 26.1 / ScreenConnect
Please bear in mind that we do our best to support legacy, end of life operating systems, we do not guarantee they will work in all cases. (System requirements - ConnectWise)
You may want to update your site - how is this applied....?
A fix is available for cloud and can be applied at any time.
A fix for on premises will be released next week.
You can track release status here:
ScreenConnect 26.1 / ScreenConnect
Please bear in mind that we do our best to support legacy, end of life operating systems, we do not guarantee they will work in all cases. (System requirements - ConnectWise)
Thank you for the feedback. I don’t doubt that you are making an effort, but releasing an agent update as a 'stable version' that cuts off legacy operating systems—without any prior notice or warning—is unacceptable. Furthermore, the inability to provide a rollback as an emergency backup calls your processes into question. We will have to disable auto-updates and vet every release from now on, as it seems we customers are being used as beta testers.
Hi Todd,
I saw on the releases page there is now info about 26.3 showing.
One of the fixes is a .NET error on older Windows Servers with screen flickering (and artefacts i guess).
Maybe that version fixes your problems.
Hi Erik,
My apologies, I missed that. Thank you for mentioning it. I will check their releases page. I didn't think to check the releases page. I was just paying attention to the versions I have available for download.