I just upgraded a Windows 7 system to the very latest CCleaner and now I notice that it skips cleaning of Internet Explorer 11 unless all instances of IE are closed. This is new behavior and severely limits the functionality for me. Is this intentional? I don't see it highlighted in the release notes. I know this was the previous behavior with Firefox but not IE. Even if this was intentionally done to "better" clean IE, can there be an option to revert to the old behavior. I have apps that use IE that need to stay open at all times...
This is due to changes microsoft made in ie 11, the developers had no control/choice over this. Ie now uses a database like firefox and chrome do; this database file is locked from access if ie is open
Could you perhaps explain then, why this issue has only started to happen with the update from 5.22 to 5.23, or is this in anticipation of an update for IE? Since with 5.22 this was still working as intended to my knowledge.
Furthermore I would like to mention that CCleaner takes 1~10 seconds from what I've seen so far, in order to recognize IE has been closed and will clean no longer skip the files.
This means that I now need to open CCleaner and repeatedly swipe for up to/after 10 seconds before the files have been wiped, which IMHO is notably inconvenient. The sweeping process itself also seems to be slower.
Could you perhaps explain then, why this issue has only started to happen with the update from 5.22 to 5.23, or is this in anticipation of an update for IE? Since with 5.22 this was still working as intended to my knowledge.
Furthermore I would like to mention that CCleaner takes 1~10 seconds from what I've seen so far, in order to recognize IE has been closed and will clean no longer skip the files.
This means that I now need to open CCleaner and repeatedly swipe for up to/after 10 seconds before the files have been wiped, which IMHO is notably inconvenient. The sweeping process itself also seems to be slower.
your issue is different dave asked before .23was released, I believe. However if I'm wrong and for you, @Avolendi I believe there may be troubles with .23 and internet explorer. The devs have been advised to look into this.
your issue is different dave asked before .23was released, I believe. However if I'm wrong and for you, @Avolendi I believe there may be troubles with .23 and internet explorer. The devs have been advised to look into this.
Added it here since the title mentions .23 and also using IE11 with W7. So I assume there is a correlation.
In any case thanks for the reply
For now I reverted back to .22 and it works normally again.