Published: in Videos
ScreenConnect Now Requires Code Signing Certificate
If you're running an on-premise ScreenConnect (ConnectWise Control) server, you may have recently encountered issues with client installers being blocked or flagged by antivirus software. That's because, as of July 2025, ScreenConnect now requires self-hosted users to sign their guest client executables with a code signing certificate.
We've put together a new video walking you through exactly what's changed and how to fix it.
What’s Changed?
ConnectWise has revoked the shared code signing certificate that was previously used to sign guest client installers for on-premise installations. Without a valid, trusted signature, these installers are now being treated as untrusted by Windows and many antivirus programs, causing failed installations and user trust issues.
What You’ll Learn in the Video
In this step-by-step guide, we show you how to:
-
Understand the reason behind the new certificate requirement
-
Obtain your own code signing certificate
-
Use Azure Trusted Signing and Key Vault to sign your guest client executables
-
Set up automation to ensure your installers are signed daily
Why This Matters
Unsigned or improperly signed executables can cause major disruptions for remote support workflows. By implementing your own signing process, you ensure that your ScreenConnect deployments continue to run smoothly and securely.
Final Thoughts
If you're running ScreenConnect on-premise, this change isn't optional—you'll need to implement your own signing solution moving forward. Watch our video to learn how to get set up quickly and keep your operations uninterrupted.