Remove ScreenConnect or ConnectWise Control from Windows / Mac / Linux

[Andy]

For Windows
From the "Add/Remove Programs" area of the Control Panel, remove the entry, "ScreenConnect Client (xxxxxxxxxxxxxxxx)" where xxxxxxxxxxxxxxxx is the thumbprint which is unique to your ScreenConnect installation.

You can also remove the access client manually via the administrator command prompt:

wmic product where name="ScreenConnect Client (xxxxxxxxxxxxxxxx)" call uninstall /nointeractive

04/08/2025 Update: An alternative method to locate the ID, along with the output from the command shown above:

This approach has proven effective even when the ScreenConnect client is severely corrupted or partially removed—such as by antivirus software or manual deletion.

For Mac
The access client is installed on your OSX device at /opt/screenconnect-xxxxxxxxxxxxxxxx where xxxxxxxxxxxxxxxx is the thumbprint which is unique to your ScreenConnect installation.

Remove the listed files and directories to uninstall the access client.

1. Stop the ScreenConnect Client service on that device:
   

   launchctl unload /Library/LaunchAgents/screenconnect-xxxxxxxxxxxxxxxx-onlogin.plist

2. Delete the service definitions (both the onlogin and prelogin ones):
   

   rm -v /Library/LaunchAgents/screenconnect-xxxxxxxxxxxxxxxx-*.plist

3. Delete the ScreenConnect Client files:
   

   rm -rv /opt/screenconnect-xxxxxxxxxxxxxxxx.app

Hint: Use the following command to see the thumbprint:

ls -l /Library/LaunchAgents/screenconnect-*

20/04/2024: Update courtesy of @jabba:
For those using later versions of macOS (Sonoma), Jeff has provided updated removal commands. Below are the steps to ensure ConnectWise Control is completely uninstalled:

sudo launchctl bootout system/connectwisecontrol-xxxxxxxxxxxxxx
sudo rm /Library/LaunchAgents/connectwisecontrol-xxxxxxxxxxxxxx*.plist
sudo rm -r /Applications/connectwisecontrol-xxxxxxxxxxxxxx.app

Kudos to Jeff for the update and for helping ensure this guide stays relevant!

For Linux
The access client is installed on your Linux device at /opt/screenconnect-xxxxxxxxxxxxxxxx where xxxxxxxxxxxxxxxx is the thumbprint which is unique to your ScreenConnect installation.

To remove the access client from a Linux device, enter one of the following (depending on your distribution):

dpkg -r screenconnect-xxxxxxxxxxxxxxxx

or:

rpm -e screenconnect-xxxxxxxxxxxxxxxx

 

[Dede]

wmic product where name="ScreenConnect Client (xxxxxxxxxxxxxxxx)" call uninstall /nointeractive

Hi Andy,
1. I tried this, in CMD, It returned:
No Instance(s) Available.
2. I substituted the (xxxxxxx's) by its registry number found on properties sheet I found under "Services". It returned:
Invalid Verb Switch.
What is the meaning of (xxxxxxxxxxxxxxxx) ?

What are the steps ? Are there screenshots step by Step ?

Many thanks.

 

[Andy]

Hi Andy,
1. I tried this, in CMD, It returned:
No Instance(s) Available.
2. I substituted the (xxxxxxx's) by its registry number found on properties sheet I found under "Services". It returned:
Invalid Verb Switch.
What is the meaning of (xxxxxxxxxxxxxxxx) ?

What are the steps ? Are there screenshots step by Step ?

Many thanks.

The (xxxxxxxxxxxxxxxx) in the commands you're using to uninstall ScreenConnect represents the unique thumbprint or identifier associated with your specific installation of ScreenConnect. This thumbprint is a unique string of characters that identifies the ScreenConnect Client on your system.

When you see the message No Instance(s) Available, it might mean that the command is not finding the exact name of the product you want to uninstall, which could be due to an incorrect thumbprint.

The Invalid Verb Switch error could be related to the substitution you made. If you're replacing the (xxxxxxx's) with the registry number you found under "Services," make sure that it matches exactly with the thumbprint of the ScreenConnect Client installed on your system.

To find the correct thumbprint, you might want to look in the appropriate directories mentioned in the instructions, such as /opt/screenconnect-xxxxxxxxxxxxxxxx on Mac and Linux, or look through the "Add/Remove Programs" section in Windows to find the exact name of the ScreenConnect Client installation.

Have a look at my screenshot below:

 

[jabba]

In the later versions of Mac OS (Sonoma). I found these commands worked well to do a manual removal..

sudo launchctl bootout system/connectwisecontrol-xxxxxxxxxxxxxx
sudo rm /Library/LaunchAgents/connectwisecontrol-xxxxxxxxxxxxxx*.plist
sudo rm -r /Applications/connectwisecontrol-xxxxxxxxxxxxxx.app

The previous commands seemed out of date as of May 2024

Cheers

Jeff

 

[Andy]

Hi Jeff,

Thanks for sharing these updated commands for the newer macOS versions. This information is handy as it helps to ensure that this guide remains current and effective for all users.

Cheers,

 

[Andy]

ScreenConnect Client Broke After AV False Positive? Here’s What Actually Happens​

Had a case where Webroot flagged a legit ScreenConnect Client as malicious and partially nuked it. The result?
The client became invisible to normal uninstall methods — Control Panel, Apps list, even some RMM tools couldn’t remove it.

So I dug into the registry to compare:

Three States:​

• Corrupted (after AV interference): 12 registry matches
• After WMIC uninstall: 5 matches left (cleaned up but not fully)
• Fresh reinstall: 15 matches (normal healthy install)

What Was Missing When Broken:​

• No uninstall key in WOW6432Node — WMIC & GUI tools can’t see it
• Installer\UserData completely gone — MSI can’t track components
• .exe and .dll paths removed
• Registry still holds enough to extract the client ID

The Trick:​

Even in that broken state, this still works:
wmic product where name="ScreenConnect Client (xxxxxxxxxxxxxxxx)" call uninstall /nointeractive
Yep — WMIC can still remove it, even if the files are toast. That surprised me.

---

Conclusion:
If ScreenConnect gets misidentified by antivirus or partially deleted, don’t count on GUI tools — they may not even see it.
Instead, dig into the registry to find the client ID, then use WMIC to force-uninstall it. Surprisingly effective, even when the install is badly broken.

---

I’ve added this outcome to the first post of the thread above for reference.

 

[dlcoleman]

In the later versions of Mac OS (Sonoma). I found these commands worked well to do a manual removal..

sudo launchctl bootout system/connectwisecontrol-xxxxxxxxxxxxxx
sudo rm /Library/LaunchAgents/connectwisecontrol-xxxxxxxxxxxxxx*.plist
sudo rm -r /Applications/connectwisecontrol-xxxxxxxxxxxxxx.app

The previous commands seemed out of date as of May 2024

Cheers

Jeff

THANK YOU THANK YOU THANK YOU. This was Driving me CRAZY. My previous employers IT company has lost their minds and have someone trying to remote into my computer at all hours and times and for no reason that we know of and were denying it. I couldn't just delete the app because "it was running". This finally worked so THANK YOU!!!