Using Windows 10 Pro, After the Nov 17th, 2022, Kamo update version 4.6.891.1424, starts fine, except Private Connection that used to start Automatically does not. I have to manually turn on the Private Connection and re-checkmark all the box settings after every system boot or restart.
Everything was working fine before the program update, I also checked Task Scheduler which shows Kamo task was updated on 11/17/2022. And is no different from the previous scheduled Task setting. Is this a program change or an error in the software coding, seems like the settings are not being saved for Protection Connection being ON or OFF.
Hi @FrancisT First of all, I'm sorry to hear of how Private Connection no longer automatically starts following the recent update we released for Kamo.
To help us investigate further, would you be willing to send us your log files?
You can save the log files using these steps:
Open Kamo > click Menu > HELP
Click "SAVE LOGS"
Afterwards, a File Explorer window will appear with the kamo_logs.zip file highlighted; please email these to our support team, using support@ccleaner.com.
We've been able to replicate the problem so our development team is currently investigating the issue, and there is no longer any need to send us any logs.
I will follow-up with you as soon as I have further insight on this and/or when I have a confirmation the problem will be resolved.
I look forward to being in contact with you again soon and meanwhile, please don't hesitate to reply if anything else is needed.
I install Kamo 4.6.891.1424, but Private Connection does not function. A message appears: "We can't connect you to the Private Connection right now. Sorry, we're having technical issues."
Private Connection does not start automatically. I realy turn on: Automatically turn on Private Connection and Block Internet access, if Private Connection suddenly drops.
But... Private Connection only works if I turn it on manually. And if internet access suddenly drops, Kamo does not block internet access.
Our development team has been able to reproduce this problem and has found a fix for it. This is expected to be made available in an upcoming update.
Unfortunately, until that update can be made available, the connection will need to be enabled manually when you want to use it.
In regards to Golddigger, that doesn't sound like the same problem at all, as the reason the connection may not be able to be established is because you can't connect at all.
Can you provide more information on precisely what error you're receiving when you try to enable it?