Jump to content

bazzaman

Experienced Members
  • Posts

    17
  • Joined

  • Last visited

Posts posted by bazzaman

  1. A couple of threads have reported issues with Opera browser cleaning in recent versions of Ccleaner

       https://community.ccleaner.com/topic/65812-cookies-not-showing-up-or-being-cleaned-in-opera-browser/

       https://community.ccleaner.com/topic/65286-ccleaner-615-doesnt-clean-opera-102/?tab=comments

    I would go further than the above and find that whole swathes of cleaning for Opera is now being missed due to updates to Opera (and these issues still persist in Ccleaner 6.18.10838).

    The browser cache is not being cleared as it's location has been moved.

    The default paths for saves (such Save Image) are not being reset to default.

    Browsing history is not being cleared

    Seems to me that a complete review of Ccleaner's interaction with the Opera environment needs a review / refresh.

    Be very grateful if this could be done soon as it's been an issue for quite some time now.

    Regards,
    bazzaman

  2. Thanks for the replies.

    I don't have Ccleaner set-up to auto-update (quite the opposite - including disabling the Ccleaner Update scheduled task, as well as unchecking "Keep Ccleaner updated automatically" and "Send notifications when there is a new version of CCleaner").

    It is not launching Ccleaner that gives the issue, but seemingly only running the main cleaning function - either just "Analyze" or "Run Cleaner" (or running ccleane64.exe /auto) .

    By contrast, doing a Registry scan / clean-up does not invoke the Restart Manager. I've not tried any of functions under Tools as these are not capabilities that I use at all.

    I find it perplexing that running these cleaning functions should cause this effect - is there any meaningful explanation as to why this is occurring?

     

     

  3. I'm using Ccleaner (Free), latest version.

    Whist browsing through Windows Event Viewer (Windows Logs, Application) I noticed a huge number of events (10000 & 10001) for Restart Manager.

    Having investigated further I see that these occur (typically two or three of each of 10000 & 10001) whenever I invoke Ccleaner to do a standard cleaning pass. Further investigation shows that this has been happening since I upgraded to Windows 10 21H2 (which I did in January this year).

    I can't be certain that all of these events relate to use of Ccleaner, but I suspect that they are. They make up about 25% of the events in the Application log.

    Any explanations as to what is going on (and, in particular, should it be happening)?

  4. For Chrome and Opera (and so possibly for other Chromium based browsers) since v5.67 Ccleaner is not resetting download folders to my defaults.

    I have the Chrome and Opera default download folders settings saved (in Chrome and Opera respectively) as D:\BrowserDownloads\Chrome and D:\BrowserDownloads\Opera. But I often modify the download locations 'on the fly' so as to save individual files directly elsewhere. Previously (in 5.66 for example) Ccleaner correctly reset the these to the my saved defaults. This no longer happens with 5.67 (they are just left wherever I last saved to).

    The same issue arose several years ago and I reported it then (and it was quickly fixed). I can't refer you back to the old thread as it seems that it is no longer on the current forum.

    If I revert back to 5.66 (just by reinstalling 5.66, otherwise leaving all settings the same) all works fine again.

    Other info

    Windows 10 1909
    Using CCleaner Custom Clean
    Window Defender AV / Comodo FW
    Chrome and Opera NOT Sync'd (don't even have accounts with them)

     

     

  5. Many thanks for the update.

     

    A couple of pertinent points:

     

    I have read through the Avast blog. It states "we released a fixed version 5.33.6163, identical to 5.33.6162 but with the backdoor removed, and pushed this version as a lightweight automatic update to CCleaner users where it was possible, further reducing the number of impacted customers. We notified the remaining users to upgrade to the latest version of the product as soon as possible (unfortunately, we weren’t able to update the free CCleaner users automatically as the free version doesn’t contain the auto-update functionality)."

     

    I particularly draw your attention to the part I have highlighted in bold. I have the free version AND it was updated automatically to 5.33.3163. Inevitably such incorrect statements by Avast only give further cause for concern. I'm guessing that they should have stated something along the lines of:- unfortunately, we weren’t able to update the free CCleaner users automatically as the free version doesn’t contain the auto-update functionality with the exception that if such users were also Avast users, Avast pushed the 5.33.3613 out via the Avast Emergency Update functionality.

     

    For my part, hopefully I was not exposed as I am assuming that the malicious code was only executable from Ccleaner.exe (not the installer that installed the Ccleaner.exe). As my firewall (Comodo) is setup to block Ccleaner.exe from having Internet access, even if the malicious code had run it would not have been able to reach the outside world (unless it managed to use the "offices" of some other service). Unfortunately, Comodo (like some other contemporary firewalls) uses Trusted Vendor lists and automatically allows Internet access to software from such vendors and so allows the installers access without even asking.

  6. We have a separate staff only discussion about it, and I gave a link very early this morning to your topic -- which instantly came to mind. If they obtain any information about that strange version you had that isn't in any change logs hopefully they'll post about it in here.

     

    I have added a bit more information to my thread at: https://forum.piriform.com/index.php?showtopic=48859

  7. I've been able to recreate the environment that gave rise to the unexpected 5.33.3163 version of Ccleaner and revisited virustotal. The hash is SHA-256 c48b9db429e5f0284481b4611bb5b69fb6d5f9ce0d23dcc4e4bf63d97b883fb2

     

    In the recreated environment, Avast Emergency Update ran just at the point that 5.33.3163 got installed. This may or may not be relevant.

     

    I also have the pertinent ccleaner.exe (securely encrypted to avoid any mishaps).

  8. I have 2 PCs (desktop and lappie), both running Win7 32 bit, with Chrome. Both had Ccleaner (free) installed (5.33.3162) and automatic checking for updates turned off.

     

    Yesterday both machines suddenly and without any warning got updated to 5.33.3163. I quickly noticed this because my shortcuts to Ccleaner (on Quick Launch bar) lost their Ccleaner icons and stopped working.

     

    Being concerned I uploaded the updated 5.33.3163 Ccleaner.exe to virustotal.com (no issues found).

     

    I also checked the Ccleaner version history ( https://www.piriform.com/ccleaner/version-history ) - no mention of 5.33.3163.

     

    I also happened to notice that Chrome had been updated around the same time. So this got me wondering whether Piriform have somehow got into cahoots with Google and Chrome is now installing (or at least updating) versions of Ccleaner without any warning or notification?

     

    Intriguingly, the Chrome version updated to was 61.0.3163.91 - i.e. also including the digit sequence 3163

     

    I got round it in the end by downloading 5.34.6207, disconnecting from Internet, restoring a system partition image, installing 5.34.6207 and then reconnecting to the Internet. But will Chrome (if it is the culprit) continue to update Ccleaner in future?

     

    Can anyone shed more light please?

  9. Thanks for the reply. I rarely use IE myself, but sometimes Chrome does not do the job and have to revert to IE.

     

    However, by way of further information, the Ccleaner issue arises even when IE has not been used (since last run of Control Panel > Internet Options, Delete). Now, it may be that something else is "sharing" the same capabilities (History) as IE (Thunderbird?) or it may be that issue with using Cleaner arises regardless (of whether there is any IE History to clean).

  10. Seems this issue has still not been addressed. Just upgraded to latest (5.33.6162) and problem still occurs, so have had to leave Internet Explorer - History unchecked.

     

    Does anyone have any update on this issue at all?

     

    Please note what I said in earlier posting "But what is interesting (to me at least) is if I use Control Panel, Internet Options, Delete.... to delete IE History, that zooms straight through it - so why can't Ccleaner?"

  11. My experience (for what it's worth) on Win7 32 bit (and I mostly use Chrome, rarely use IE, but do use Thunderbird):

     

    Using Ccleaner 5.20 - runs fine.

     

    Update to 5.24 (and subsequently to 5.26), Ccleaner stalls for quite a while while cleaning IE History, but eventually completes. Note that IE not running (most of the time it won't have been launched since boot).

     

    If I uncheck History under Internet Explorer, Ccleaner zooms along fine.

     

    But what is interesting (to me at least) is if I use Control Panel, Internet Options, Delete.... to delete IE History, that zooms straight through it - so why can't Ccleaner?

     

    Does any of that shed any light (on a possible Ccleaner solution)? 

  12. Have just installed latest version (3.06.1433) and see that some Chrome items are not being cleaned.

     

    Previously (2 versions back, in 3.04.1389), Speed Dial info (in Chrome's Top Sites file), Chrome's History file and Chrome's DNS cache (as evidenced in the dns_prefetching section of Chrome's Preferences file) were not being cleared. As workarounds, I created a batch file that ran Ccleaner with /auto and then deleted both Top Sites and History files. Only way I could address the DNS cache issue was to turn Chrome's DNS pre-fetching feature off and on a couple of times and then leave it off so that Chrome flushed the dns_prefetching section of Preferences and didn't re-populate it.

     

    Latest version of Ccleaner seems to have addressed only the Top Sites issue. I've been deleting the History file as well (in the afore-mentioned manner), with no apparent side effects. Could the History file be deleted by Ccleaner as well please?

     

    As for the DNS cache, I'm not sure how much value this is and whether the Windows DNS cache comes in to effect as well anyhow. But concentrating on the Chrome cache, it would be good if Ccleaner could purge it anyhow, so that Chrome's DNS cache facility can be left turned on with the proviso that any benefit the cache has can only be gleaned between runs of Ccleaner.

     

    BTW, I run WinXP SP3 with latest Chrome.

     

    Thanks.

×
×
  • Create New...

Important Information

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