Splashtop Streamer v3.5.6.0 generates high CPU and IO load due to antivirus software

A note for users of Splashtop Streamer software (is integrated into management tools like NinjaRMM) who wonder about high CPU and IO load on their machines. The cause could be the antivirus software in use, which wants to scan log files generated by the software.

Splashtop Streamer is a remote software that can be installed on Windows, Mac or Linux computers. Then the Splashtop app can be used to access the computer from another device to display its screen contents and control the device.

A reader tip

German blog reader Michael K. emailed me this week to let me know about a problem with the Splashtop Streamer version 3.5.6.0 solution (thanks for that). Michael wrote:

Hello Mr. Born,

I wanted to bring to your attention a problem with Splashtop Streamer in combination with antivirus solutions.

According to a technician [of the company] Splastop writes temporary files with the update v3.5.6.0, on which the virus scanners jump and increase the CPU and hard disk load.

In our case, Splashtop Streamer is integrated into NinjaRMM, a remote management tool, and the virtual servers in a VMware environment run SentinelOne as antivirus protection.

As a result, the entire ESXi was overloaded in our case and normal work was no longer possible for the employees.

Maybe one or the other admin also has to fight with this problem.

Michael was kind enough to share the following information from Splashtop with hints to the problem:

Issue: We have received reports of an issue involving high-resource utilization from Splashtop and various antivirus products. This issue appears to be related to Splashtop Streamer v3.5.6.0.

Per Splashtop, this is likely due to how Splashtop utilizes WMI to gather system and hardware inventory conflicting with scheduled or on-access AV scans. Splashtop's Development Team expects that this will be fixed in their next update, v3.5.8.0.

Workaround:

1. Splashtop has recommended that you create an AV exclusion for the entire Splashtop Program Files (x86) directory. If this exclusion does not work for your particular AV, please work with your AV's Support Team to determine the necessary exclusions that need to be made.

2. If you do not wish to create an AV exclusion, you can disable Splashtop per device or per organization. Instructions on Splashtop removal can be found in Uninstalling Integrated Components.

Please note that Splashtop client updates are controlled by Splashtop. Please see this Splashtop article for more information about automatic Splashtop Streamer updates.

Solution: Splashtop independently controls its update channels and will gradually roll out 3 5.8.0 on applicable devices. Ninja does not have the ability to control which devices are targeted, as updates are pushed out directly by Splashtop on a rolling basis. Please see this Splashtop article for more information about automatic Splashtop Streamer updates.

Maybe it helps somebody who is affected.