Support articles
Find clear, step-by-step solutions to common WithSecure issues across installation, configuration, updates, and product performance.
WithSecure product installation fails due to error: “F-Secure Hoster (Restricted) failed to start”
Last updated
Issue:
This articles applies to the following WithSecure products: Client Security, Server Security, Elements EPP for Computers, Elements EPP for Servers
The WithSecure installation fails and I see windows system event log shows error message: "Error 1920. Service 'F-Secure Hoster (Restricted)' (fsnethoster) failed to start. Verify that you have sufficient privileges to start system services."
Resolution:
The error message might indicate that there are missing permissions in the root-directory where the WithSecure product is trying to be installed or is installed.
We recommend download and run the WithSecure Uninstallation Tool, then delete the entire C:\Program Files (x86)\F-Secure folder, reboot the, and retry the installation. Uninstallation Tool can be downloaded from here: https://support.withsecure.com/en/support-tools/
If running the uninstallation tool and restarting the computer did not fix the issue:
- You will have to verify that the default permission set. If you are using the default installation path (C:\Program Files (x86)\F-Secure), verify that the Program Files (x86) directory has permissions set for the following: NT AUTHORITY\NETWORK SERVICE.
- In doubt, reset the permission on that specific directory back to defaults and retry the installation.
Other possible solutions:
- Check if Windows is fully updated
- Check or reinstall .NET Framework 4.7.x
- Check or reinstall Universal CRT
Potential Workaround:
- Rename following files to anything else (e.g. vcruntime140_old.dll):
- On 64 bit Windows:
-
C:\Windows\SysWOW64\vcruntime140.dll C:\Windows\SysWOW64\msvcp140.dll
On 32 bit Windows:
-
C:\Windows\System32\vcruntime140.dll C:\Windows\System32\msvcp140.dll
-
- Restart the host
If the steps above still causing error message "fsnethoster does not have sufficient privileges", there is a possibility that registry key HKEY_USERS\S-1-5-20 doesn't have the required permission for NETWORK SERVICE and fsnethoster is unable to create an entry there. For this follow the steps below to try fix the issue:
- Click Start
- Type regedit, and press Enter
- Navigate to and select registry key HKEY_USERS\S-1-5-20
- Select Edit
- Select Permissions
- Click Add…
- Type NETWORK SERVICE
- Click Check Names (the name should get underlined)
- Click OK
- Check Allow checkbox for Full Control (also Read permission should be automatically allowed)
- Click Apply
- Click OK