Every time we update to a new version of ConnectWise Control, it freaks out our EDR. We spend days dealing with hundreds of benign alerts -- because your update files aren't signed. It also delays the rollout process. Would really appreciate if you used signed files for updating. It is more secure and significantly less headaches.
Additionally ScreenConnect causes ESET Antivirus products to go nuts with alerts which freaks out my clients and prevents the program from loading properly and running causing support agents from quickly getting connected to resolve customer issues by having to spend an arduous amount of time resolving something that should be a non-issue without being able to see the customers screen yet. Signing the program would help eliminate this issues. Team Viewer and AnyDesk do not have these issues.
Yes, it is a huge issue that SC does not respect this industry best-practice!
This is a major impact on our workflow every single time there is an update. In this day and age and in the market we are in I do not understand why this is not just standard practice?
Would love to have this enhancement added as well. Would make deployments easier through automation tools.
Hello, I am also looking to have this feature implemented. We use ScreenConnect internally as well as deployed to clients. Whenever there is a server update, our computers prompt to install an update before connecting to the computer. This installer is an MSI file with a randomly generated name and there's no way to identify it as a ScreenConnect updater. Having the files be signed by ConnectWise would help us a lot
Can’t believe this is still a thing in 2025. I just renewed and now I can’t even use the software because AVs are flagging the entire domain I host Control on. Makes my business look shady and blocks connections before I can even help the client.
Self-signing isn't a fix — it still gets flagged. Why is ConnectWise not signing their own installer? This is basic. Might seriously look into switching to RustDesk at this point.