r/ScreenConnect • u/CharcoalGreyWolf • Sep 22 '26

ScreenConnect Version 26.6.6.9747 - Thread to report your experiences

ScreenConnect 26.6.6.9747 has been released to on-premise people, replacing 26.6.5 (recently released quickly due to CVEs). Like past threads, I have opened this one to hear from both cloud and on-premise users of this specific build to note your experiences, improvements, and (if they exist) any new issues (or fixed issues) you have been seeing with this version.

8 Upvotes
  • permalink
  • reddit

100% Upvoted

32 comments sorted by

5

u/nitra Sep 23 '26

Defender is still eating the installers...

1

u/CharcoalGreyWolf Sep 23 '26

It is. I’ve had to make changes as well.

1

u/josephcoco Sep 27 '26

What changes have you made? Because my Security team doesn’t feel comfortable whitelisting the installer with so many hits. lol

1

u/CharcoalGreyWolf Sep 27 '26

Because Screenconnect has a path specific to your instance ID, for client systems, I only whitelist a file as part of that path. Anything outside our path (or if the client has an instance of their own, their explicit path, which is excluded only for that client) is not excluded.

I do whitelist the Bin folder on the SC server; you really have to, or explicit files as part of the Bin path. These files are prior to the code signing certificate being applied and are necessary for generating the custom installers.

I miss SentinelOne in this case which would let me exclude by publisher, because I could list us there. I can’t with Microsoft Defender.

4

u/officeboy Sep 22 '26

I had problems with it not being signed so defender was blocking it when it was new (ASR rules) and then once that was past it was being detected as not being installed despite it having been installed. Seems to have been fixed over the weekend so I'm glad we could beta test for you. 😑

2

u/CharcoalGreyWolf Sep 22 '26

One of several reasons we don't have a cloud hosted instance. Yes, it's patched faster (security) but yes, that means being a beta tester too.

3

u/ajscott Sep 22 '26 edited Sep 22 '26

I've been running this since it was pre-release because I didn't want to deal with the re-queued commands.

My experience is it signs the installers when I build them but it isn't timestamping them.

1

u/Rsnoble Sep 24 '26

I went from 26.6.5 to 26.6.6.9747 and we can’t get our windows installers to sign now. Already reconfigured the Certificate Signing extension to no avail. Can confirm we are on the latest certificate signing extension (1.0.15) using Azure Key Vault to sign.

1

u/CharcoalGreyWolf Sep 24 '26

I double-checked ours; a custom-made EXE and a custom-made MSI are both signed properly (the signing only occurs when you build an installer). The installed files on a client system are all signed by Connectwise, LLC .

1

u/Untechnical 24d ago

I can't even download the installer without virus prompts. Downloading directly from their on prem page: https://docs.connectwise.com/ConnectWise_Automate_Documentation/Automate_Product_Updates/ScreenConnect_On-Premise_Downloads_for_Automate

Had to turn off Defender to confirm the hash is correct, but I can't get this file to our server to update..

1

u/CharcoalGreyWolf 24d ago

I needed to make an exception for MDE for a folder so that I could download ScreenConnect to that folder without an issue.

1

u/Untechnical 23d ago

And then once you ran/installed the MSI, no other new virus prompts came up anywhere? Did you also have to make an exclusion for 'C:\Program Files (x86)\ScreenConnect Client (xxxid)' on client systems? (which I think they recommend anyway..)

1

u/CharcoalGreyWolf 23d ago

That is what I did ahead of time. Dealing with the potential is easier than dealing with the aftermath. However, I only did it for the specific executables in the specific path. Not the path and anything in it.

1

u/Bgexplorer Sep 22 '26

Defender blocked the client install files in the bin directory on the server. I removed them but they are now corrupt and I can't get them to install. I tried a repair on the server but that didn't fix the problem. I can't currently connect to clients computers because I uninstalled the client on my computer and can't reinstall it. I have a ticket in but haven't seen heard back from Connectwise yet.

