We have received reports of malfunction after update to beta 1. We have identified the cause and are working on a fix. We expect to release it in beta 2 early next week. Until that, you can open Services as administrator and restart "F-Secure Hoster" service to fix the problem.
An error has been encountered and the device needs to be restarted for protection to take effect
krankenzxczxc
Posts: 2 Observer
Answers
-
Hello,
I am also only an F-Secure user.
I think it is better to send an email via current beta communication channel:
beta@f-secure.com
fsdiag can probably be attached to a letter or uploaded via a web form (upon request in response to your initial email; or if you have already been sent / know the secure link - as a reference to How to submit a large FSDIAG file to customer support | Total | Latest | F-Secure User Guides).
I think I have the same problem with fs protection on two devices (these are the only two devices I tried to update to 19.9 beta 1 on).
Thanks!
-
just as a follow-up about subject
Although on one of the affected systems I tried the suggested step of restarting F-Secure Hoster and this did not fix the problem, but maybe in your situation it could help (or as already written - wait for the release of beta 2 next week).
Of course, if this notification is related to this malfunction.
-
-