Failure to update update Freedome to v. 220.127.116.11
[NOTE: This is about the update of Freedome, NOT about today's critical update of SAFE.]
- When starting my computer (PC, Windows10, current Freedome version 2.45.888.0) yesterday, I got a pop-up (now on every boot) telling me that an update (18.104.22.168) is available. I clicked on the "Install" button, and that started a process F*_updater.exe (seen in Process Explorer; but can't remember if it was "F-Secure_updater.exe" or "Freedome_updater.exe", and strangely cannot find the EXE file in the F-secure folder tree).
- After a while I got another pop-up saying (something like) "Services need to be stopped which requires admin rights".
- I was logged in as admin and granted those rights (Win10 UAC pop-up).
- After another while, another pop-up appeared, now saying that "Unfortunately restarting the application didn't solve the problem. Please reboot your machine and try again."
- However, after rebooting, the same sequence as above happened again.
- I then discovered (Win10 Computer Management) that the "F_Secure Freedom Service" was in "Stopping" state but never actually finished and went to "Stopped". It could not be set to Manual and then stopped manually either. However, I don't know if this is the cause of the update failure.
- NOTE: I did not get any message about "Unknown error", so this Knowledge Base article does not seem to apply. (Besides, by now the installer would certainly warn against this anyway, and not just leave it to the user to find this article?)
- Further I found that in the whole struggle (I may have clicked various "Install" buttons more than once), no less than four (4!) identical folders had been created/downloaded in the Freedome folder tree, with identical content and a volume of 165 MB each:
- C:\Program Files (x86)\F-Secure\Freedome\Freedome\1.1 to ....\1.4
After rebooting again, I can now at least still run the older version (2.45.888.0) of Freedome.
But for how long? And how to achieve a successful update?
I don't want simply to try again and again if that each time triggers yet another 165 MB download.
Would it perhaps help to manually stop the "F_Secure Freedom Service" before running the installer (if that is at all possible; it may of course have special protection)?
Thanks in advance for your help.