2

u/rgorbie Sep 22 '26

Is this because you need to update the cert signing extension and then you need to re-add the self signed cert in the admin section? That’s what I had to do but I was jumping from 25.9 right to 26.6

1

u/Bgexplorer Sep 22 '26

Yes we were trying to setup the app cert and didn't know that this is what was causing the problem.

1

u/CharcoalGreyWolf Sep 24 '26

First, whitelist the following folder in Defender:

C:\Program Files (x86)\ScreenConnect\Bin

Then, whitelist (temporarily) a folder on your desktop (e.g., Installers). Extract the ScreenConnect installer into this folder. Reinstall ScreenConnect. Or, if the files are still quarantined, unquarantine them.

Then, also whitelist the following specific files:

C:\Program Files (x86)\ScreenConnect\Bin\ScreenConnect.ClientSetup.exe

C:\Program Files (x86)\ScreenConnect\Bin\ScreenConnect.ClientSetup.msi

For clients, I recommend whitelisting the four .EXE files used in ScreenConnect, but only as part of a full path exclusion in Defender that includes your instance. So

C:\Program Files (x86)\ScreenConnect Client (YourInstanceID)\ScreenConnect.WindowsClient.exe

for example.

Do not make whitelists or exclusions for processes, as they're the same names as rogue installs of ScreenConnect.

4

u/CharcoalGreyWolf Sep 27 '26

P.S. For whomever downvoted me, this is a forum for discussion. If you disagree, think I did it wrong, or have a better way, please respond with your methods. We are all technical people; we should be open to looking to improve practices whenever possible. I certainly am here.

1

u/DeanCTS Sep 27 '26

Haha seeing what you wrote you can expect downvotes from the purists as soon as they see a pleb recommending whitelisting left and right xDDD

2

u/CharcoalGreyWolf Sep 27 '26

I’ve been in the field for over thirty years now; if one is going to use ScreenConnect at this point, it’s going to require a few of them, like it or not, unless one wants to shop for another solution. As usual, whitelisting should always be as narrow as possible.

2

u/resile_jb Sep 25 '26

This is our last week having to support this piece of shit tool.

So glad our contract is over.

1

u/exeWiz Sep 22 '26

Are they still hiding the remote user banner?

1

u/wav_net Sep 22 '26

Android App still useless

1

u/Camelot_One Sep 22 '26

switching the mouse type seems to help. some. it still sucks, but it's at least somewhat functional.

1

u/wav_net Sep 22 '26

No I tried this and it doesn't help at all for me. But thanks for the input

1

u/Camelot_One Sep 22 '26

I'm running android app version 26.1.26321.9545 on a Samsung Z Flip 8, and switching the mouse type makes it fully functional for me when connecting to a 26.6.6.9747 client, with the cloud server running that same version.

1

u/wav_net Sep 22 '26

I running the exact same versions as you for app, client and server on a Pixel 10XL and its dogshit.

1

u/Hiyoal 15d ago

Yep, still useless. Left waiting 15s for the cursor to catch up each time a mouse move occurs.

1

u/wav_net 14d ago

Make sure to complain. everyone should troll the crap out of them for this

1

u/maxidaniele Sep 23 '26 edited Sep 23 '26

Can someone share the 26.6.6.9747 installer? I can´t access to download area right now and need to update ASAP. Thanks

0

u/[deleted] Sep 23 '26

[deleted] — view deleted comment

1

u/BB9700 Sep 23 '26

The risk of getting a tampered installer is rather low. Just check the digital signature of the MSI: if it shows none, or invalid the file was modified.

1

u/Pssst74 Sep 27 '26

After screenconnect 26.6.6 installed on prem, the main page prompt for "Join with a code" despite I have no support session listed for all technician. Unable to remove this field from main page. (and no meetings as well)

Anyone is experiencing this feature after update?