Support articles

Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.

Elements Endpoint Protection Agent's WithSecure Plugin Hosting Service is causing high CPU usage

Issue:

I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Elements Endpoint Protection, why is this happening? It is slowing down the performance of the device. 

Resolution:

When WithSecure plugin hosting service is using high amounts of CPU performance and disk resources, it is an indication that: 

  • A scheduled or manual scan is currently running and it is scanning the files
  • Real-time scanning scanning files that are accessed by the system 

If you want to confirm if a scheduled or manual scan is running, you can check from the Task Manager's Details tab if the fsscan.exe process is running. If it is, then a scheduled or manual scan is currently running and that is causing high CPU and RAM usage, especially if you have scanning of compressed files (archives) enabled in the Elements profile. 

To change the scheduled and manual scanning settings:

  1. Log in to the Elements Security Center portal
  2. Navigate to the Security configurations > Profiles page
  3. Click on the profile that is in use on the devices 
  4. Go to the Manual scanning settings page

Here you can find separate sections for scheduled scanning and manual scanning settings. To decrease the CPU usage during scans, you can:

  • Enable Run scanning as low priority
  • Disable Scan inside compressed files
  • Enable Scan only known file types during scheduled scanning

To stop or cancel a scheduled scan, you can follow these steps:

  1. Open the WithSecure client's user interface
  2. Click on the three dots and select Recent events 
  3. Click on the Cancel button on the right side of the ongoing scheduled scanning event

 

If the issue is not caused by a manual or scheduled scan, it could be that real-time scanning is scanning some files for a very long time or very frequently. If you collect a wsdiag diagnostic file from the device, you can check the fa.log (frequently accessed) log file from the path wsdiag.zip\f-secure\logs\system\FSAV\. 

Here is an explanation of the columns in the fa.log:

  • First column: 1 means scan was longer than usual. 2 means file was scanned frequently
  • Second column: how many milliseconds the last scan took and if file has been scanned frequently, How many milliseconds in total has been spent scanning the file
  • Third column: How many times the file has been scanned 
  • Fourth column: Date and time of last scan
  • Seventh column: path to the file

You can use the information in the fa.log to create real-time scanning exclusions in the device settings. 

High CPU usage can also happen if Security Cloud is either disabled or it doesn't have proper network connectivity. To check the network connectivity, run the WithSecure Connectivity Tool from the product's installation folder: 

  • Elements EPP for Computers/Elements EPP for Servers: C:\Program Files (x86)\F-Secure\PSB\ui\wsconnectionchecker.exe

If Security Cloud is disabled, you can enable it from the Elements profile from the Real-time scanning settings page, with the Upload suspicious samples to WithSecure Security Cloud setting. You can select from the drop-down menu either Upload all suspicious files or Upload suspicious executables only to enable Security Cloud. 

If the high CPU usage appears on a Terminal Server:

If fshoster32.exe causes high CPU usage on a Terminal server, we propose to disable the Elements Agent's local user interface:

  1. Log in to the Elements Security Center
  2. Navigate to the Security configurations > Profiles page
  3. Open the server profile 
  4. Go to the General settings page
  5. Disable Show user interface to clients 
  6. Click Save profile