FS Protection PC 18.2 releases will be posted under this thread.
SAFE 18.2 was released to production. Thank you all beta testers.
F-Secure R&D, Desktop products
"Tamper protection ..." - I was really looking forward to this feature. Many thanks to the developers! I think the defense is even more secure now. :)
please send me the link of fs beta. Thanks
You can register here: https://beta.f-secure.com/welcome/
self updated without my intervention, works perfectly fine on W11 x64, I tied all options: ok
I am unable to get beta fs protection0 key. please help me.
Sorry for this comment.
I am not sure if there is any connection with fs protection. But just as a thought and ask about the experience of other users.
My laptop with Windows 10 system has no huge changes. However, there are some. For example, some Windows own updates, some drivers updates, a try to use Microsoft Windows Game Mode and nothing more out of the common state. Also, there was F-Secure Ultralight Core (64-bit) update. Partially, the most 'recent' to date after which something triggered BSODs.
So, the trouble is: from 20.11.2021 to 25.11.2021 - I experienced three BSODs. All of them were after system launch and some minutes of use it like browsing (but only today I saw the BSOD, and not the already rebooted system) with no much strange activities. Basically, two (?) opened browsers and trying to use them (switch tabs) or "background" loading for the first two occurrences.
CRITICAL_PROCESS_DIED (0x000000ef (0xffffc28e1d3950c0....), there are dumps - but I did not manage to check anything with them.
Has anyone seen anything like that recently? I just did not remember any of such BSOD before with that system.
@Ukko Windows bluescreen with CRITICAL_PROCESS_DIED happens because some critical user-mode process died. I believe session manager and service manager are these kind of processes. I hit this problem often around 2007 when developing DeepGuard user-mode hooking and if there was a bug, it took down one of these processes, resulting in bluescreen.
So, it could be a bug in DeepGuard or it could be a bug in Windows itself. We need a bit more data to investigate.
Thanks for the detailed explanation, could you please create a bug ticket with fsdiag? Please change the log level to debug beforehand.
Best Wishes, Ivan.
SAFE PC 18.2 went from beta to production on Tuesday. Thanks again to everyone for the good feedback and bug reports - those are very helpful and valuable for us!
...but the wheel keeps turning and our work continues with 18.3. See you there.
Sorry for the reply. A bit of addition to the "CRITICAL_PROCESS_DIED" discussion.
Today is the fourth time. Before the blue screen (minutes) - I noticed that Windows Security informs about trouble with security solution (snoozed?) And notification mark on logo. Then, while trying to use some websites - Microsoft Edge crashed. Then, I feel some laggy around. And then after re-try to use (and actually use a bit) Microsoft Edge - blue screen happened.
Perhaps, with the previous three times - Windows Security Center also was with related toast / logo as something wrong with installed AV.
/// two additional points about other things:
Just tried to clean install fs protection. After (before clean installing) one of recent OneClient updates that was after beta 8 and shortly after announce of 18.2 was released to production. When I tried to check updates. The first attempt is fine. If to try once more (briefly) - greyed out button as a result.
However, after and with clean installation. I do not able to repeat this behavior. Is it supposed to be so? Or why it was so before clean installation?
Another point: sounds as My FS Protection portal is a bit overloaded. At least, too visible delays with logging / log out, thinking and so. Is it possible to check? Or such delays are about my own network connectivity? Originally, I felt it with Android clients. Today with Web-version and then with Windows-client functionality about "People and so".
FS Protection has recently suffered from some bugs in the Banking Protection area, which some of you have also noted and reported. Symptoms have been mainly such as slowness accessing web sites during banking sessions (or even failures to open web pages), including those of the banking site. These issues should now be resolved with the latest NIF Web Plugin update 2021-12-21_01.
If you are still suffering from such problems then please report them through the Beta portal as usual.
Apologizing for the inconvenience caused by this.
Thanks, Best Regards, Urmas