Again the same random problem: Freedome did not start automatically this afternoon, when waking the pc out of sleep; a manual start was necessary to initiate the program. Why is this, sometimes Freedome wakes up from sleep automatically, sometimes not?
This is just to repeat my message of Jan 25: when waking up my pc (Win 10, updated) from sleep/hibernation, Freedome sometimes comes on automatically, sometimes not. I have not been able to determine any pattern in this random behaviour. I thought that the latest update to Freedome (ver. 1.3.2906.0) might correct this, but unfortunately this is not the case.
I experienced this problem again today acoompanied by this error message (in Finnish):
"VPN alustusvirhe. Salatun VPN yhteyden luominen ei onnistu verkkoasetuksissa olevien ongelmien vuoksi (netsh.exe palautti virheen). Tarkista, että IPV6-liikenne on otettu käyttöön."
I checked the network settings and IPv6 was marked with x (on); so that could not be the reason for this error. There surely was something amiss, since Freedome could not be turned on from the program itself. However, a restart of the pc did the trick: Freedome came on by itself after the restart without further ado.
This problem is annoying and something should be done to remedy it preferably sonner than later.
A restart of the pc was enough to
Looks like it's been fixed! I recently upgraded to 1.3.2906.0. Since then Freedome has always started after my computer comes out of both Sleep and Hibernation. I've tested them both a dozen times over several days and everything looks good. Please send my warm thanks to the devs for fixing this problem! Not auto-starting after Sleep and Hibernation was the only reason that kept me from installing Freedome on my family members' computers. Now that it's fixed, I feel comfortable setting it up for them. Thank you!!!!!
Problem came back - see below
Sorry to say, theoriginal problem persists, and from time to time (like today, once) Freedome does not come on automatically though it most of the time does. The error message refers to IPv6-problem (on checking the network connections I found that FreedomeVPNConnection was marked with red cross meaning it was off); this happened during a period of sleep/hibernation lasting about one hour. Seems there is still some checking to be done by the Freedome team at F-Secure!
Win 10, latest updates, Freedome 1.3.2906.0.
If the issue persists with the latest version, could you open a support ticket so we can look better into it?
Looks like I spoke too soon, the same problem happened again a little while ago - my Windows computer came out of Hibernation and Freedome didn't auto start. That's too bad, it had been working flawlessly since the update.
I can open a ticket but I'm not comfortable sending the entire FSDIAG.ZIP - it contains too much identifying information about my computer. Are there specific files I can send instead of sending the entire ZIP package?
Update - since my last post, the problem has not happened again. It could be that the one time Freedome didn't start was because I didn't have it connected when I shut the computer down.
I'll keep a close on it and post again if I experience any more problems.
For me, on my laptop Freedome usually reconnects VPN after sleep mode. On my desktop computer, it never does. Version is currently 1.3.2906.0, but have had the problem for several months, ever since I started using Freedome. Because I generally forget to turn it on manually, I'm "unprotected" most of the time...
Windows 10 on both machines, by the way. On my secondary HTPC desktop computer with Win7 64-bit the **bleep** thing won't even work at all because some driver wasn't signed and wouldn't install.
This topic has been closed due to inactivity. If you would like to discuss this topic further, please start a new post.
You can reference this topic in your post by adding this link: