Overview
Splashtop SOS is designed to run without requiring installation on the end user's computer. When launched, the SOS executable temporarily extracts its runtime components into the user's local temporary folder and starts several supporting processes required for remote support sessions.
In most environments, no additional configuration is required. However, if antivirus software, Endpoint Detection and Response (EDR) solutions, application control policies, or restrictive firewalls are deployed, they may block one or more SOS components and prevent successful connections.
This article outlines the recommended exclusions and allowlists for Splashtop SOS.
SOS Temporary Extraction Directory
When Splashtop SOS is launched, it extracts its runtime files into a temporary folder under the user's profile:
%USERPROFILE%\AppData\Local\Temp\unpacksos\A randomly generated numeric subfolder is created beneath this directory for each SOS session.
To prevent interference from security software, we recommend allowing all SOS executables under:
%USERPROFILE%\AppData\Local\Temp\unpacksos\*.exeRequired SOS Executables
The following executable files are extracted and launched by Splashtop SOS during a support session.
These files should not be blocked, quarantined, sandboxed, or prevented from launching by antivirus, EDR, application control, or behavior monitoring policies.
Launcher.exe
SRAgentSOS.exe
SRAppPBSOS.exe
SRAppSOS.exe
SRAudioChatSOS.exe
SRChatSOS.exe
SRFeatMiniSOS.exe
SRFeatureSOS.exe
SRFeatureSOSNoUIA.exe
SRManagerSOS.exe
SRServerSOS.exe
SRServiceSOS.exe
SRUtilitySOS.exeBlocking any of these components may result in:
- SOS failing to start
- Remote sessions disconnecting unexpectedly
- Continuous reconnecting behavior
- Missing remote control functionality
Firewall Requirements
Splashtop SOS uses the same cloud infrastructure and network requirements as other Splashtop services.
For the latest firewall exceptions, required ports, domains, and IP address information, please refer to: