Multiple Cleaner Profiles

Hypotheticals: perhaps I just want to clean my MUI cache on one day; another day, I want to wipe my cookies in Firefox, but leave Internet Explorer intact, and on another day, I want to do a full system clean. It would be very helpful to have an option to save settings to "Cleaner Profiles", or whatever name you would like to call them. Then, a particular profile could be loaded from a menu and run without having to select and deselect all of the desired options.

Thanks for a great program, Piriform!

Welcome to the forums!

Even though this sounds helpful, it might be overkill. Just my opinion.

Lets see what the others have got to say. :)

I use the portable version of CC which uses INI files instead of the registry.

There are several differently named INI files in the same folder which replace CCLEANER.INI,

as selected by a desktop shortcuts such as

H:\Utils\CCleaner\Clean.cmd ALAN

In the same folder is my script Clean.cmd which includes

@ECHO OFF
SET LEVEL=DEFAULT
IF EXIST %1.INI SET LEVEL=%1
COPY %LEVEL%.INI CCLEANER.INI > NUL
CCLEANER %2 %3

I launch CC and adjust all the cleaning check-boxes for a particular requirement,

and when CC closes it updates CCLEANER.INI with the latest settings.

To reuse the same settings I then rename CCLEANER.INI to DEFAULT.INI or ALAN.INI etc.

ALAN.INI holds the settings for a strong purge under my supervision,

which I only clean after an analysis and my decision that it should be safe.

DEFAULT.INI holds the settings for a minimal purge of safe things (keeping out of system files),

and I am confident that I do not need to see the analysis - it is good for an /AUTO

"Other Name".INI can target different areas of the system, and can also be used by other users/profiles.

I often use this desktop shortcut

H:\Utils\CCleaner\Clean.cmd ALAN

When I (or other users ) wish to switch off the Laptop we use

H:\Utils\CCleaner\Clean.cmd DEFAULT /AUTO /SHUTDOWN

Clean.cmd expects at least one argument,

but if there is no argument, or if the spelling is wrong,

it will instead use DEFAULT.INI for safety.

N.B. the script works for non-admin users when the INI files are FAT32.

When I tried it in a NTFS partition CCleaner.ini could not be over-written until I used CACLS to allow this.

Alan