12 replies to this topic

[titanad]

I frequently have a problem with my browser(s) not closing completely. I may close the browser, but when I run CCleaner a message pops up asking if I want CCleaner to close the browser. Since updating to version 3.20, this feature is NO longer working. It just skips the item(browser) when searching and deleting the files.

This was a very useful feature and I hope you will consider adding this back to CCleaner. I have deleted version 3.20 and will keep version 3.19 if and until it will again have this feature.

thanks,

Harold

[Winapp2.ini]

I can confirm that I am not prompted to close my browser.

[Nergal]

Are both of you of 64bit version? is this true with both chrome and firefox (or just one or the other)? I know winapp2 is not but titanad are you running ccleaner in a language other than english?

[Winapp2.ini]

I did not recieve prompts for :

Firefox 14 beta (32bit)
Waterfox 13 (64bit)
Chrome 20 (32bit)

I did receieve a prompt for Thunderbird x64 (Earlybird)

[MrT]

Let us know if you have any of these entries on your ccleaner.ini or under "HKEY_CURRENT_USER\Software\Piriform\CCleaner"
MSG_WARNCHROMECACHE=false
MSG_WARNMOZCACHE=false

Set them with the word "true" in order to be prompted again.
MSG_WARNCHROMECACHE=true
MSG_WARNMOZCACHE=true

[Winapp2.ini]

Weird, I never selected (knowingly or intentionally, anyway) the 'do not prompt me again' thing, but that seems to be the case here.

[titanad]

Are both of you of 64bit version? Yes, 64bit
Are you running ccleaner in a language other than english? No, english

--Let us know if you have any of these entries on your ccleaner.ini or under "HKEY_CURRENT_USER\Software\Piriform\CCleaner"--

Remember, I said that I had re-installed version 3.19 and those registry keys don't show up for this version. Are you saying that if I upgrade to version 3.20(and later versions) that I will have to edit the registry every time?

[Keatah]

Perhaps we can have options to toggle this functionality?

[titanad]

MrT, on 27 June 2012 - 01:16 PM, said:

Let us know if you have any of these entries on your ccleaner.ini or under "HKEY_CURRENT_USER\Software\Piriform\CCleaner"
MSG_WARNCHROMECACHE=false
MSG_WARNMOZCACHE=false

Set them with the word "true" in order to be prompted again.
MSG_WARNCHROMECACHE=true
MSG_WARNMOZCACHE=true

MrT,

I replied to your question in post #7. Please reply to my post.

Edited by Andavari, 29 June 2012 - 09:19 AM.
No need to triple the quote

[Alan_B]

titanad, on 29 June 2012 - 03:33 AM, said:

MrT,

I replied to your question in post #7. Please reply to my post.

You have no right to demand answers from developers unless you have paid for support.

Mr T. was asking questions to determine what needed fixing.

You said that you had no keys MSG_WARNCHROMECACHE etc.
It is unrealistic to expect Mr. T. to predict in advance of fixing the problem whether such a key will be used again.

It should be obvious that CCleaner has never yet required a user to meddle with the registry as standard procedure,
and Mr. T. was kindly giving a fix for those that needed a fix to v 3.20.
I am confident that the problem will be fixed on future versions and will take care of any inappropriate keys and settings from previous versions.

[titanad]

Alan_B, on 29 June 2012 - 04:45 AM, said:

You have no right to demand answers from developers unless you have paid for support.

Mr T. was asking questions to determine what needed fixing.

You said that you had no keys MSG_WARNCHROMECACHE etc.
It is unrealistic to expect Mr. T. to predict in advance of fixing the problem whether such a key will be used again.

It should be obvious that CCleaner has never yet required a user to meddle with the registry as standard procedure,
and Mr. T. was kindly giving a fix for those that needed a fix to v 3.20.
I am confident that the problem will be fixed on future versions and will take care of any inappropriate keys and settings from previous versions.

First, I wasn't demanding anything. I answered the questions MrT had asked.  I waited on a response from MrT for a day and when I did not hear back I simply asked(nicely) for a reply.

Edited by DennisD, 30 June 2012 - 07:38 AM.
I've removed an undeserving comment from your post..

[DennisD]

Alan was correct in his above reply, and the comment I removed wasn't necessary. To get direct developer support, there is an option to pay for it.

On this free support forum the devs at times enter into a topic to obtain the info they may need to provide a fix in a future version.

They've done that, and your issue has also been confirmed by another member. There isn't anywhere else for this topic to go really, as the suggestion re the registry was simply a workaround until a fix is found.

Going back to a previous version until then is the best way to go.

[Super Fast]

@titanad -> Thanks for posting about the issue. Tiny things like that could escape my notice, although they are certainly things I would be very annoyed with discovering after using it long enough to have it happen to me. I am sure with your input that they will have it fixed in newer versions.

If you are able to do so, if you could verify whether that key existed, it would greatly assist the developers in crushing the bug.

The reason they ask is not so much that they want you to have to manually edit it each time, but just that if you can verify whether it exists, then they will have a more definite knowledge about what needs to be done to fix a future version. Software does contain bugs, & sometimes more so than others, so your input is very valuable.

If you are unable to do so, do not worry. As Dennis here kindly noted, there are others having reported the same issue. So future versions should be fixed.