Exitcode CCleaner

CCleaner for Windows
1

Hi everybody,

Completely new here. Couldn't find an answer to my question in the forum, at least I think. At least, the search-function didn't deliver any answers.

I'm using the free version of CCleaner on my home laptop, version 3.21.1767, OS Windows Xp Prof SP3, Firefox 14.0.1 (all Dutch).

Lately I'm using CCleaner during shutdown of my computer. Because I want to do several other tasks during shutdown, CCleaner is part of a shutdown-script (DOS-batch), using the /AUTO switch.

While testing this script during running time of my computer, just by executing the batch-file, I sometimes encountered an unexpected error from CCleaner. A real look-a-like of the one mentioned in the post of ChilliP2012, 27 July 2012 01:08 AM.

Strangely I didn't have to close the error-window in order to end CCleaner. It just ended, and so did my shutdown-script.

Now I'm wondering if there is a way to test the status of CCleaner on completion. Thus testing if CCleaner completed successfully, or if it encountered problems. Since the is no log file, not even for these problems, it would be nice if I could test whether CCleaner ended successfully on return in my shutdown-script.

Hope I clearly subscribed my problem, especially since English is not my native language. (Surprise ?)

2

You can run it with the debug command, although I don't know how it will work from within your script:

CCleaner.exe /debug

After running it with the debug command open the CCleaner program folder and look for a log named similar to this:

CCleaner_v3.21.1767_2012-07-29_17-29-11.log

3

Are you sure you are launching CCleaner in the optimum fashion..

There are three possibilities that spring to mind

Start CCleaner.exe /AUTO
Start /Wait CCleaner.exe /AUTO
CCleaner.exe /AUTO

I never use the third one in a script because whether or not the script waits for completion of the *.EXE depends upon whatever Microsoft Documentation Gobble-de-Gook might mean.

I think 16 or 32 bit applications worked differently on 32 bit XP many years ago, and I have not bothered to read about what happens on my 64 bit system.

In a script I always use one of the first two.

"Start CCleaner.exe /AUTO" will launch a separate instance of CCleaner.exe to do its own thing whilst the batch script continues to do whatever I want,

and they each finish and close independently,

"Start /Wait CCleaner.exe /AUTO" will launch CCleaner.exe and wait for it to close, after which the script resumes control and performs whatever else I want.

In either case you should be able to append /debug

N.B. Often I omit the /AUTO because I like to have a last look and think about what is going to be destroyed.

4

In XP if using a bat or cmd script it will wait for programs to exit automatically before continuing onto what's next in line in a script.