nukecad

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.

Just to add that personally that is not an extension that I'd find much use for. 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. (Like I did with that quote from Google above). Each to their own.

Thanks to Megan for that actual filename/location. Out of interest I did try adding that extension to Edge Chromium, and clearing the Edge session with CCleaner does remove the context menu entry. So it seems to be an issue with how/where Chromium based browsers store it, as I say it doesn't happen for me with Firefox. (I have learned something new about Chrome for future reference). As we have all said it seems odd that Chromium is storing extension settings in the session information. Extension temporary data fair enough, but settings are not session related so why put them there? CCleaner cleans the Extension State because it can contain a lot of junk, Google themselves say: http://shouldicleanit.com/apps/google-chrome-extensions-state Adding exlusions shouldn't be an issue with CCleaner updates, they will carry across updates especialy if you have your settings saved as an '.ini' file. (CCleaner Options>Advanced>'Save all settings to INI file'). If you ever have to reinstall CCleaner (rather than update) the .ini file can be used to bring in your previous settings. Another advantage there is that you can copy the .ini to the CCleaner folder on other machines to get exactly the same settings. I also keep a backup copy of my particular .ini file, I'm always messing with settings when answering questions here and so it's a quick way to get my own particular setting back, just put my .ini back into the ccleaner folder. In the end though it is as you say, if you don't want to clear the open tabs and logins anyway then it's simplest just not to clear the sesion. PS. The Custom Clean ticks/unticks are for use by Custom Clean only, if you run Health Check then it has it's own rules and will still clear the session.

Moderators are users just like everyone else, but we have proved ourselves helpful/knowledgable and are trusted to keep the forum tidy (and get rid of spam and spammers). We can and do contact the staff in a private section of the forum if a question needs more insight than we have, but they also read the posts on the open forum anyway. I'll flag this thread up, but I don't think they can do much more than we have already covered. It seems evident from your testing that it's saving the setting in sessions, where you wouldn't normally expect them to be. Whether that is being done by design, or by mistake, only the extensions developer could comment. Another problem is that the session information is usually saved as a 'json' file with everything saved as one line in that one file, with the different settings seperated by commas. So it's generally a case of deleting that file to clear all the information rather than trying to edit it for specific things. For an example this is the current contents of just one of my Firefox session files after I've just closed Firefox - 'sessioncheckpoints.json' {"profile-after-change":true,"final-ui-startup":true,"sessionstore-windows-restored":true,"quit-application-granted":true,"quit-application":true,"sessionstore-final-state-write-complete":true,"profile-change-net-teardown":true,"profile-change-teardown":true,"profile-before-change":true} As you can see there are 9 different settings saved there as 'true', and all as one line of text which makes it difficult to try and remove some but not others. Plus of course the number of entries in the session files will also change depending on what you have been doing in the session. And that's just one of the session files. In the end it may simply be that clearing the session is incompatible with that extension in Chrome. (I see the extension is also available for Edge Chromium, I wonder if it has the same issue there? Might have a play if I get time later).

It isn't the browser that is blocking your access to those sites. As the message says it is the websites own server that is temporarily blocking the access for security reasons. And as it says, the server will probably not be blocking access later. That is why you don't get CCleaner browsers 'Proceed anyway' option - it isn't the CCleaner browser doing the blocking so it can't let you through that block. More about HSTS: https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security

AFAIK 'Firefox suggest' is only currently enabled in the US with v93.0, but no doubt it will be rolled out worldwide. It's certainly not yet on my v93.0 here in the UK, so can't yet be disabled. One concern I've seen is that mozilla must now be reading what you are typing into the address bar and processing this information on it's servers in order to offer you it's own suggestions. But Google, Bing, and other search engines, have been doing that for years anyway.

As Hazelnut says an email to support will sort this out for you. How did you extend the licence? Did you renew through a notification or purchase a licence from the CCleaner webpage? The first should automatically add the days remaining on the old licence to the renewal, but it can take a day or so for that to show up in the licence information. However if you purchased a new licence through the website then it is assumed it's for a different computer, the support team can merge the old/new licences for you to add the remaining time. https://support.piriform.com/hc/en-us/articles/360045224272-Can-I-renew-CCleaner-early-

Of course we do have to be fair to the extensions developer and recognise that it's a possibility that CCleaner is removing something that it shouldn't be for the Chrome 'session'. Until we know where/how the developer is saving the information for Chrome we can't be entirely sure about that. As said above having something in the session may be the only way to get it to work with Chrome? (The fact that a keyboard shortcut is also affected may also point to that). PS. I Also checked a few other things with the Firefox extension in CCleaner. The extension is listed in Tools>Browser Plugins, as it should be. The context menu entry is not listed in Statup>Context Menu, so it's working in some other way. Which you would expect as it's only available in the browser and not for everything.

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/

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.

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.

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), But 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?) Maybe Chrome has changed where things should be stored, but that extension hasn't been changed yet? Chrome (and Firefox) do keep changing where things are or should be stored. 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.

