[Exclude menu options]

In Exclude → Add → File types Menu options similar to those present in Include Menu should be added, namely, to exclude files and file masks in ALL subfolders.

For example, if the mask *.bak is to be deleted throughout the whole computer, at present there is no chance to secure such files as MY.BAK or MY*.BAK or MY.* if they reside somewhere in some subdirectories.

[ExcludeKeyX=FILE not working]

The mask *.ext works well in Recurce mode while the mask foo.* does not!

Precisely:

This

ExcludeKey1=PATH|C:\|*.bak

excludes the file foo.bak in all subdirectories of C:\

whereas this

ExcludeKey1=PATH|C:\|foo.*

excludes the file foo.bak only in the root of C:\

Same bag when introducing the mask foo.* through the menu EXCLUDE

[ExcludeKeyX=FILE not working]

Wouldn't you need to select the *.db from each subfolder?

 

It would seem CCleaner is only willing to save the .db file from D:\ and not the ones from D:\Movie1\ etc

 

If I'm reading this right, I'm not actually awake right now :X

 

Yes, this is the core of my problem. And it does not depend on the operating system (say XP SP2)

RECURSE does not work in the EXCLUDE mode.

See my suggestions

http://forum.piriform.com/index.php?showtopic=32311

Posted 27 April 2011 - 09:29 PM

[ExcludeKeyX=FILE not working]

Hi, thanks. This has been corrected

Yeah?But I need this function.

Men, I need badly

ExcludeKeyX=FILE|C:\|MyFile1.MyExt1,Myfile2.MyExt2,Myfile?.*|RECURSE

work!

Looking forward to recover this function in the next upgrade!

Thank you!

[ExcludeKeyX=FILE not working]

Yeah you have to play around with the exclusions sometimes as I found out trying to exclude Microsoft Security Essentials signature files download/update folder. It's easier to play around with exclusions by first:

1. Start CCleaner and go into 'Options->Settings->Advanced' and tick the box "Save all settings to INI file", then close CCleaner.

2. Now open the folder where CCleaner is installed and open the settings file "ccleaner.ini" and look for your exclusion which you can then manually play with to see if CCleaner will finally exclude what you want.

 

Tip:

Sometimes you have to remove these for an exclusion to work: \|*.*

 

Example, this didn't work:

PATH|C:\WINDOWS\Temp\46D3ABA7-DD84-4AE5-9CF8-96FC61882AE2-Sigs\|*.*

 

Example, this did work:

PATH|C:\WINDOWS\Temp\46D3ABA7-DD84-4AE5-9CF8-96FC61882AE2-Sigs

 

I think if regular Windows expressions were used it could save allot of confusion on how to get some things excluded easier.

What I actually meant to emphasize was that the RECURSE option from the pattern in the 'On Line Help' that read

'ExcludeKey4=FILE|C:\temp\|*.*|RECURSE'

definitely produced no effect, independently of the use of |*.* there.

RECURSE does not work together with either 'Exclude' command, contrary to what is asserted in the Help!!!

To be more precise, the following works:

Exclude25=FILE|D:\TestFolder\|TestFile.back,

whereas the next does not exclude same files named TestFile.back placed in no matter what subdirectory of D:\TestFolder\ :

Exclude25=FILE|D:\TestFolder\|TestFile.back|RECURSE

[ExcludeKeyX=FILE not working]

Sorry to report that the manually added entries of type

 

ExcludeKeyX=FILE|C:\Windows\|*.*|RECURSE

ExcludeKeyX=FILE|C:\Windows\|MyFile.MyExt|RECURSE

 

produce no effect (see http://www.piriform.com/docs/ccleaner/advanced-usage/ccleaner-ini-files/how-to-exclude-items-from-ccleaner's-cleaning)

[Custom exclusions]

I disagree.

 

I purge Macromedia Flash directories - I do not want that junk.

If the folder is recreated but not populated it is doing no harm,

and I have no interest in seeing an analysis result showing that zero space saved.

In fact I prefer not to have my time wasted by being shown such a non-result.

 

It is not compulsory to delete all subfolders when you delete the contents of a parent folder.

 

You can use masks to filter what is specified for deleting.

Why do you want extra filtering to exclude the things you have just specified for deleting ?

 

Let me explain.

1. Imagine I expect a file named HOOPS.BAK appear somewhere in the future, but I have no idea in what exactly folder that will happen. Nevertheless I don't wish it being erased. At the same time I definitely am not going to waste my time checking hundreds of *.BAK files listed for deleting. Or I've long ago forgotten what my precious files look like. I'd like to feel safe a priory, without going thoroughly through the list of found items.

 

2. Imagine I am tired of gazing at folders GLOOMY.00? reappearing throughout my directory lists anywhere on my machine, no matter whether they are empty or not.

 

3. You know, many applications create trees of subfolders in TEMP folder, and I wish to sweep them away from my FAT and from directory lists. Because such is my sense of accuracy

 

4. Or imagine I myself had created lots of temporary (sub)directories with similar names here and there and have forgotten the exact paths, and now I wish to erase them all or empty them of all their subdirectories once a quarter at one single move.

 

5. Now about empty folders NOT APPEARING in the list of items to be erased. This is the matter of satisfaction at having everything under one's control. Assume I bother not only about the space to be saved but also about tidiness. Yes, empty folders do harm to the directory lists!

[Custom exclusions]

I appreciate that the user defined directories can be deleted as a whole. Several other products I experienced with did not offer this magic solutions.

Alas, once found, these directories DO NOT APPEAR in the results list unless they are NOT EMPTY. They should appear, since they will be erased.

Also the effect of file/directories attributes is not clear at the 'Analise' stage. Some files/directories are not listed (the read-only ones), some are (hidden are listed), nevertheless them all are erased.

One can not chose in the list of found objects, which objects one wishes to erase, and which others to preserve.

The serious shortcoming is that the user has no means to introduce MASKS of files/directories in the custom 'Exclude' list! Only if the full path is indicated. This is very dangerous, 'course there might be no such files at time of 'Analise', but they may appear in future, and one does not know in advance, in what exactly directory they might appear!

I look forward to the enhancements in the ability to put MASKS of directories as well as files with and without paths into each of user defined lists.

Thank you.