F Secure failed to update
Accepted Answer
-
Hello @BoskoM
Welcome to the F-Secure Community, and thank you for bringing this to our attention.
We have received similar reports regarding this issue. However, we are still in the process of gathering feedback from users. To assist you further and support our investigation, we will send you detailed instructions via private message.
Thank you once again, and we wish you a wonderful day.
Firmy
Community Manager | F-Secure Community
🔐 Strengthening digital security through knowledge and collaboration
🌐 Explore our User Guides | Knowledge Base for self-help resources
💻 Empower yourself with Cybersecurity Insights and protect what matters
Answers
-
It is always a good idea to include the device & software environment where the problem occurred in these notifications, at least:
- Win/Mac/Android/iOS version (supported environments)
- F-Secure version (latest recommended )
- Screenshots(if possible)…
The community portal could also be developed so that this information is always mandatory in opening the threads
-
Thank you,The issue you presented is known to dev. team as far as i know and in that case they are allready eagerly researching the root cause.If they need more information, you will receive a personal message with detail instructions.Othervise we have to wait at least the next release(25.6 ?) to solve this.Unfortunately, the consumer does not normally receive any reason code (info text) for that "failed" reason that would directly tell the possible reason for the failure.
-
win 10
as a random suggestions:
- can you try to restart / reboot system? I mean, perhaps, you may have tried to do this, but it seems like your system with quite a set-up and you may be keeping it "online" without properly shutting it down or rebooting it for long periods of time.
- can you try turning on F-Secure VPN and check if the update can be completed?
- optionally, try to consider whether some applications might be complicating the update process (network [over]load, proxy, simply some kind of system overload, or maybe the update process is somehow failing due to some third-party points, for example, I don’t know if it might react incorrectly to nmap activity and so on).
other than that - it would be useful to know how long you've had this trouble, whether you've tried reinstalling the product, other things around (as if it were a stable or 'temporarily' state, but it happens often) and so on.
Thanks!
-
-
i have the following message when trying to update the antivirus database:
F-Secure One Client
11.11.2025 waiting restart…
F-Secure One Client is usually about 'major' update/upgrade from one version to another (rather than AV database / engine / core). So, it looks like a certain update has not completed and you need to reboot your system to continue with it. Could you try to do it?
Although it might be strange if you haven't rebooted your system since 11.11.2025. Also, most often, such situations are resolved somehow 'automatically' (or per more 'visual' request), but something likely interfered with the installation or final stage of upgrading. Anyway, if rebooting the system doesn't help, can you try showing a screenshot of the situation.
// as well as some system specific details: what is your OS (Windows / macOS) and its version.
Thanks!
-
-
Hi,
For many years already now, shutting down computer does not reboot it. Windows has implemented a feature called hybrid sleep, where shutting down logs users out but hibernates the system. This means that system is resumed without restart when the computer is started again. In order to actually reboot the computer you need to select the reboot option instead of shut down.
Ville
F-Secure R&D, Desktop products
-
@madiccocom , thanks for your response and screenshot (and sorry for the delay with my reply).
as mentioned in the comment above: sometimes rebooting and turning off/on a computer (especially a laptop) can differ, because modern versions of Windows can have a so-called 'Fast Startup' option in power settings (I do, mostly, disable it via Control Panel: Hardware and sound — Power options — Power Button Actions — uncheck Fast Startup). Which (I don't know for sure, but I suspect so, since it describes a similar operating principle) is called above in the comment as hybrid sleep feature. Otherwise, shutdown is now always not equivalent to reboot.
Anyway, based on your screenshot:
- it has a bit of 'old' user interface;
- it may contains older Updates server (but likely is still 'fresh' enough);
- it contains older main core/engine (kind of things stuff);
The Ultralight-approach has now been replaced by the new technology design since F-Secure version *25.2 (released in March 2025), based on this What's New article. While your version could be something like 19.8 (released in November 2024).
So I don't quite know how to explain the situation exactly. It looks like you were still receiving updates to the old "infrastructure" until the very end.
Also, your listed "One Client" is 6.7.363 version which is not really old and not entirely the latest (but I can't check what is the latest stable one). Thus, I would consider that the reboot request / waiting restart should have already been many times/days/months (like if in September, October but for older One Client received updates).
And sounds that your installation is tried to upgrade from something like F-Secure 19.8 to the most current build like F-Secure 25.11 with replacement old approach to new approach. Which may in itself be a problem or a breaking point.
I also don't know how someone could get into such a setup. For example, leaving the laptop unused for a long time (many months), and then periodically turning it on and using it. And not receiving any kind of "update" notification or direct reboot request. And in general, how normal is the situation? Maybe if your laptop is ARM-based (processor), then if it is a faulty situation where reboot will not help - one of releases were 'unsupported' and maybe some stuck happens (but it is a fantasy-like thought).
Therefore, I would suggest the following: try rebooting the system. If that doesn't help, then if possible, and have a backup of things like Password Vault, reinstall F-Secure (if there's some kind of glitch). Or better to contact support or wait for more official answers in the Community.
Maybe @Ville can look at your screenshot and either confirm 'strange' set-up or suggest something better.
Thanks!
// Sorry for the unnecessary length.
-
-
