/cleanmgr /sagerun in batch scripts

If you want to see the VolumeCaches [ StateFlags ] that appear in the Registry, Copy & Paste the following command into a CMD Prompt and press Enter.

Code:

@echo off & echo. & for /f "usebackq tokens=8 delims=\" %i in (`REG Query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches`) do echo %i

Paul,

Paul Black said:

Surely that only sets the Default StateFlags items if you have NOT already changed them [ Checked or Unchecked ] !

The dialog for setting the checkboxes appears as part of running this command.

But the [trimmed] exported .reg file afterwards can set it all up again for the SageSet:NNNN number used to match those choices without any dialog being involved.
So I used my [trimmed] exported .reg file to transfer my settings from one computer, where I'd done the work, to all my other computers. I could then run the same SageRun:NNNN command on the others.
The trimming is just to remove all the other entries from the relevant Reg key because they are involved in several other [unknown] functions.

Paul Black said:

Do you have to hover over the box for it to disappear ?

No.
It does its job and closes when it's done, like almost every other command or batch file.

All the best,
Denis

Oh, while we're on the subject of CleanMgr, an apparently well-regarded individual called Fred Langa conducted experiments that demonstrated that Registry cleaners do not add one jot to the cleaning up that routine application uninstallations & CleanMgr do.
About Temporary Files and Registry Junk Data Slow Down - CleanMgr does the job - TenForums
See the article Callender linked to in post #5.

I had never before seen experimental evidence of Registry cleaners being snake oil.

All the best,
Denis

Hello @Beasticles,

Beasticles said:

I have yet to mess with registry keys or use FreeBooter's script.

Just a word of WARNING.

FreeBooter's Script ALSO cleans up the Temp files, DELETES the oldest Shadow Copy on drive C, and cleans up the Event Viewer Logs etc.

I hope this helps.

Beasticles said:

ill try my best to try all of these attempts including the running cleanmgr on its own again in different ways.

Try3 said:

There are two steps & two steps only:-

Step 1 - Once-only setting up command in an elevated command window

Code:

cleanmgr.exe /sageset:1

Step 2 - Routine command to use thereafter whenever you want to clean disks

Code:

cleanmgr.exe /sagerun:1

Try3 said:

The dialog for setting the checkboxes appears as part of running the first [SageSet] command.

If you run those two steps on their own [without your batch file] you should see CleanMgr running & finishing without any human intervention during the second step [and the first step never needs to be repeated].


Best of luck,
Denis

Hello @mngerhold,

mngerhold said:

oh - except that when I closed various windows (NP++, explorer) a lot of cleanmgr windows flashed before my eyes!

That is why I always close EVERYTHING before I run my weekly cleanup Script to avoid any unusual behaviour and to allow the computers full resources to be available for the cleanup processes.

OK.

I have been performing some tests to try and get to the bottom of why there is a delay in continuing to run cleanmgr for some, until they hover over the cleanmgr box, and NOT for others.

I did find something very interesting which I believe is a contributing factor, if NOT the reason, for this behaviour.

These are my findings when cleanmgr is run in a Script along with other commands, or run in a Script on its own.

When the cleanmgr box appears, the CMD Prompt visually changes. By this, I mean that the Title Bar does NOT show as the Active screen and has a lighter appearance. When you hover over the cleanmgr box, the CMD Prompt shows as the Active screen and continues.

Perhaps someone can confirm if this is also the case for them !

I have tried to explain this as best I can.

Paul,

Having previously used SageSet:1 to set up the options {without defining a drive i.e. for all drives}, I run CleanMgr from a shortcut
C:\Windows\System32\cleanmgr.exe /sagerun:1
and I do not see any cmd window. I see minimised Disk cleanup tabs in my Taskbar and they disappear when their job is done.
- It starts off with a single drive [I assume it's the OS drive], then
- it gets into its stride and cleans multiple non-OS drives in parallel, then
- it finishes.

I wonder if what you've described is that the cmd window is indeed not the active window because the active window is a Disk cleanup one.

All the best,
Denis