FS Protection PC 19.1 releases

Huomenta (or Hello),

When is the version 19.1 likely to be released? It's already February 20 and my Software Update Monitor tells me that there is an updated version of F-Secure OneClient available (new version is 7.26.11.0).

How is the update to be released? Manually polling via Settings/Updates is rather unreliable.

Is the next beta going to change the taskbar icon too?

Or it's going to stay as it is because it's beta? :)

Left is stable version's icon, right one is beta's:

Seems my insider licenses have expired what did nhappen ? where can I get help ? Please pm the answer if you have disclosure worries

Hello,

I have some unclear results with this nice feature.

Is there any complicated logic about?

I mean, originally my set up was "Every four weeks" (a certain day / time). When first time scheduled scan missed (system was OFF) -> it is re-scheduled to the next week (so, right the next week). Second time (system was OFF / I managed to shut down laptop before the time of scheduled scan point) -> it is re-sechuled to the next week again.

Then, I decided to check with other options. The first one was "Daily". Also managed to miss scheduled scan point by turning system off before. With the very next launch (~some hours after, maybe no more than six or eight) - scheduled scan is triggered. So, really like "as soon as possible". Missed -> next system launch. I skipped the actual scanning then (if important).

Then, I decided to check with "Each week". Missed scan date is re-scheduled to the next launch system (as with "Daily"). Thus, also "as soon as possible". Missed -> next system boot - scheduled scan is triggered. Also skipped it.

Then, I tried to check back with "Every four weeks" and got another experience (compared to original). Missed scheduled scan is re-scheduled to 'four weeks later'. So, not "the next week" as before, but the next "after four weeks". Probably, it was 06.03.2023, so switched now to 03.04.2023

This result is different with my original (when 'virtual' 06.03.2023 would be switched to 13.03.2023 as example) and other options (when 'virtual' 06.03.2023 miss ->> next system launch; like 'as soon as possible').

Is this matched to feature's expectations? Like if some else things will affect re-scheduled point. Weekday/weekend... system resources.. or something.

Thanks!

Hi,

It looks like I just got the 19.1 beta 2 today.

And since then, I have had it. I am in a loop:

1. The first screen - I need to log in - OK, it's working
2. one screen asks me to free a license since there are not any available
3. a button invites me to see the list of devices to free one
4. I do, and it then goes to a white screen
5. back to the first one, saying no license is available
6. I go again to the device list and see my current device added.

If I do this 3 times, I'll see my device name 3 times. But I can never free and use a license. I'm 100% stuck.

And that's the case on 2 laptops.

Yep,. this. You described the case much better :)

We had a problem with licensing server, see https://community.f-secure.com/en/discussion/126394/beta-account-getting-logged-out#latest

In fact, it has been working on one of the two laptops I'm using.

For the failing one, it's the same experience as I described yesterday.

I had a little trouble trying to login after the update. But it seems to be working ok now. I am able to login fine now. This is the first time I've had to "login" after an update. It seemed a little strange. And then when I couldn't login, I was a little worried. But I am able to login in now & everything seems to be working good.

I feel I haven't contributed much lately. But its only because everything has been working good for me. I haven't had any problems. Until trying to login after this last update. But that is working again now.

Thank you!!!

Again I tried logging into the community here & I wasn't able to login using my usual email address & password. This time I had to use the "forgot password" link to change my password, so I could login.

A few weeks ago I had a problem logging in. But after a little bit I was then able to login. But this time, after a little bit, I still couldn't login. So I had to reset my password in order to be able to login.

This was just for the community here. The FS Protection portal is fine.

Hello,

Can I ask about content filtering / categorizing. And F-Secure security cloud knowledge or other source of decision?

Or, maybe, there are some tweaks about how it works or more complicated decisions?

Because some days (or maybe week/weeks already) - I feel some changes. Mostly about uncategorized-category (unknown content / unrated). First observation coincided with my attempt to clear up reputation cache ('security cloud'-disconnected state) - so, I thought that it is a temporary situation. And, maybe, a lot of ratings are gone (happened yearly...).

But some examples are still there (I also tried 'rate' them via BP extension - but nothing yet changed). For example, uncategorized/unrated/unknown-content reputation is applied suddenly to:

• some Google Account pages (in gmail way to login); For example, to open login Gmail form - I need to allow web-pages twice. Both for accounts[.]google[.]com (which can be enough for both, but by surfing way - I ended with allowing first accounts[.]google[.]com/ServiceLogin and then accounts[.]google[.]com/v3/signin/identifier - that's URL in allowed websites)
• then Outlook - outlook[.]live[.]com;
• en[.]wikpedia[.]org (but.. for example, no[.]wikpedia[.]org is still okay);
• search[.]yahoo[.]com/

and so on. all of them are about subdomains (looks like), but as with wikipedia example - Norwegian (for instance) with no changes about rating (still rated);

Another example is DuckDuckGo main-page:

• duckduckgo[.]com is blocked as "Illegal Downloads" (which I am not sure if applied to some functionality of this search engine).

All mentioned changes (duckuckgo maybe a bit more later) appeared at once. Tried them re-rate (or rate) via BP extension and (yet) allowed them locally.

Just not sure is it 'should be' reported via F-Secure SAS for re-rating. Or something different with entire design, so.. mentioned result is expected and normal one. Like if it is should be so.

Thanks!

There was a bad Ultralight update F-Secure Ultralight Core (64-bit) 2023-04-13_01 published to beta that causes the product to show malfunction error. This error is not real - the protection still works. To clear the error you need to restart your device. We are sorry for the inconvenience.

Hello,

No any updates since 28.04.2023 (the last was Capricorn 2023-04-28_03). Are they just hooked / frozen till something*?

*stable dbtracker seems still with quite active releases of updates (Capricorn engine as example).

Yes, as such, it's a perfectly normal situation.

the last one was in the middle of Friday. and just then downtime for the whole weekend. I just thought it was odd that nothing had arrived today (01.05.2023). I looked in dbtracker (a stable F-Secure solution) and there were no such breaks this weekend. // sometimes, virgo/hydra/deepguard database or anything else also can be updated suddenly.

I thought that either something went wrong with my installation or just the beta solution froze the delivery of updates temporarily. // also, I looked at the time of announcement of beta releases in the topic and they were all in the morning or close (so I decided to write a comment, since it's not morning anymore; and if assuming there are no updates because of potential next beta-release).

// Well, I'll add. however, this is not the first case of course. It's just that this time it somehow suddenly drew attention to itself. And usually before it turns into a concern - some of the updates arrive.