Windows - Software - Uninstall Splashtop Business

What the Splashtop Business uninstaller does

This Automox Worklet™ detects and removes Splashtop Business from your Windows endpoints. The Worklet searches both 32-bit and 64-bit registry locations to identify installed versions, then executes the application uninstaller with the silent flag to perform a clean removal without user interaction.

The Worklet handles both MSI-based and EXE-based uninstall strings, which supports various Splashtop Business installation methods. The process runs in native 64-bit mode on 64-bit systems to deliver accurate detection of all installed versions.

Why uninstall Splashtop Business from your endpoints

Removing unused remote access software reduces your endpoint attack surface and simplifies software inventory management. Splashtop Business, like other remote access tools, can present security risks if left installed on endpoints that no longer require the functionality.

Automating Splashtop Business removal through this Worklet allows you to maintain consistent software policies across your Windows fleet. You can retire Splashtop Business across all endpoints simultaneously, rather than manually uninstalling on each machine.

How Splashtop Business removal works

1. Evaluation phase: The Worklet searches the Windows registry at HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to detect 64-bit and 32-bit installations of Splashtop Business. If any version is found, the endpoint is flagged for remediation.

2. Remediation phase: The Worklet retrieves the UninstallString from the registry for each detected version. For MSI-based installations, it runs msiexec.exe with the /x flag and GUID. For EXE-based installations, it executes the uninstall command with the /S silent flag. The process monitors exit codes to verify successful uninstallation (exit codes 0, 1641, and 3010 all indicate success).

Splashtop Business uninstall requirements

• Windows 10, Windows 11, or Windows Server 2016 and later

• Splashtop Business must be installed on the endpoint

• Administrator or SYSTEM privileges required for silent uninstallation

• Supports both 32-bit and 64-bit installations on any Windows architecture

Expected state after Splashtop Business removal

After successful remediation, Splashtop Business will be completely removed from the endpoint. You can verify successful installation by checking the installed applications list in Control Panel or by searching for the application in the Start menu. Registry entries for Splashtop Business will no longer appear in the Uninstall registry keys, and all application files and shortcuts will be deleted. The endpoint will return a compliant status in Automox when Splashtop Business is no longer detected.

Users will no longer be able to launch Splashtop Business from the Start menu or installed applications list. If the endpoint previously relied on Splashtop Business for remote access, you should confirm alternative remote access solutions are deployed before removing this Worklet from your policy.

How to validate uninstall splashtop business changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for uninstall splashtop business.

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for uninstall splashtop business. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Write-Output, Get-ChildItem, Get-ItemProperty and remediation operations such as Get-ChildItem, Get-ItemProperty, Where-Object. Use these indicators to verify that endpoint changes match intended policy outcomes.