Jump to content

MeganCCleaner

Admin
  • Posts

    123
  • Joined

  • Last visited

Everything posted by MeganCCleaner

  1. Hi @robertpri We've become aware of how in certain situations, disabling the "Start Kamo when I start my computer" option does not work correctly, exactly as you are describing. However this should be fully resolved in the next update we release for the software, which should be available in the near future. Meanwhile, you can resolve this by deleting the update task Kamo uses, as follows: Open the "Run" dialog in Windows (On the keyboard, hold the "Windows" () and "R" keys simultaneously) Type: taskschd.msc > click OK Expand "Task Scheduler Library" > open the "Kamo" folder Right-click on the "KamoStart" entry > click "Disable" Or if that doesn't work, can you please "Delete" the "KamoStart" entry, instead? Simply right-click on the entry > click Delete > Yes.
  2. Hi @Skybat First of all, I am very sorry to hear of how you experienced this problem as a result of using the Driver Updater; I'll immediately report this to our development team as we definitely do not want anyone to have this type of experience when using our software. To help us with the investigation, would you be willing to send the following files to our support team, using support@ccleaner.com ? C:\Program Files\CCleaner\Data\ DUState.dat C:\Program Files\CCleaner\LOG\ DriverUpdaterLib.log C:\Windows\INF\ setupapi.dev.log
  3. Hi @robertpriYou can prevent Kamo from auto-starting by configuring it as follows: Open Kamo > click Menu > SETTINGS Uncheck "Start Kamo when I start my computer" If it continues to auto-start after disabling this setting, please let me know as we've become aware of an issue that has affected a small number of our users, which results in this option not working properly, and I'll be more than happy to provide further insight on that.
  4. Hi @robertpri The exception you created did not work because unfortunately, the "Allowed websites" area of Kamo solely correlates with "Browser cleanup". Specifically, the "Browser cleanup" feature will delete website cookies, and "Whitelisted websites" allows you to specify which websites cookies should be retained when using Browser cleanup. This means it won't allow for you to prevent Kamo from blocking a website and instead, it will only allow you to prevent website cookies from being deleted. However I am glad to say our development team confirmed they are currently working on making it possible to create website exceptions for the browser protection/anti-tracking mechanism of Kamo, at which time problems like this can be easily resolved. Meanwhile, can you please tell me what websites you are unable to access when Kamo is running?
  5. Hi @Martin71 We had become aware of this type of issue occurring in certain types of circumstances and the problem was fully resolved in the v2.3 update we released for Kamo on August 18th. You can install this update using the following steps: Open Kamo > click Menu > SETTINGS Click "UPDATE NOW" However if the problem has persisted in the new update, our support team would be eager to investigate further. You can easily contact them via email, using support@ccleaner.com.
  6. Hi @phobden Our support team would like to investigate further. Do they have permission to contact you via email, using the same address registered to your forums account?
  7. Hi @Mineria CCleaner uses the "Release date" to determine what driver updates are available, rather than the version number and in some cases, a newer driver may actually have a smaller version number because of how different manufacturers use different numbering ranges. For example, for a Intel device on Windows 10, the version of a default Microsoft driver can be 10.0.19041.1 (date: 06/21/2006), but the newer driver supplied by Intel may have a driver version 9.4.0.1025 (date 07/31/2013). The Intel driver is preferred because its release date has a higher priority. You can view the release dates in the CCleaner UI by clicking the "Learn more" button located next to each driver that has been identified.
  8. Hi @Martin71 Our support team would like to help with this. Do they have permission to contact you via email, using the same address that is registered to your forums account?
  9. Hi @greenscreen45 I wanted to follow-up with you on this as I suspect this problem was resolved in the new update we released for Kamo on August 18th. If needed, you can install this update using the following steps: Open Kamo > click Menu > SETTINGS Click "UPDATE NOW" Otherwise if these problems have persisted in the new version of Kamo, our support team would like to investigate further. Do they have permission to contact you via email, using the same address that is registered to your forums account?
  10. Concerning the issues you are experiencing with the Driver Updater, our support team would like to investigate further. Do they have permission to contact you via email, using the same address that is registered to your forums account?
  11. Hi @Andy Bell I suspect that all of these issues are attributed to the network connectivity problem you have described. This is something our development team recently became aware of and they are currently working towards getting this resolved. Would we have permission to follow-up with you on this via email, using the same address registered to your forums account, when we have further insight on the issue?
  12. Hi @Anthony Dean Concerning how CCleaner choses the 32-bit version of WinRar when the 64-bit version is installed, our development team is now investigating the issue and working towards getting this problem resolved. Additionally, our team confirmed they were already able to resolve the file version issue you saw so the 32-bit update will be displayed correctly, as v6.0.2. If you happen to notice any other issues, please let us know; we greatly appreciate you for reporting these problems to us!
  13. Hi @jSan I've now discovered this is a problem our development team has become aware of and they are currently working towards getting this resolved. I'll follow-up with you again as soon as I have further insight on this.
  14. Hi @pezinbristol Concerning the shutdown issue, this has been resolved in the new version of Kamo we released yesterday, v2.2. To install this new version, simply open Kamo > click Menu > SETTINGS > UPDATE NOW. Otherwise we are not aware of any issues that was cause Kamo to frequently hang in the way you've described. If this problem has persisted in the new version of Kamo, can you please send the following log file to our support team, using support@ccleaner.com ? C:\Program Files (x86)\Kamo\Support\Log\ ErrorLog_[date].txt
  15. Hi @Nerdbucket Although it is not currently possible to create exceptions for websites via the anti-tracking mechanism of Kamo, this is something we are planning for so it should be much easier to avoid issues like this in the future. Meanwhile, I'll inform our development team of how Kamo blocks two-factor access on https://www.chase.com/ as this is definitely something we'll need to fix, and we greatly appreciate you for bringing this to our attention.
  16. Hi @jSan I am very sorry to hear of how the Kamo filter process is interfering with your network connectivity, forcing you to terminate the process in order to regain access. Has this problem persisted in the new version of Kamo we released yesterday, v2.2? To install this, simply open Kamo > click Menu > SETTINGS > UPDATE NOW If so, can you please send the following log file to our support team, using support@ccleaner.com ? C:\Program Files (x86)\Kamo\Support\Log\ ErrorLog_[date].txt
  17. Hi @SteveM65 Thanks for letting me know as I am delighted to hear that problem was resolved for you! I've not yet been able to replicate the other issue in regards to the "Start Kamo when I start my computer" and "Minimize Kamo upon starting" options so it may need further testing and investigation. May we contact you via email, using the same address registered to your forums account?
  18. Hi @Anthony Dean Exactly as you've noticed, we use release dates as criteria for driver updates, rather than version numbers, and in some cases a newer driver may actually have a smaller version number because of how different manufacturers use different numbering ranges. For example, for a Intel device on Windows 10, the version of a default Microsoft driver can be 10.0.19041.1 (date: 06/21/2006), but the newer driver supplied by Intel may have a driver version 9.4.0.1025 (date 07/31/2013). The Intel driver is preferred because its release date has a higher priority. However I can definitely understand your concern with this and I also feel as though it would be ideal for the end user to have an option to select their preference; I'll send all of this feedback directly over to our management team for further review, and as a suggestion.
  19. Hi @Bill R First of all, we're very sorry to hear about how this happened as we definitely do not want anyone to have this type of experience with the Driver Updater. To help us investigate further, can you please send the following files to our support team, using support@ccleaner.com? C:\Program Files\CCleaner\Data\ DUState.dat C:\Program Files\CCleaner\LOG\ DriverUpdaterLib.log C:\Windows\INF\ setupapi.dev.log Additionally, would you be willing to send them a report from the System Information utility in Windows? You can save the System Information report using the following steps: Open the "Run" dialog in Windows (On the keyboard, hold the "Windows" () and "R" keys simultaneously) Type: msinfo32.exe > click OK Click File > Save...
  20. Hi @SteveM65 I wanted to follow-up with you on this again as the new version of Kamo, v2.2, has now been released. You can immediately install the new version of Kamo using the following steps: Open Kamo > click Menu > SETTINGS Click "UPDATE NOW"
  21. Hi @SteveM65 I'm glad to say that all update installations occur in the background, and they automatically replace the existing version, so it should be a 'hassle-free' process. By default, Kamo is configured to automatically update itself; simply ensure the auto-update feature is enabled, using these steps: Open Kamo > click Menu > SETTINGS Check "Automatically update Kamo" Otherwise if you would prefer to manually install updates, you can instead use the "CHECK FOR UPDATES" button located in that area of the program. (This will allow you to manually consent to each update installation, rather than having then automatically installed without your given consent)
  22. Hi @Bob J I discovered that our support team replied to your message on July 23rd, July 26th, and again today on July 27th so it seems as though you may not be receiving our emails. Can you please check to see if our emails were delivered to your Spam folder and/or perform a search in your inbox for "support@ccleaner.com" to see if this will allow for you to find our messages?
  23. Hi @SteveM65 & @pezinbristol I'm glad to say our development team has identified the cause of this problem and it will be resolved in the next version of Kamo we release, v2.2, which should be made available in the coming weeks.
  24. Hi @Mike Roh Can you please tell us what CCleaner displays as the "Release date" for the driver update that is being offered? This will be displayed after clicking on the "Learn more" button. Furthermore, and to help us investigate further, can you please send the following files to support@ccleaner.com ? C:\Program Files\CCleaner\LOG\DriverUpdaterLib.log C:\Program Files\CCleaner\Data\DUState.dat C:\Windows\INF\setupapi.dev.log Please also send a report from the System Information utility in Windows: Open the "Run" dialog in Windows (On the keyboard, hold the "Windows" () and "R" keys simultaneously) Type: msinfo32.exe > click OK Click File > Save...
  25. Hi @SarahC Thanks for the updates on this situation as we're delighted to hear that you solved the problem by reinstalling Kamo. Also, I'll inform our development team of how this happened as we definitely don't want anyone to experience this problem following an update installation.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.