Just as generic suggestions (addition to discussion):
-> good to doublecheck that platform is still supported by F-Secure solution.
Otherwise, update is not applicable maybe.
-> for except noted 'should update itself' flow - possible to try trigger receiving fresh build by reinstallaton.
Usually, fresh installation is about most recent available build.
Installation flow for Windows:
-> if concern is about databases/signatures - good to doublecheck that network connection is OK, proxy is not used or proxy is configured properly.
Each hour - solution should to check updates, but possible to check it manually:
-> if concern is about "renew subscription" or switch to another package - there are some Knowledgebase articles:
My computer still has the following software installed: Safe 17.4.
No final version of the next software:17.5 (with Avira)?
What's Avira got to do with it? If you have two anti-virus products installed on your machine, then neither will work properly, so you need to choose between one or the other.
F-Secure 17.5 beta 10 (now with Avira signatures)
Interesting thread, thanks. I must admit I wasn't aware of any of that, so perhaps I need to pay more attention.
I don't think they have released 17.5 as stable version yet, but i hope they will soon.
There was a message in beta forums that there was some server reconfiguration issues in december and that it should be released as stable version early this year, so all we can do is wait.