F-Secure 25.8 Language/Notifier Issue
Good day, my F-Secure was updated to version 25.8 today, and I noticed that the notifier display looks strange (from system update to VPN notifier display, see below).
My language installation preference is Traditional Chinese (Hong Kong). May I ask if anyone here has encountered the same problem?
Also, may I confirm if this is just a translation issue and whether it is still safe to use without any problems? I will have at least 10–15 devices that will be upgraded soon, depending on the timing. Otherwise, will this be corrected in version 25.9?
Answers
-
Ok, I tracked it down a bit more. Looks like we have a problem in our localization pipeline and notification localizations are missing for all languages except English. We are working on a fix - the fix does not require app update, it will just come silently.
Ville
F-Secure R&D, Desktop products
-
VPN does not work on my computer. When putting it only, the waiting symbol is spinning and it also cut the Internet connection and while I wait for the VPN I can not use the browser. What can I do? Please help me. Thanks a lot.
For the most correct and accurate advice, it would be better to know some additional things:
- what is your operating system (like Windows, macOS; which version of it)?
- what is your F-Secure solution and its version (like F-Secure TOTAL, F-Secure VPN)?
- were there any changes in the system that caused this problem to occur?
- your problem is that "VPN does not work" (like 'at all') or "while you wait for the VPN - you can't use the browser"?
Just as a general suggestions: to not cut the Internet connection while F-Secure is trying to establish a VPN 'network' - you may try to disable Killswitch feature (Blocking internet access when VPN is disrupted or is being established).
If it is constantly rotating in the "Waiting" state (like 'activating' phase), you can try using other protocols (Changing the VPN protocol used). For example, start with Hydra. Then, with WireGuard. Then with OpenVPN options.
If all protocols have this problem, then try connecting to another spot (selecting another location, another server for connection). Not the one(s) you have tried.
If nothing helps, have you tried, for example, rebooting the system, waiting for a few minutes and then using a VPN?
If all the basic steps did not help, you can try reading the official knowledge base article about common ways to 'reset' the configuration and some other extra basic steps to try:
This would help to understand whether there is a connection with a specific network (for example, if the ISP does not allow the use of certain ports or certain types of solutions such as VPN), and also that there has not been some kind of failure in the system - which can be fixed by the actions described in the instructions (something like an alternative to simply reinstalling the product).
// forgot to mention that you can check that all F-Secure services (VPN related) are up and running. By accessing list of services and check their status. I think, there are two of them: fsvpnsvc and fsvpnextsvc (at least, on Windows machine).
Thanks!
-
Ukko:
I have an Acer Aspire A515-44 ,Processor AMD Ryzen 5 4500U with Radeon Graphics 2.38 GHz
Installerat RAM-minne16,0 GB, System type 64-bitars OS, x64-baserad processor
Windows 11 Home, Acer Aspire A515-44
ProcessorAMD Ryzen 5 4500U with Radeon Graphics 2.38 GHz
Installerat RAM-minne16,0 GB (15,4 GB går att använda)
Systemtyp64-bitars operativsystem, x64-baserad processor
Windows 11 Home Version23H2
Before consulting you, I had already disconnected the Killswitch. Then I could use my internet. Then I tried the four VPN protocols but none of then worked.
I have followed your recommendation and I have read how to reset the configuration but I get only this:
Microsoft Windows [version 10.0.22631.5472]
(c) Microsoft Corporation. With exclusive rights.
C: \ Windows \ System32> IPCONFIG /FLUSHDNS
Windows IP Configuration
Successfully flushed the dns resolver cache.
C: \ Windows \ System32> Netsh Winsock Recovery
The Following Command was not found: Winsock recovery.
C: \ Windows \ System32> Netsh Int IPV6 Recovery
The Following Command was Not Found: int ipv6 Återställning.
C: \ Windows \ System32>
After this I restarted the computer, despite not completing the process, in the hope that the problem would have solved but it was not so.
Is it a problem with my computer? All other programs work perfectly.
What can I do?
Thank you for your help. -
I have followed your recommendation and I have read how to reset the configuration but I get only this:
Microsoft Windows [version 10.0.22631.5472]
(c) Microsoft Corporation. With exclusive rights.
C: \ Windows \ System32> IPCONFIG /FLUSHDNS
Windows IP Configuration
Successfully flushed the dns resolver cache.
C: \ Windows \ System32> Netsh Winsock Recovery
The Following Command was not found: Winsock recovery.
C: \ Windows \ System32> Netsh Int IPV6 Recovery
The Following Command was Not Found: int ipv6 Återställning.
C: \ Windows \ System32>
…
I have solved the problem with the VPN. I followed the instructions to reinstall fs protection and finally I could use the VPN. Thank you very much for your help.
Hello, @Ericvar
Sorry for the late reply.
Right away - it is good that you managed to fix the situation and reinstallation helped (I hope without any aggravating circumstances).
I just thought I'd try to mention the reason for the inability to execute the commands you provided. I think the problem is in the writing. You used it like "Netsh Winsock Recovery", but the working form is (likely) just "netsh winsock reset" (as I see it in KB article). So, I am not sure when 'recovery' comes in (they are also expected to be in English when putting into the command line).
So, both lines are expected to be like "netsh winsock reset" and
"netsh int ipv6 reset" instead of 'recovery' in it (and I am not sure if they are case sensitive). Thus, I think all is fine with your system; but something wrong was with network (VPN-related) configuration (maybe VPN network adapter).Thus, I think that it might be good that the situation was corrected by reinstalling F-Secure (more reliably).
Thanks!
