Uninstall LabTech and ScreenConnect Agents: For those who are having a hard time uninstalling the LabTech Agent from their computer, the first script will remove the LabTech Agent, and the second will remove ScreenConnect aka (ConnectWise Control).

UninstallLabTechAgent.ps1

$url = "https://s3.amazonaws.com/assets-cp/assets/Agent_Uninstaller.zip"
$output = "C:\Windows\Temp\Agent_Uninstaller.zip"
(New-Object System.Net.WebClient).DownloadFile($url, $output)
# The below usage of Expand-Archive is only possible with PowerShell 5.0+
# Expand-Archive -LiteralPath C:\Windows\Temp\Agent_Uninstaller.zip -DestinationPath C:\Windows\Temp\LTAgentUninstaller -Force
# Use .NET instead
[System.Reflection.Assembly]::LoadWithPartialName("System.IO.Compression.FileSystem") | Out-Null
# Now we can expand the archive
[System.IO.Compression.ZipFile]::ExtractToDirectory('C:\Windows\Temp\Agent_Uninstaller.zip', 'C:\Windows\Temp\LTAgentUninstaller')
Start-Process -FilePath "C:\Windows\Temp\LTAgentUninstaller\Agent_Uninstall.exe"

UninstallScreenConnectClient.bat

wmic product where "name like 'ScreenConnect Client%%'" call uninstall /nointeractive

Works great! Thanks for this!

Brilliant, thank you.

Just made an account to let you know it's still helping people to this day, so thanks a lot for that! :)

Still working!!!

Very happy to hear this. I am no longer working in the MSP space, but I am happy to hear that this helped so many people.

Thank you! We'll let you know when it's no longer working so you can get a small taste of the MSP space again :)

If you get the following error with System.Net.Webclient:
The request was aborted could not create ssl/tls secure channel

Just add this to the top of the script
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Still works :)
MSPs still exiting clients without proper cleanup.

Might be slower, but that that "Agent_Uninstaller.exe" is basically just a zip file. Use 7-zip, or whatever, to open the file and pull out both that Uninstall.exe and the Uninstall.exe.config files. Put those in the same location and run the Uninstall.exe. Takes a moment but should still do the trick.

Went through writing a script to identify the uninstall string in the registry and found that it didn't do squat. This script, however, still delivers in 2025. Thanks!

Still works, awesome 👍

While the script seems to work fine, I'm leery about how generic and unaffiliated the $url link appears to be with ConnectWise. Is there any official documentation or support that shows this isn't some random file that someone could swap out at any time for a malicious version?

@InsanityOnABun I wrote this a very long time ago and stopped working for MSPs not too long after I wrote it, but I got this link from opening (at the time) ConnectWise Automate and looking for the Agent Uninstaller there. If there is documentation, it isn't prominent. As far as I know, assets-cp is ConnectWise's AWS S3 bucket.

While the script seems to work fine, I'm leery about how generic and unaffiliated the $url link appears to be with ConnectWise. Is there any official documentation or support that shows this isn't some random file that someone could swap out at any time for a malicious version?

Does a powershell command that doesn't connect to any web resources work instead? Dunno about any "official documentation or support", but it has the benefit of working.

( Get-WmiObject -Class Win32_Product | Where-Object{$_.Name -like 'ConnectWise Automate*'} ) | ForEach-Object {
& msiexec /x $_.IdentifyingNumber /quiet /qn /norestart
}

At the time that I wrote these scripts, I was trying to clean up old agents that would not uninstall, did not show up under Win32_Product queries, didn’t have clean registry entries for the agents. And I had to get it done across thousands of endpoints, without downtime.

If you are a subscriber to ConnectWise Automate, go to the link in your Automate interface for the agent uninstaller and compare it to the one in the script above, that should resolve your doubts. I know it’s frustrating to trust a “random URL”, but that’s how you can verify it. Again, I haven’t used ConnectWise Automate in years, I just left this up here to help others.

@realchrisolin Your script is the “happy path” where everything is clean. I didn’t have that scenario. The Agent Uninstaller works no matter if whoever installed the agent made it so it would only uninstall if the server told the agent to uninstall itself, or if the agent got corrupted, or if the registry is broken.