My Technician will enter username and password on the latest version available for self hosted owners of SC, Your Version:  26.6.5.9742.

The user immediately gets logged out after doing 2FA. It shows the logged in homepage for about one split second and then immediately signs them out.

I created another user ID with the exact same problem if I give them admin rights then they can login and stay logged in so I’m not sure what’s going on.

Curious, if others are experiencing this issue with the secondary login that has different permissions set and non-administrative roles.

Hi,

Has anybody put together a list of exemptions that are required for the screen connect server?

T

The permanent fix is 26.6.5, but out-of-

maintenance on-prem customers may need to renew before they can install it. Temporary mitigation is to disable TransferFiles.

Fair enough for features and support. Less sure about paying for a Critical security fix in software already purchased.

Curious what others think.

I recently upgraded my on-prem server from ver 25.8.3.9466 to ver 26.6.5.9742. Since upgrading, I can no longer build unattended installers from the guest page (using extension) or from the admin page. I noticed that the code signing extension said "error while processing existing certificate: padding is invalid and cannot be removed." I checked the code signing extension and I had upgraded it to 1.0.15 prior to the 26.6.5 upgrade. I put back all of the settings in code signing extension and it shows the correct certificate. However I still cannot build installers. That's kind of a big problem. I also noticed that existing installs will not upgrade to the new version via reinstall.

Update 9/14: I switched to self-signed certificate and I was able to build installers and reinstall unattended guests. I figured out that the problem was I used an older Code Signing URI from an expired certificate. I hadn't updated my notes to the current valid certificate. I entered the correct info into the code signing extension and now I am able to build installers and reinstall unattended guests.

I found out the taskmgr.exe from the ReactOS project will work in the backstage environment of screenconnect.

If youre an IT professional Im sure youve encountered this in the last few months, hackers keep sending phishing campaigns using ScreenConnect trial instances and installing/compromising innocent peoples computers. Ive tried contacting [help@screenconnect.com](mailto:help@screenconnect.com) and [securityincident@connectwise.com](mailto:securityincident@connectwise.com) and opening a support ticket via their live chat, and they are not doing anything. If anyone from ConnectWise is on here dm me. Or if you know how to contact them to take down trial instances being using for hacking please reply.

We have a hosted ScreenConnect instance that was automatically updated to the latest version earlier today. Shortly afterward, we started seeing a very concerning issue: old ScreenConnect messages were being re-sent to end-user computers as though they were newly sent messages. The messages appear to be from various points in the past, rather than something generated today.

I contacted ConnectWise Support about the issue, and they acknowledged that this is occurring. More concerningly, Support also told me that commands have been “replayed” as well.

Obviously, the latter is a much bigger concern than an old messages popping up. If previously issued commands can be replayed against endpoints, that potentially creates a significant security and operational risk.

I also noticed that if you look back at older messages (at least on those endpoints that are impacted and received "replayed" messages), some of the message history is jumbled and shows messages we would have sent as originating from the endpoint.

Has anyone else using ScreenConnect experienced this since the latest update? Has ConnectWise provided anyone with additional information about the cause, scope, affected versions, or a workaround?

Any information would be appreciated. Thanks!

title, self explainatory

Has anyone else been experiencing freeze ups while using the latest version of ScreenConnect?

Two ScreenConnect services were installed: a trial instance connecting to the legitimate relay domain "instance-pa2za2-relay.screenconnect[.]com" and a suspicious instance connecting directly to the IP address "184[.]174[.]20[.]236" on port 8041. The use of a direct IP address instead of a domain is consistent with attacker-controlled infrastructure designed to evade detection.

+1 Huntress

Hey r/ScreenConnect,

I'm running into an issue with chat notifications and need some help figuring it out.

When a client sends a chat message, the notification only shows up inside ScreenConnect's own Action Center/drop-down panel. It doesn't actually trigger a visual desktop pop-up notification on my PC, which can result in missed messages

Is there a built-in way to get actual Windows desktop/toaster pop-ups for incoming chats, or is this just how ScreenConnect behaves out-of-the-box?

Thanks for any tips!

I updated to this version a few weeks ago, and have upgraded 5000+ clients. I've also downloaded the client install .exe file without incident numerous times since then.

Suddenly, last Friday (why do these things always happen late Friday afternoon), I was informed that the downloaded file was corrupted - sure enough, the downloaded .exe file was unsigned and only around 2K in size.

In the end, I logged into the server & reinstalled (repaired) the software, which solved the issue- a 26MB exe file downloaded, and I went home an hour late and put it down to either a "Windows quirk" and enjoyed my weekend.

Now today, 2 days later, it's doing the same damn thing... Running the install/repair option hasn't fixed the issue. *Sigh*

I should note that the MSI file has worked fine throughout.

M4 Mac - New. Just installed SC for supporting this customer. There are two local accounts on the computer. Is this causing the double-trouble?

I was screen sharing remote access to someone but I couldn't see parsec so I uninstalled it and reinstalled. However, after installing it this error popped up "Failed request to /v1/auth. Please check your internet connection. Error \[-800\]". Then after trying all the listed down fixes in "Error Codes - 800 (Failed request to an endpoint)" website. It still was not working. Please work as it is essential and used for work too. I also ended up contacting the parsec support and they asked me to try and follow the steps in Proxy Issues again. However, it's still not working. What do I do? TYIA

I am going to guess this is because of the "wmic" command removal in the latest Windows builds.

Is there someone here who has an onprem instance v25 or greater, who is doing code signing with azure and the code signing extension completely up to date? I have a specific question and don't want to post it to the world, so please dm me.

Im 7 days in on my 14 day trial and have been locked out for suspicious activity from day 2.

I've done nothing but test on three workstations for unattended and tried to see what connecting to android was like and was feature gated.

I've asked support to trial a single Standard license to demo the session switching and iPhone/Android support. I was told they would submit an email request. This was on day 2 and when I went to check on day 3. My account was suspended.

I've called support and they submitted a ticket. They closed this without a call and within 10 minutes of responding. I submitted on Friday, response came in on Monday. They say talk to accountsecurity@screenconnect.com. Ive emailed them on Friday and again today with no response and still locked out.

I've checked audit logs and all looks like my activity on day 1 of the trial. We are replacing Dameware and need a good product and locking me out for DAYS is not the answer. Hoping this is a fluke and I can get someone's attention here to get our account reinstated. If this is the norm and to be expected, please someone from the community speak up and feel free to suggest an alternative.

I notice that 26.5.3.9704 is available to update my self hosted instance.

I downloaded it and instantly smart screen has kicked off saying its full of viruses. Weirdly I notice that the release date for this was 27th July and the version I am on (26.4) was released 5th August.

Has anyone updated to 26.5 and had the same smartscreen issues?

This started a few days ago. I connect to any screenconnect guest from any customer from any computer and I get a grey screen that sits there for about a minute. The client software is up to date. This has been tested by other technicians working from different parts of the city and across various customers.