macOS - Software - Uninstall Splashtop Streamer

What the Splashtop Streamer uninstaller does

This Automox Worklet™ completely removes Splashtop Streamer from macOS endpoints by targeting the application bundle, launch daemons, system preferences, and installer receipts.

The Worklet first attempts to run the application's built-in uninstaller if available. It then stops all running Splashtop processes and unloads system services via launchctl. The Worklet removes the application bundle located at /Applications/Splashtop Streamer.app, along with all support files stored in system and user Library directories.

splashtop.streamer-agent.plist".

Finally, the Worklet clears package installer receipts so the operating system no longer tracks Splashtop Streamer as installed. This prevents reinstallation issues and removes all traces of the application from your endpoint.

Why remove Splashtop Streamer from macOS endpoints

Organizations often need to remove legacy or unapproved remote access software to maintain security compliance and reduce the attack surface on managed endpoints. Splashtop Streamer, while a legitimate remote support tool, may conflict with newer remote access solutions or fail to meet your security requirements.

Leaving remnants of uninstalled applications creates persistent risks. Background processes continue consuming system resources, configuration files may interfere with system updates, and orphaned service entries complicate troubleshooting. A complete, automated removal maintains consistency across your endpoint fleet.

Use this Worklet to enforce software policies, free disk space on resource-constrained endpoints, or maintain clean transitions when you migrate from Splashtop to alternative remote access platforms.

How Splashtop Streamer removal works

1. Evaluation phase: The Worklet checks for Splashtop Streamer installation across three methods: the application bundle at /Applications/Splashtop Streamer.app, launch daemons and agents in /Library/LaunchDaemons and /Library/LaunchAgents, and installer package receipts via pkgutil. If any indicator of installation is found, the Worklet returns a failed status.

2. Remediation phase: The Worklet executes Splashtop's official uninstaller script if available within the application bundle. It then forcibly stops all Splashtop processes and unloads system services using launchctl. The Worklet deletes the application bundle, removes support directories in /Library/Application Support, clears preferences in /Library/Preferences, and removes launch configuration files. Finally, it strips installer receipts so the system no longer recognizes Splashtop as installed.

Splashtop removal requirements

• macOS 10.12 (Sierra) or later

• Local administrator privileges to remove system services and application files

• Bash shell available on the endpoint

• Sufficient free disk space if Splashtop Streamer is currently running

Expected state after Splashtop removal

After the Worklet completes successfully, Splashtop Streamer will be completely removed from the endpoint. The application bundle will no longer exist in /Applications, system daemons will be unloaded, and all configuration files will be deleted. The endpoint will show no trace of Splashtop installation when checked via pkgutil or file system inspection. You can verify this change through the Automox Activity Log or by checking the endpoint configuration directly.

The operating system will no longer report Splashtop Streamer as an installed application. System resources previously consumed by background processes will be freed. If you run the evaluation script after successful remediation, the Worklet will confirm that Splashtop Streamer is not found and return a compliant status.

How to validate uninstall splashtop streamer changes

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

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 set, exit, else.

4. Validate remediation effects from script operations such as set, log, exit, then rerun evaluation for compliance.