Jump to content

Clean MisterB

Experienced Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by Clean MisterB

  1. On 21/10/2021 at 04:43, SumGuy said:

    Chrome 95 now has a baked-in feature called "copy link to highlight". It's been available for a while through one of Chrome's experimental flags, but it's currently enabled by default. No extension necessary:
    https://support.google.com/chrome/answer/10256233

    <snip>

    @SumGuy  Unfortunately, that Chrome feature is NOT the same.

    It allows for a raw link to the highlighted text for sure.

    However, the "Link to Text Fragment " Extension allows for either a raw link, or rich text link

    image.png.f5aae8b9d088049c2fe4af3b0c32e6e9.png

    The effect is shown in the attached Word doc

    Screen Capture test.docx

  2. 2 hours ago, nukecad said:

    I think that you are upsetting the dev there by suggesting that is coding may be 'incorrect'.

    It doesn't seem to be his coding at fault at all, it seems to be the way that Chrome works.
    (In testing it I don't get the same issue at all with Firefox).

    Rather than saying the coding is 'incorrect' you might be better saying that you've found this issue with Chrome and 3rd party cleaners, and asking if he could take a look.
    But TBH as it seems to work unless/until you clear the browser session by using something other than the browser itself he'll probably just suggest that you stop clearing the session that way. (See the PS)

    Presumably if you clear your session in Chrome itself the extension still works, so as far as the dev is concerned it's working properly and it's your use of a 3rd party cleaning tool that is the problem. That's a reasonable point of view.
    If Chrome itself was removing the context menu entry then that would be a different matter.

    As @MeganCCleaner said above:
     


    For what it's worth I took a look at that code.
    I don't speak java, or write browser extensions, but that code is just calling a function in the browser- "contextMenus.create()" and then doing some error trapping.

    The dev has no control over where the "contextMenus.create()" function is storing things, that's a function of the browser itself.
    https://developer.chrome.com/docs/extensions/reference/contextMenus/

    I think that this is something that has no real solution other than not clearing the session for Chrome.
    Whilst it does seem slightly odd that no-one has reported a similar issue before, that may simply be because there aren't that many browser extension that create context menu entries?

    PS. His comment about seeing ads for CCleaner on 'spurious' sites is misdirection, I've seen ads for Microsoft products on dodgy sites, so what?
    He's basically just saying - "Stop using CCleaner and you won't have this problem"

     

    Lol 😂 you're right @nukecad 

    Not really too bothered about upsetting the Dev - I'm just reporting what I see, and until that GitHub entry, I was happy to leave it be anyway;  as I pretty much said above it isn't a PROBLEM as such - more of an issue that, in a perfect world (!) wouldn't exist.

    I actually took slight exception to the suggestion that CCleaner was somehow to "blame" having used it for so long.  (I've seen plenty of those ads too!)

    I agree with your "I think that this is something that has no real solution other than not clearing the session for Chrome" - I just have this "OCD" approach to seeing problems through, especially when I was the one to raise them. 

  3. On 13/10/2021 at 09:59, nukecad said:

    It's sometimes the way that you are unable to stop 2 apps from clashing with with each other, and so just have to find the way that suits you if you want to use them both.
    Usually that means sacrificing a function in one or the other. In this case you've sacrificed the cleaning of sessions.

    At least having some understanding of why it's happening can help you decide which way you want to go.

    As you note with todays larger drives clearing junk to free up storage space is not the issue it once was, these days for most people it's more a case of wiping up your footprints to avoid the possibility of someone accessing the files and seeing where you have been.
    That's why most browser now have an option to delete history, cookies, etc. on closing, CCleaner goes a bit deeper with that cleaning.

    @nukecad

    Would you care to look at the GitHub thread - https://github.com/GoogleChromeLabs/link-to-text-fragment/issues/44#issuecomment-945816061

    The Context Menu code (along with subsequent comments)  has been posted for me, but it's FAR more appropriate for you!

  4. To @nukecad You said "I prefer to quote the relevant text fragment so that it can be quickly/easily seen without having to follow a link, and also give a link to the full article for those who want to follow up and see the full contents." As you know, that extension gives the heading and a link which is how I prefer to do it thus: Brexit: EU to reveal new proposals on Northern Ireland Protocol  taken randomly from the BBC. Again...IMO, I find that looks neater if I'm sending an email with a link.

    Of course, you also said  "Each to their own" a sentiment with which I most certainly agree and "(I have learned something new about Chrome for future reference)." Well raising this thread has taught me a fair bit about Chrome and CCleaner for future reference!

    I mentioned earlier that it's a few KB of space wasted so Google's issue of "Session State wasting valuable space" is, (again IMO) irrelevant  in these days of system partitions being hundreds of GB - I think that comment is a hangover from earlier years - I'm old enough to remember sub 100MB system drives!  Backing up that INI file is an excellent idea - I have got the "Save all settings" ticked - I think it's set by default.

    And @Andavari I 've come round to your way of thinking about Sessions - I did look at that community winapp2.ini file - I think I'll continue letting CCleaner create my own INI file - this being a case of "If it ain't broke......" we know the rest!

    All very educational and despite none of us actually being able to fix the issue, as the Author of the thread, I find the solution of simply not ticking "Sessions" the most practical and elegant. 

  5. 1 hour ago, Andavari said:

    When it comes to Chrome/Chromium based browsers it also helps to input an Exclude for their Local Extension Settings to prevent them from being tampered with. Those .log files and whatever else is in those folders can't be cleaned by 3rd party cleaning tools or anything outside of the browser or the addon/extension that created them.

     

    Examples:

    Edge Chromium:
    C:\Users\UserProfileName\AppData\Local\Microsoft\Edge\User Data\Default\Local Extension Settings

    SRWare Iron Portable:
    E:\PortableApps\IronPortable\Profile\Default\Local Extension Settings

    Well that implies that you think CCl;eaner "tampers" with Extensions as a matter of course which is what is actually happening here.  

    The folder you've suggested is, presumably Edge's equivalent of the Chrome folders discussed above.

    If everything "played nicely" i.e. Chrome / Edge, its Extensions and CCleaner that wouldn't matter.  What this fault demonstrates is that doesn't happen.

    What it looks like you're saying, is that parts of CCleaner, which is itself a 3rd party cleaning tool need to be defeated in order to prevent problems.

    One could (but I'm not) draw the inference that you're suggesting that CCeaner  "out of the box" isn't fit for purpose! 

    HOWEVER...As it happens, that "sessions" setting is UNticked by default on Edge (I have both Edge and Chrome on my machines), I'm now actually thinking, that I may have ticked it on Chrome myself at some stage. 

    The more I look at what "Session" does, the less use I see it being - @nukecad touched on this earlier and I just found his post here

    • Session – You can save the session and reopen it at a later time. Your Session contains all saved and opened tabs, so cleaning it will remove these tabs.

     Well my browsers are set to open specific pages at start-up so that facility is of little use to me - and if Chrome crashes, it asks you what to do (i.e. re-open last tabs or not)

    image.png.f18ecc29557b9596139428717af93acb.png

    Also, oddly, CC has  had similar issues a very long time ago 

    I paraphrase what I said above: 

    "Unless someone can give me a good reason to include Session, I'm inclined to leave it as it is (UNticked), rather than apply a workaround which makes the installation non-standard: saving 18kb of disk space is hardly worth any effort "

    Your thought on that would be interesting. 

    If anything, starting this thread has enlightened me to some of the stuff CCleaner does "under the bonnet" 😁

  6. 2 hours ago, MeganCCleaner said:

    Hi @Clean MisterB On my system, this problem occurs as a result of the following file being removed during the "Session" cleaning operation-

    C:\Users\[USERNAME]\AppData\Local\Google\Chrome\User Data\Default\Extension State\[number].log

    I'm not certain if this is something we can correct as it seems to be directly related to an oddity with how the extension stores data but in any situation, I will notify our development team of this issue to ensure they are also aware of the problem, just in case there is something we can do.

    Meanwhile, I would suggest that you manually exclude the file in CCleaner as a workaround to the problem, using the following steps:

    1. Open CCleaner > click Custom Clean
    2. Open the "Applications" tab
    3. Under Google Chrome, right-click "Session" > click Analyze Session
    4. Right-click the "Google Chrome - Session" cleaning result entry > click "View all files"
    5. Right-click the entry for C:\Users\[USERNAME]\AppData\Local\Google\Chrome\User Data\Default\Extension State\[number].log
    6. Click "Add to Exclude list"

    Thanks VERY much for jumping in on this @MeganCCleaner

    I took a screenshot of the result of the "View all files" that you suggested above (attached "Sessions - View all files")

    There was one file matching your description "\000010.log" so I Clicked "Add to Exclude list", restored the Sessions functionality and ran Custom Clean again
    Sessions were cleaned and the problem returned. 

    Just for fun (?) I readded the extension, left Sessions enabled, ran Custom Clean again and this time it kept the extension INTACT
    Ran Custom Clean again and AGAIN this time it kept the extension STILL INTACT. So I'm not sure why it didn't work first time around but it did on subsequent Custom Cleans.

    Then I removed the log file from the Exclude list, ran Custom Clean again and sure enough the problem returned.

    So yes your suggestion does restore the "Sessions" functionality PARTIALLY if you ignore the excluded log file, but I'd have to do it on several systems and I don't like non-standard setups where they can be avoided.

    Plus I'd be willing to bet that the problem would reappear after a CCleaner update or at least the potential is there!

    As I said above "To be perfectly honest, having played around with this and looked into it in greater detail, I'm content to leave "Sessions" deactivated if that's the only CCleaner functionality I'm losing".    

    It seems to me that it  doesn't do that much of importance - now if it was Cache or Cookies, that would be different.  The containing folder (Session Storage) only contains about 18kb of files, so it seems to me that the extension is of more use to me than the Sessions functionality.

    So bearing the above in mind, unless you can give me a good reason to include Session, I'm inclined to leave it as it is (UNticked), rather than apply a workaround which makes the installation non-standard. 

    Your thought on that would be interesting.

    Of course if the Devs come up with some new code, I'll give it a go!  (There is so far no response to my post on Github)

    Thanks again👍

    Sessions - View all files.JPG

  7. 11 hours ago, nukecad said:

    Just out of interest I decided to put that same extension on my Firefox and do a bit of testing.

    If/when I clear the Firefox 'session' information then the context menu entry remains in Firefox and still works as expected.
    (I used CCleaner first to clear the session, it didn't remove the context entry - and then as a double check I manualy deleted the session information files, still the CM entry remained).

    So it looks like your issue is specific to that extension CM entry when used in Chrome.

    One thing that I do note is that you can assign a keyboard shortcut, and that may still work even when the CM entry is not showing for you?
    If so it would be one way you could get around this issue, highlight the text and press the shortcut instead of right-clicking.

    EDIT. Here's how you set a keyboard shortcut for an extension in Chrome: https://chromeunboxed.com/quick-tip-create-shortcuts-for-you-chrome-extensions/

    Nice try but no cigar! 😄

    I did exactly as your link instructs, assigning Ctrl Z as the shortcut. It worked exactly as if I was using the context menu - I could use either, as you'd expect with a shortcut.  So far so good.

    However..... I then ran Custom Clean with "Sessions" enabled again. Same problem - extension present but doesn't work either with the CM or the new shortcut.

    Same fix - remove and re-add extension - all working, but of course the shortcut was removed along with the extension.

    To be perfectly honest, having played around with this and looked into it in greater detail, I'm content to leave "Sessions" deactivated if that's the only CCleaner functionality I'm losing. The extension is of more use to me than that particular functionality.

    Having said that I'm also happy to test any other suggestions anyone here may offer and if anything appears on Github, I'll test that too.

    As I'm sure we agree, bottom line...it shouldn't behave like this. It's a very naughty extension! 😂

  8. 2 hours ago, nukecad said:

    Yes it will stay open; we don't usually close threads unless there is a good reason to do so.

    I suppose at the moment it's a choice of how much you  want/need that extension whether you clear your sessions ot not.

    If you want/need both then it might be worth the time to do the testing?

    Sometimes things are just not compatible and you have to choose one or the other.

    Indeed..... that extension is VERY useful so as I said "I think I'm going to try running CCleaner without clearing Sessions for a while whilst at the same time monitoring Github"

    I presume that the CCleaner Devs and Testers see this forum so someone might have some more input. Naturally if I get any feedback via Github, I'll post it here.

    Thanks again for your time @nukecad

  9. 6 minutes ago, nukecad said:

    By more testing I was meaning you could try excluding the actual files/folders for the session information one by one, similar to what you did above but longer winded and you'd have to find where the files and folders are. (Probably: ...\appdata\....\chrome\... and so on).

    It will be interesting to see the response on github.

    I thought that might be what you meant -  that was what I meant by "there is likely a  (hidden) folder somewhere  to add to the "exclude" locations"   Thanks for clarifying. 👍

    When you get to that level, it's sometimes arguable whether the cure is more intrusive than the disease! Also, I've got 2 other machines  on the same Google account with the same Chrome extensions, so it's effort x 3. I think I'm going to try running CCleaner without clearing Sessions for a while whilst at the same time monitoring Github as you say.

    Will THIS thread remain open and allow for further comment if the wait is lengthy?

  10. 35 minutes ago, nukecad said:

    Good step by step testing.

    It is indeed telling us that it is the clearing of the Chrome 'Session' that is causing the context menu entry for that extension to dissapear.

    'Session' typically is the information about what Tabs you have open, what sites you are currently logged into, etc.
    So if you clear the browser session then you get logged out of all websites and your open tabs don't come back next time you open the browser.

    TBH I'm also at a loss as to why clearing the session information would remove a context menu entry, and if it is then why the extension wouldn't simply put it back when Chrome, and thus the extension, is launched again?

    The session information seems entirely the wrong place to be saving a context menu setting, (you would have thought that anything extension related should be saved  in the 'extensions' directory: C:\Users\[login_name]\AppData\Local\Google\Chrome\User Data\Default\Extensions),
    Bbut I can only think that the developer of the extension is doing it that way for some reason.
    Maybe he can't get it to work any other way in Chrome? (or maybe he has not realised it's being saved in the wrong place?)

    It may be worth reaching out the the developer of the extension, there is a page on github where you can raise issues and get answers:
    https://github.com/GoogleChromeLabs/link-to-text-fragment/issues

    If you are prepared to do some more testing yourself then you may be able to find which particular part of the session information the setting is being saved to and make that part of the information an 'Exclude' in CCleaner.
    No doubt the developer may be able to tell you that to save doing your own testing.

    Of course setting an exclusion would mean that CCleaner wouldn't clear anything else in that part of the session information either, so it may be simpler just not to clear the session at all.

     

    Thanks....again.... @nukecad

    Your paragraph "'Session' typically is the information about what Tabs you have open, what sites you are currently logged into, etc." makes perfect sense.

    NOT clearing Session therefore defeats one of my preferred reasons to use CCleaner  - need to think about that!

    As for:

    "The session information seems entirely the wrong place...."  - I agree - we sort of covered that earlier when I looked at the Startup > Context Menu tab and found nothing there.

    I don't quite understand what you mean by:

    If you are prepared to do some more testing yourself then you may be able to find which particular part of the session information the setting is being saved to and make that part of the information an 'Exclude' in CCleaner.  I think you're saying that  there is likely a  (hidden) folder somewhere  to add to the "exclude" locations??

     

    As suggested, I created myself a Github account and raised this issue Chrome Extension is disabled when running CCleaner Custom Clean #44

    I "cheated" by simply linking to this thread! 😄  I assume any Dev will find that sufficient. 

  11. So this is what I did:

    Searched for likely cookie in "Cookies on Computer" list - couldn't find one so:

    Deselect (Untick) all items in Chrome Settings Capture list
    Run Custom Clean
    Nothing in Chrome got cleaned - issue does not occur (ie Extension works correctly)

    Reactivate (Tick) Internet Cache and Internet History
    Run Custom Clean
    Appropriate items in Chrome got cleaned - issue does not occur (ie Extension works correctly)

    Reactivate (Tick) Internet Cache and Internet History AND Download History and Last Download Location
    Run Custom Clean
    Appropriate items in Chrome got cleaned - issue does not occur (ie Extension works correctly)

    Reactivate (Tick) Internet Cache and Internet History AND Download History and Last Download Location AND Session
    Run Custom Clean
    Appropriate items in Chrome got cleaned - issue OCCURS (ie Extension missing from Context Menu)

    Removed and readded Keep to Text Fragment Extension 
    Closed and reopened browser - Extension works correctly

    Reactivate (Tick) Internet Cache and Internet History AND Download History and Last Download Location AND Cookies
    Leave  Session UNticked
    Run Custom Clean
    Appropriate items in Chrome got cleaned  - issue does not occur (ie Extension works correctly)

    Run Custom Clean again (just to crosscheck)
    Appropriate items in Chrome got cleaned  - issue does not occur (ie Extension works correctly)

    Reactivate (Tick) Internet Cache and Internet History AND Download History and Last Download Location AND Cookies AND Session
    ie back to my original configuration
    Run Custom Clean again
    Appropriate items in Chrome got cleaned  - Appropriate items in Chrome got cleaned - issue OCCURS (ie Extension missing from Context Menu)

    Removed and readded Keep to Text Fragment Extension 
    Closed and reopened browser - Extension works correctly

    Left all items activated ie staying at my original configuration
    Run Custom Clean again
    Appropriate items in Chrome got cleaned  - Appropriate items in Chrome got cleaned - issue OCCURS (ie Extension missing from Context Menu)

    Removed and readded Keep to Text Fragment Extension 
    Closed and reopened browser - Extension works correctly

    Left all items activated EXCEPT Session
    Run Custom Clean again
    Closed and reopened browser - Extension works correctly

    *** Conclusion: Something in  "Session" is the culprit ***

    ===============================================

    According to this website:

     

    • Session – You can save the session and reopen it at a later time. Your Session contains all saved and opened tabs, so cleaning it will remove these tabs.

    I confess I do not understand why this should cause the issue as I also don't understand where the Session information is stored, and what the practical effect(s) of clearing or not clearing it is / are.

    Can anyone enlighten me please.

  12. 16 hours ago, nukecad said:

    It's a bit unusual being a context menu entry put there by a browser extension rather than by an app.

    I'm not sure just how the extension is doing that, and it may be putting something where you wouldn't expect it to be.

    As you say that excluding Chrome from Custom Clean stops it happening then I would test which particular component of the Chrome cleaning is removing it.

    To do that re-enable cleaning of Chrome and tick all the boxes.

    Make sure Chrome is closed then in Custom Clean right-click on the first Chrome component and clean just that one from the context menu (ie. Dont run a full clean), fire up Chrome and check to see if the context menu item is still there or not, if it is then close Chrome and in Custom Clean right-click/clear the next component.

    Do them one by one  checking Chrome after each until you find the one that is removing the context menu entry.

    PS. Obviously don't clear your saved passwords -- unless you want to.

    Thanks again.

    Did you see where I wrote above "You can see it shows up on the actual Context Menu, but CCleaner does not acknowledge it" ?

    ** That baffles me!! ** Because if CCleaner doesn't know its there, why does it get affected by a Clean operation in the first place?🥺

    You say "To do that re-enable cleaning of Chrome and tick all the boxes." Actually not all because if you look at the attached "CCleaner Chrome settings Capture" you can see how I have CCleaner set vis-a-vis Chrome. So not all settings are ticked anyway but with these settings, I get the problem.    

    However, you are right inasmuch as that must be my next step.     I was sort of hoping to avoid that but, as soon  as time permits.......

    CCleaner Chrome settings Capture.JPG

  13. 12 hours ago, nukecad said:

    That is an unusual one.

    You say the extension itself is still there and it's the entry on a context menu that dissapears.
    That makes me think that it's something other than simply Custom Clean clearing Chrome.

    Something is removing that context menu item, reinstalling the extension puts the menu entry back.

    I know that you say you only used Custom Clean but:

    There is a way to remove context menu entries in CCleaner, it's Tools>Startup>Context Menu where you can enable/disable context menu items.
    Of course you would know if you used that.

    Now the most likely way to unintentionally remove a context menu item - are you running the Registry Cleaner?
    Context menu entries are saved in the registry so an item dissapearing from a context menu can happen if you remove a registry entry.
    CCleaners Registry Cleaner may well remove a reg entry if it doesn't see it as being linked to an app that you have installed. (Which it won't be if it's for an extension).
    Reinstalling the extension would recreate the registry entry and put the context menu item back.
    (Which is all just as you describe happening).

    If it's neither of those then I may have a few other ideas.

    Thanks for responding @nukecad 👍

    In reply:

    You say the extension itself is still there and it's the entry on a context menu that disappears.   YES - see "From List of Extensions Capture" attached - this doesn't alter until I remove it to "fix" the problem

    ===================================================

    Under  Tools>Startup>Context Menu that particular extension doesn't actually appear. Attached screenshots taken when the Extension is actually working correctly!

    You can see it shows up on the actual Context Menu, but CCleaner does not acknowledge it - see attached captures

    ======================================================

    I very carefully avoided running Registry Cleaner when testing for this problem so as to isolate it. It most definitely happens after just running Custom Clean. In fact, if I exclude Chrome from the Custom Clean then the problem does not occur

    ===================================================

    Now, about those "other ideas" if you'd be so kind 😄

    Actual Context Menu Capture.JPG

    CCleaner Context Menu Capture.JPG

    From list of extensions Capture.JPG

  14. I have 21 extensions in my Chrome Browser.

    Included in these is "Link to Text Fragment" https://chrome.google.com/webstore/detail/link-to-text-fragment/pbcodcjpfjdpcineamnnmbkkmkdpajjg

    This appears in the (Right Click) context menu as described in above link.

    However, when I run CCleaner Custom Clean, this item disappears from the context menu. The ONLY way to get it to work again is to REMOVE AND REINSTALL the extension. I've tried Just switching it off and on again, refreshing pages, refreshing whole browser - nothing else works. 

    THIS IS CONSISTENT EVEN IF I REMOVE ALL OTHER EXTENSIONS

    None of the other extensions is impacted in this way so I'm at a loss to guess which CCleaner setting is responsible....or is it a bug?

    I have previously raised  a bug with Google here https://bugs.chromium.org/p/chromium/issues/detail?id=1246011#c18 but it does appear to me that it is CCleaner responsible. 

    Despite my  title to the Google bug, it's not intermittent, but reproducible simply by running CCleaner Custom Clean.

     

    Current versions:  

    Chrome is up to date
    Version 94.0.4606.81 (Official Build) (64-bit)
     
    CCleaner Free
     
    image.png.7e2074ca5533cba744a99b9d89e1cedf.png
     

    Any suggestions please?

  15. I  think people must be doing something wrong!

    I've always used the FREE version and because of the previous well-known issues I was still on  CCleaner 5.44.6575 until a few days ago.

    I'm now VERY aware of potential issues and look before I leap (install)

    I've just updated 3 PCs to CCleaner 5.51.6939 by downloading from the genuine site  http://www.ccleaner.com/ccleaner/download/standard and then manually installing it by clicking on the downloaded ccsetup551.exe file....as I always have done.

    Also I run the installations "customised" to prevent CC options from being added to the Recycle Bin Context Menu.

    No mention of Trial versions, Smart Cleaning was disabled by default (I was upgrading from a previous version as I mentioned and it kept my settings) and I have NO related Startup item in Task Manager, the only time a CCleaner process appears is when I run it!

    I'm the first to complain when things go wrong but in this instance CC is doing just what it should be doing. Btw....before anyone asks - NO - I have no connections with CC or Piriform other than as a user. ;)

  16. Much obliged to @nukecad and @mta

    A combination of your suggestions sounds like the way to go - i'll report back if I have any new findings. :D

    @nukecad I just tried your netstat suggestion -  now I need to do a bit of digging to find out what some of these mysterious  communications are about. I'm pleased to say that CC is NOT amongst them - that whole link contains some very interesting info .:)  Please see my UPDATE below

    One question for you both (as you both mention it)

     if you delete the ccupdate file, does that prevent the manual Check for updates button   image.png from working? 

    I've always found that even if CCleaner offers an update, whether automatically or after a manual check,one can choose to ignore it.

    Clearly, one must be aware aware that manually checking for updates results in a communication with Piriform. I would prefer to retain that facility - to me it's all about retaining control of what my devices do!

    One can then peruse Release notes, read here and other forums to make a decision - not that that should be necessary of course :huh:

    The problem with using the excellent cleanmgr, (which I use between Windows Feature Updates and Macrium images) is that I don't think it clears browsing history and cookies, for which I've always used CC on a daily basis.

  17. @Kernol   @mta  @Augeas

    I have NOT yet tried version of 5.46 of CC - I reverted to 5.44 (and am still using it) when all the monitoring problems with 5.45 started, so perhaps you could answer this for me please:

    I read the the v5.46 changelog but I'm not entirely clear whether the telemetry that is now running is due to the Settings option "Inform me of updates to CCleaner" being ticked.

    It strikes me that with that option on, then CC MUST "phone home" in order to see if there's is in fact a newer version available.  If that's the case then it would make sense that the only way to block it would be via the firewall.

    I have the  "Inform me of updates to CCleaner"    option OFF in 5.44 until I'm happy to get 5.46 but if you've already installed 5.46 perhaps you, (or anybody else using 5.46) could check? 

    Thanks. :D

  18. On 03/08/2018 at 15:30, Stephen Piriform said:

    Thank you all for your continued feedback (positive and negative, it all helps). I wanted to give a quick progress update on what we're doing. We’re currently working on separating out cleaning functionality from analytics reporting and offering more user control options which will be remembered when CCleaner is closed. We’re also creating a factsheet to share which will outline the data we collect, for which purposes and how it is processed.

    Today we have removed v5.45 and reverted to v5.44 as the main download for CCleaner while we work on a new version with several key improvements. You can grab version 5.44 from one of the links below:

    (File hashes here: https://forum.piriform.com/topic/52095-ccleaner-v5446575/)

    Software Changes

    As stated before, we'll split cleaning alerts (which don't send any data) from UI trend data (which is anonymous and only there to measure the user experience) and provide a separate setting for each in the user preferences. Some of these features run as a separate process from the UI: we'll restore visibility of this in the notifications area, and you'll be able to close it down from that icon menu as before.

    We understand the importance of this to you all. This work is our number 1 priority and we are taking the time to get it right in the next release. There are numerous changes required, so that does mean it will take weeks, not days. While we work on this, we have removed version 5.45 and reinstated version 5.44.

    Thank you for that - I now have v5.44.6575 installed and have checked Task Manager and the Registry finding no "nasties".

    Options > Privacy > Allow usage data to be shared.....  defaulted to ON but I switched it off and it has remained off after a reboot.

    Options > Monitoring is all OFF by default as it should be.

    @Stephen Piriform I would like to point out that you really do need to get this right in the next release. Apart from the fact that I and many others are very disgruntled with this whole affair, might I point out that this is the THIRD time in less than a year that someone at Piriform has dropped the ball.

    In September 2017 there was the incident where CCleaner 5.33.6162 contained malware and earlier this year there was that infernal popup that one finally found could be got rid of by setting a cookie to "keep" - ie using a CCleaner function to fix a CCleaner problem!

    My point is that you / Avast are a SECURITY company and as such, this behaviour saps the confidence of the most loyal user (I've been using CC since it was known as Crap Cleaner and there are many other people the same!)

    I'm willing to await the next release even if it does take weeks, but I must say, i'm keeping my other options on the "back burner" for now. PLEASE fix it, test it, and test it again!!!!

    By the way, I was a professional software tester for 15 years - take it from me, bugs WILL be found in the code if you give your test team a free hand and enough time!

    Thank you.

     

     

  19. 2 hours ago, Willy2 said:

    - Right. I found that registry entry as well. (with the help of ...... CCleaner).

    - I disabled that entry (with CC) and the CC monitoring feature was running again when I restarted my system today. Seems that CC refreshes/re-enabled that registry entry when one is fiddling with CC.

    I presume you went into Tools > Startup and set it to Disabled?

    I just tried that and got the same effect - in fact it created a NEW entry giving 2 entries in CCleaner - 1 enabled and 1 disabled.image.png.4b5d101de433a1bd8b8f62d99403a357.png

    That makes sense actually because Windows reads the registry at Windows Startup which is long before tasks like CCleaner start, so when it gets there, monitoring has already started. It then creates a new Entry in CCleaner to match the Registry. Remember - the Registry is all powerful!

    The way to do it is to edit the Registry key that I quoted above.
    I've just tried it; restarted Windows and Monitoring did NOT start.

    CCleaner functions all OK

    I edited it back, restarted Windows and the monitoring came back on with all the settings in Task Manager and CC as before.

    I am NOT going to be the one to tell you HOW to do this - if you're not conversant and comfortable with editing your Registry, you can do untold and irrevocable damage to Windows if you mess it up!!!! If you do that, and don't have a system image of Windows, you are potentially faced with a rebuild. Please be warned!

    Additionally, there may be other entries that need to be changed if this one is changed - I have not investigated that!

    Suffice it to say that this works and what we need is for the Developers to remove that Registry entry and issue a new build.

    To repeat what I said above:
    "I intend to wait and see for a few days as I think a solution from the Developer is not only more elegant but will prevent the issue reoccurring with subsequent releases! I for one don't want to have to edit my Registry every time CCleaner is updated especially as I have 5 PCs to manage!!

     

×
×
  • Create New...

Important Information

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