Rostia CCleaner

I'm wondering, are there any cases of this behavior (CCleaner opening when a game closes) where people don't use Razer Cortex?

Hi everyone, I'm a bit late to the party but maybe it will still help someone. I looked a bit at Cortex and indeed it is the culprit here. When Boost runs, it kills processes it thinks are expendable in order to free up some RAM. CCleaner is one of those processes. Cortex remembers the path of the executable, but not the command line arguments which were passed to the process when it was executed. So when the process is later (after the game) restored, it is restored without any command line arguments. And that's the problem. CCleaner background process is started with the "/monitor" argument. Cortex kills it, but restores it without this argument, which displays the main GUI window as you have experienced. There seems to be several ways how to make Cortex stop killing CCleaner (for the price of less memory freed for the game). The simplest one is probably unselecting CCleaner in Game Booster -> Boost -> Processes. Cortex saves this option in a file in something which looks like a profile folder and it persists through different instances of both Cortex and CCleaner. C:\ProgramData\Razer\RazerCortex\RZR_0280995146178ed00acc91979bae\process.ini [Process0] CCleaner64.exe=0 As for three instances of CCleaner running, which was mentioned above, that should not be three instances but rather tray icons which were left there when CCleaner was forcefully killed by Cortex. If you hover with your mouse over those icons, they should disappear, at least those belonging to the killed processes. I think it's something for us to look at though.

@ccleaner_user 10+ times a day is for sure not the right frequency. Would you please mind sharing some details? What Windows version do you use? On a day when those 10+ toasters appear, how do you use CCleaner? Is it just Smart Cleaning monitor running in the background, or do you open CCleaner application window? If so, how often (once / multiple times)? Do you use Internet Explorer? How is your IE Security level set? You can find this setting in Control Panel -> Internet Options -> Security tab. This applies for Windows 10, it might be slightly different for other versions. How are you IE Cookies set? You can find it in Control Panel -> Internet Options -> Privacy tab -> Advanced button. Again might be slightly different for other versions.

So as it says the 'new style' partitioned cookies are not written to your disk so don't need to be cleaned from it. And they no longer show up in Options>Cookies as 'Cookies on Computer', because they are not on your computer. This is what WebKit does, I'm not sure if Firefox does the same...

Hello everyone, I'd like to clarify some details of this change. TLDR: What changed in 5.83 is how CCleaner treats HSTS flags. HSTS (HTTP Strict Transport Security) is a mechanism how a website informs the browser that it can only be accessed via secured HTTPS. The purpose of this mechanism is to improve security by preventing various man-in-the-middle attacks. A nice explanation of why and how is in Firefox webdev documentation. Unfortunately, HSTS has been abused for cross-site tracking, so this security feature became a privacy issue. If you are interested in details, you can read for example this article. The idea is quite interesting, one must really admire ingenuity of these people. :) Firefox stores a list of these websites (i.e. sites to be contacted via HTTPS) in the SiteSecurityServiceState.txt file. Before 5.83, CCleaner treated items in this list as cookies, so if you cleaned cookies, you cleaned this list too. Some time ago, Firefox started to partition HSTS flags by appending partition keys to the websites (these are the "cookie jars" if I may borrow @nukecad's term). This is the reason why weirdly looking cookies started appearing in CCleaner. Thanks to this change however, HSTS has become much less of a privacy issue, so we moved it away from the "Cookies" category to "Site settings" category. This is by the way the same way how Firefox treats HSTS flags. So Firefox cookies (the traditional HTTP cookies) are still cookies and nothing has changed for them. It's only HSTS flags which are no longer cookies and have become site preferences.

Thank you very much, it's been very helpful!

Thank you, I checked the log and it is actually helpful. Would you mind running it in debug and post the log again? There is some oddity in the log you posted and I'd like to see how much deterministic it tends to be. Yes, I know this issue has been around for some time.

Hi @Mcd73165, could you please try to run CCleaner in debug mode and send me the log? I suppose you don't experience this issue very often, so there's not a big chance of it happening in the debug run (would be great if it did though), but please send me the log anyway.

It's hard to predict this behavior apparently. The fact that it re-occurred and even changed after an update is however quite interesting and I'll try to take a look at it again with this in mind. lil.log is a license component log, you can ignore that one. Thank you! Maybe delete the old logs once in a while, so that they don't take up your space. A new log file is created every time CCleaner runs (with the /debug argument).

Hi @cphisher, I was going to ask you for those logs but you were faster. CCleaner doesn't create logs by default, this needs to be explicitly enabled. To do that, could you please run CCleaner with a "/debug" argument? You can either: Run CCleaner from the command line ('CCleaner64.exe /debug' from the folder where it is installed) Or create a shortcut and add the argument to the target like this (and then run CCleaner using this shortcut): The log will be created in the CCleaner install folder. May I please ask you to get that log and send it to me?

@cphisher Amazing, thank you!

Thank you both for the links, one of them slipped my attention before. Interestingly, the user in that thread reports that he gets duplicate items almost every time

Hello @cphisher, I'm a member of the CCleaner development team and it would be very helpful if you could provide us with some additional information about the issue. Could you please try to answer the following questions? Are the duplicates in the rules tree on the left displayed also without running the analysis, or do they appear only after the analysis has finished? Did you visit some other screens (Health Check, Registry,...) before navigating to the Custom Clean? What have you set as your home screen (Options - Settings - CCleaner Home Screen)? Are you using any custom .ini files? Thank you very much!