Products & Services
FS Protection PC 18.3 releases will be posted under this thread.
Thank you for the continued updates & fixes! Happy New Year 2022!!!
Hi, I was trying to install the this beta version but i received the follow error.
I´m using windows 11 Pro 21H2 and im on preview chanel.
Can you help pls? How can i install this version? Never happened before. I installed and production version 18.2 today and it installed fine. But i want to return to beta version on this device.
smooth ride as always
Please run support tool to collect logs so that we can analyze the problem. Attach the output (fsdiag.zip) to the report. (https://beta.f-secure.com/welcome/)
Meanwhile please try to update Windows, and see if that solve your issue?
Thank you Fengping! I sent today. when i had the 18.2 installed to see if with this one works and it didnt work only with the new beta.
not a glitch, than k you, evolution not revolution works best
We have released a new beta Browsing Protection extension to beta. This extension is automatically installed to Chrome and Edge browsers and user is asked to enable it by the browser. The old extension is automatically removed from browser. Firefox continues to use the old extenion.
The new browser extension is using latest browser APIs to work and there are no changes in functionality.
You receive the update silently as part of "F-Secure NIF Web Plugin 2022-01-26_01".
F-Secure R&D, Desktop products
One addition: because the new extension will not be enabled automatically while the old one will be uninstalled automatically, you may get a "task" about the missing extension in the user interface of FS Protection when you open Chrome or Edge for the first time after receiving this update.
I am using Edge browser and I had a little box come up in the upper right corner of the page, saying the new browsing protection extension for FSecure was installed & to either click to enable the extension or to cancel it. I clicked to enable it.
Yes, this is expected also. The NIF Web update automatically installs the new extension, but cannot enable it automatically, this always requires user decision.
There is one more thing: in case your computer did not get beta 2 yesterday (e.g. you did not use the computer, or it did not check for updates), you may get the NIF Web update before beta 2 update. In this case, your browser extension will not be upgraded. It will be upgraded with the next NIF Web update when it becomes available.
Alternatively, if you wish, you can install the new version 4 extension manually using the Chrome or Edge web store links on Settings UI. In this case, you will need to disable the old version 3 extension. But you don't need to do that, the old extension continues to work and you are still protected.
Thank you very much, Urmas!!!
There is one issue we discovered yesterday. With Edge, even after you have enabled the new browser extension (version 4), the "orange" task in Main UI asking you to set up the extension will remain because of a bug in the browser extension state detection logic. This will be fixed in the next beta release. Until then, you can dismiss the task once you have verified that the extension is indeed installed and enabled. The task will disappear automatically once you get the fix, in the next beta.
Interesting :) My experience was about a dismissed task (to check if it ever reappears and the browser extension was removed from Microsoft Edge). So, when Microsoft Edge received a browser extension (4) -> the browser reported it and I decided to activate it (though not from the very first opening). As a result, dismissed task disappeared (as if not actual or as if I "configured" the extension).
However, I look into the card to see (whether it is and what is there) after activating the extension. And the task remained in the dismissed state. The task itself did not disappear immediately (I think it was expected) - but after some minutes - and it already disappeared.
Sounds like the opposite of the trouble discovered. :)
I'm using win21H2 on two desktops, with 18.2 and 18.3 beta installed on each. 18.2 is fine, but in 18.3 Beta I can't connect to the security cloud. There are no problems with other processes such as updates.
I'm not sure if I should do bugreport, but I find it a bit odd that FS-Secure asks to uninstall the HitmanPro scanner before installing, and without that you can't proceed to the installation. Since it's an on-demand scanner that doesn't even install any drivers as far as I can see, what possible compatibility issues could there be to block installation like that?
We have reverted a recent change which was the reason for the update problem you have observed. Should be fixed on the next beta.
Thank you for your comment. I have make a ticket (PBL-9469) about it and our development team will look into the issue.
The issue has been fixed by update. Thank you for your prompt response. splendid.
P.S. The connection was temporary. I look forward to beta3.
We don't have resources to test for compatibility with any other AV vendor software. This is why we at the moment just blanket remove all other AV vendors during installation. This question rises from time to time and we will be reviewing this policy in medium-term future, but for now, this is how it is.
If you want to install our product without removing the 3rd-party software, you can run installer with parameter "--skip-sidegrade *".
In general, it's hard to test for compatibility issues with AV products. The problem is that conflicts usually happen during malware infection, when both products are trying to clean it and prevent all other processes from accessing it. They may prevent each other from accessing it, thus, preventing the cleaning from both products from happening.
No problem, i understand this very well. It's just surprising that the installation was prevented by an on-demand scanner (not anti-virus or any other security application) which is not active and not working at the moment. Besides, it is practically the most popular scanner in the world (at least among IS specialists).
Withdraw previous comments. Currently there is no problem with the cloud security connection. The reason why I could not connect was due to the firewall settings of the pc.
I am on a Windows 11 desktop computer. A while ago I noticed in my bottom tray, that the icon is blank (see attached picture) for FS Protection (that when clicked brings up the FS Protection subscription box that says, "You Are Protected" and allows you to control your account (Viruses & Threats, Secure Browsing & Banking, People & Devices, etc.).
I believe I said something a while ago about this. They had me try a few things on my computer (that I don't remember now) but it didn't change it. Every time there is an update, I keep thinking that maybe this will be corrected. But so far it hasn't. It's not causing any problems. But the icon (circled in red in the picture attached) is just blank & doesn't show the FS Protection icon like the one to the right of it (which is the ID Guardian/password manager). I know what the blank icon is, from it being like this for so long. But I'm not sure if this is happening with anyone else.
Is there some way this can be corrected to show the correct icon instead of it just being blank?
The blank "icon" circled in red should show the "Fs Protection" icon instead of it being blank.
Interesting. Could you run support tool to collect logs and attach the output (fsdiag.zip) to the report? Thanks! (https://beta.f-secure.com/welcome/)
Yes. Sure. I ran the support tool. Here is the report.
Edit: PII Removed
"Reset reputation cache" button (PBL-5944) in Settings → Support tab. You can use this feature if, let's say, you had a false positive/negative result.
Sounds that it working silently now. But then, should this button be with any output? Like wording (as with "check updates"), text-line or any pop-up, or any other visible 'reaction' after using button?