New update for ScreenConnect removed the option to hide top bar/banner. This is not acceptable since we have 100s of Point Of Sale devices that are touchscreen and not being able to hide is causing tons of issues
Expend sometime with CW Chat and they didn't know about the change, had to spell it out for them, keep telling me to Hide the option even though I told them 3 times in chat it's permanently disable
We have made significant changes to this implementation in our upcoming 25.7 release.
-The banner is now only visible on the Guest side
-The banner does not interfere with the host; if something is behind the banner, the host will not be blocked from clicking through
Upcoming changes will add a Dismiss button so the guest can hide the banner if they choose, and we will improve discovery that the banner can be moved.
We are planning some changes in this area, but moving forward, this banner will be present whenever a host is connected to a user session.
The option we are exploring is to draw it on a layer where it's not visibile to the host. Stay tuned for more on this.
Do we have an official response yet? I feel like the general consensus is to AT LEAST provide us with more options if you're going to force banners and icons that we can't even change.
Me and my team are running into separate issues with the bar interacting poorly with the Microsoft Teams banner, causing people to get locked out of meeting controls.
This REALLY needs to be reverted.
All I know is that in my last conversation with an SC engineer, they mentioned the issue is being actively discussed and should be resolved “soon.” What “soon” means is anyone’s guess—it could be a month, maybe two. They did confirm, however, that it’s currently the most talked about issue and that numerous partners are royally pissed. I do agree with the other post about getting out of contracts or another option is credits.
I've used every remote software out there and I still believe SC is the best remote access product on the market, but its product support has been trending in the wrong direction. We came from TeamViewer (TV) and glad we left them and will never go back regardless of these SC issues. [If anyone is still with TV, I strongly recommend leaving as soon as your contract is up and never giving that company another dime. We had tickets and emails "in writing" confirming that auto-renew was disabled. For years, this was never an issue. Then last year, they charged us anyway. When we opened a ticket about it, TV claimed we hadn’t replied to their auto-renew Nov notice, despite our documentation clearly showing auto-renew was disabled back in 2018. We even filed a chargeback with our bank, but TV argued that “per the EULA, you didn’t respond to the auto-renew notice,” and the bank sided with them every time. TV knows exactly what they are doing and updated their EULA. They're criminals, just like the banks. We went as far as hiring an attorney in New York to file a suit, but ultimately decided not to proceed—the legal fees would have exceeded the amount in dispute. Attorney's always win! We also worried about potential retaliation, such as being permanently banned from using their free version for one-off clients. In the end, we had to cancel our business card entirely just to stop them from charging us again. Now they get no money from us and we use their free product. All we wanted to do was downgrade our product to a less amount version, however, they refused, so we killed them off completely. In they end, they scammed us but lost all future business from us and everybody we talk to we make sure they never use them again.]
As a final thought, new features for SC are great, but the priority should be supporting the existing product and keeping partners satisfied to not leave. Change can also be valuable, but hard forcing it across all partners without fully considering the impact only creates unnecessary frustration.
Side note: Simple copy-and-paste still isn’t working from Excel or other applications—a problem that’s been around for a long time. My ticket on this has been open for a year and a half. Yes, you read that right, 1.5 years! Supposedly, it’s finally fixed and will roll out in version 25.7 or 25.8, so we’ll see.
Everyone,
We’ve been doing a deep dive on security and design, which meant tearing things down and rebuilding some core features from scratch. It’s not just cleanup; we’re rethinking how things work to make the product more secure, scalable, and future-proof. That’s led to some tough calls in terms of priority, but we're still hard at work.
Version 25.6 began stable rollout earlier this week. In this release, we’ve removed the Guest Page Welcome Panel Heading and Message—only the “Join with Code” box will be shown now.
Version 25.7 is expected to roll out in about three weeks. In that update:
We’re listening, and we’ll keep sharing updates as things roll out.
Thanks Sean, however version 25.6 is still not available on the download page.
(I check 3 times a day, with the cumbersome filling in of the license key)
I used to be a member of the focusgroup to be able to test beta releases. For some reason, that and the Slack forum : Screenconnect Advisory group does not seem to be active anymore.
Thanks Sean, however version 25.6 is still not available on the download page.
(I check 3 times a day, with the cumbersome filling in of the license key)
I used to be a member of the focusgroup to be able to test beta releases. For some reason, that and the Slack forum : Screenconnect Advisory group does not seem to be active anymore.
Hey Eric,
I posted this a while back, I'd expect it to be available mid-next week.
ScreenConnect release process / ScreenConnect
Sean in that case it should have been available as Pre-Release to download since it has been available as preview for quite a number of days before it went stable.
No interest in beta testers anymore ?
The hide function needs returning.
Some connections I'm constantly moving that bar around the screen out of my way... but invariably it ends up in the way.
Most useful place is I drag it off the screen in the bottom right past the clock in the area of the show desktop button.
Everyone,
We’ve been doing a deep dive on security and design, which meant tearing things down and rebuilding some core features from scratch. It’s not just cleanup; we’re rethinking how things work to make the product more secure, scalable, and future-proof. That’s led to some tough calls in terms of priority, but we're still hard at work.
Version 25.6 began stable rollout earlier this week. In this release, we’ve removed the Guest Page Welcome Panel Heading and Message—only the “Join with Code” box will be shown now.
Version 25.7 is expected to roll out in about three weeks. In that update:
We’re listening, and we’ll keep sharing updates as things roll out.
So to be clear we will be able to hide it again or just the notification balloon - and does this apply to self hosted or cloud versions? I like many others am canceling if I cannot get rid of this and my renewal is in 2 weeks. I use the platform for not only my customers but my own machines it's driving me insane. Don't fix what isn't broke my goodness.
We have serious concerns over the recent changes in ScreenConnect that have removed the ability to hide the connection banner and the system tray icon in Remote Access sessions.
These visibility controls were critical for our deployment. We use ScreenConnect in a tightly controlled, enterprise-managed environment. The ability to suppress the banner and icon was essential to our workflow, particularly for performing maintenance, silent updates, and classroom technology support where non-disruptive access is a requirement.
These changes negatively impact the functionality we’ve come to rely on and fundamentally reduce the value of the product for our use case.
Reconsider this change and restore the ability to suppress the connection banner and tray icon, at the very least, for customers using enterprise or paid versions of the software who can affirm proper use in managed deployments.
Please advise if a rollback is being considered. This is an important issue for us, and we’ll need to reevaluate our continued use of the platform if this restriction remains in place.