That is the nub of it - Neither of us knows just where that extension is saving it's information, and CCleaner doesn't know either. CCleaner is just cleaning something where that information is. I suspect it's probably a cookie?, So if you clear Chrome cookies then it would get cleared. But it could just as easily be in the cache, or the session? The way to check is to only clear only one at once (as I described above) to find out which it actually is. If you don't want to do it by right-clicking as I described then you can untick them all, then just tick one and run Custom Clean, check if that has removed the context menu entry. If it hasn't then tick the next one and clean, check again. And so on. When the menu entry gets removed then you will know that it's the last one that you ticked that is removing it. Once you know that then it may be possible to narrow it down further. (And maybe stop CCleaner removing it). (eg. If it is a cookie then you could tell CCleaner to 'Keep' that cookie and not clear it; if it's somewhere in the cache then you may be able to set an 'Exclude' so that bit of the cache doesn't get cleared).

Something to know is that the term PUA stands for 'Potentialy Unwanted Application'. The thing that you should take note of there is the word- Potentially. (It means 'might be'). That is someones personal opinion that they might not want that app - but whether it is 'Unwanted' or not is up to you not them. Occasionally someone decides to try and force their personal opinion on others, even some Microsoft employees do it now and again. (They should know better and get pulled up when they do). But it's your choice if something is unwanted or not. Some people want things, other people don't want them. So: Updating your driver(s) caused you a problem, that is not unknown. (And sometimes not unusual). Updating Drivers can result is problems, but that is because the updated driver is not the right one for your machine. (Personally I would not use any Driver Updater, I would decide first if it needs to be updated and if it does then update it myself - but again that is my choice). PUA's (and PUM's - Potentialy Unwanted Modifications) should be treated as just alerts/warnings from your security app that you may want to take a closer look at what something may be doing. It's then up to you to decide if you want to keep using it or not. Millions of people around the world use CCleaner, they don't consider it a 'Unwanted' Application. Some do consider it unwanted, but they shouldn't be trying to force that opinion on everyone else. (As an example Facebook is unwanted by me, but I wouldn't try to tell anybody else that they shouldn't use it. That's their choice if they want it or not). Now having said all that: The 'PiriformBundler' that is being objected to is not in CCleaner itself. It is a component of the Standard Installer for CCleaner, (CCsetup###.exe) and it will only run when you install CCleaner from the Standard Installer. It is the page that comes up offering an additional software. That page has very big 'Decline' and 'Accept' buttons. It will only run, and you will only see it, when you are installing CCleaner.

I think that @crizalits the nail on the head. Stay with Win10 unless you want to play about. Win11 has been released too early. Microsoft, and others, seem to have pushed beta-testing out onto users as a policy. (Looks good on accountants balance sheets, but it costs more in the long run).

Sorry but that is still not clear. Can you explain exactly what you are wanting to do?

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.

Google (and others are just as bad) are in the business of selling your browsing history etc. to advertisers - they don't want you to be able to completely delete it and so they make it pretty hard for you to do so. (Browser and app Syncing was a masterstroke for them; all that lovely sellable information, browsing history and other data, that users are putting on their servers where they can pick through it at their leisure).

They are still sticking with 'You will need TPM2.0', this is only a temporary workround which they say they will pull later.

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.

When you log into Gmail it also automatically logs you into Google as well. However I think that your problem with the history coming back in Chrome after cleaning is probably due to having syncing enabled. If you have your browser (or any apps) synced then anything 'synced' that you clean from your computer will be restored by the syncing. That's how syncing works, it saves your data in the cloud and sends it to all your devices from the cloud. CCleaner can clear the data from your computer, but it can't clear data from a cloud server, (they are protected). So to stop that syncing happening and your data, history, etc. coming back you have to use the browser/app to clear the synced information from the cloud, or turn off syncing altogether. PS. You may want to have a read of this explanation of various reasons why some files will come back after cleaning> https://community.ccleaner.com/topic/52668-tracking-files-not-cleaned-files-coming-back-solvedexplained/?tab=comments#comment-300043

I'm not sure why you would be trying to use the CCleaner Browser to uninstall apps? Use CCleaner itself - Tools>Uninstall. (Or use Windows - Settings>Apps )

This PDF opening happens when during the install of CCleaner browser you tell it to associate PDF's (and other filetypes) to open/read by default in CCleaner browser. It's one of the options during the install. If you then uninstall the browser then obviously you can no longer use it to open/read files. Windows doesn't know what you then want to open those files with and so has to ask you. Reassociating the files to open with something else cures the problem. The link that John gave you is fine, but a bit long winded, see this for a quick way to reassociate PDF (and other files) to open with a particular app:

Of course in this case the corrupted bin is E:\$Recycle.bin and not C:\$Recycle.bin - so you should modify that command line accordingly to reset the bin on E:.

Moved to CCleaner for Mac.