An error has been encountered and the device needs to be restarted for protection to take effect

krankenzxczxc

An error has been encountered and the device needs to be restarted for protection to take effect。After restarting, it still doesn't work。

PII: FSDIAG removed

Ukko

Hello,

I am also only an F-Secure user.

I think it is better to send an email via current beta communication channel:

Spoiler Warning

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!

Ukko

just as a follow-up about subject

https://community.f-secure.com/en/discussion/comment/139101#Comment_139101

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.

Chaddy_the_Owl

I was going to blame macOs Sequoia! ;-)

krankenzxczxc

I reinstalled the software. Solved this problem