Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
Business Suite Client Security or Server Security WithSecure Plugin Hosting Service is causing high CPU usage
Last updated
Issue:
I am noticing high CPU usage by WithSecure Plugin Hosting Service in Windows host installed with Business Suite Client Security or Server Security, 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 host's policy settings.
To change the scheduled and manual scanning settings for Client Security or Server Security:
- Log in to the Policy Manager Console
- Select a host or policy domain from the domain tree
- Open the Settings tab
- Navigate to the Windows > 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:
- Disable Scan inside compressed files
- Enable Run scanning as low priority
- Enable Scan only known file types
To stop or cancel a scheduled scan, you can follow these steps:
- Open the WithSecure client's user interface
- Click on the three dots and select Recent events
- Click on the Cancel button on the right side of the ongoing scheduled scanning event
- Note: the Allow users to skip scheduled scans setting must be enabled for a local user to be able to stop a scheduled scan
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:
- Client Security: C:\Program Files (x86)\F-Secure\Client Security\ui\fsconnectionchecker.exe
- Server Security: C:\Program Files (x86)\F-Secure\Server Security\ui\fsconnectionchecker.exe
If Security Cloud is disabled, you can enable it from the policy settings:
- Log in to the Policy Manager Console
- Select a host or policy domain in the domain tree
- Open the Settings tab
- Navigate to the Windows > Real-time scanning settings page
- Enable Use Security Cloud
- Distribute the policy (Ctrl + D)
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 local user interface for Server Security:
- Log in to the Policy Manager Console
- Select a host or policy domain in the domain tree
- Open the Settings tab
- Navigate to the Windows > Centralized management settings page
- Scroll down to the Local user interface section
- Disable Show local user interface
- Click Save profile