/cleanmgr /sagerun in batch scripts

Denis,

Try3 said:

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.

That could very well be the reason. So now, we need to investigate a solution to overcome that behaviour, if there is one of course.

It will be interesting to see if @Beasticles and @mngerhold noticed similar results to mine when they run theirs, and if they did NOT notice, then perhaps they could run cleanmgr again and report back.

Obviously running yours from a Shortcut appears to by-pass this behaviour.

Paul,

Try creating the shortcut [containing the command] then, in your batch file, run the shortcut rather than the command itself.

Denis

Denis: running a shortcut or the batch file direct makes no difference for me. But I have been trying other things - here goes: I have found at least 3 actions that will send the frozen Cleanmgr window on its way:
(i) Hovering over it - the job completes, and all is well
(ii) hitting any key, regardless of where the cursor is - OK[*]
(iii) left-clicking anywhere on screen: bad news!

If I do 3, the CMD window stays open, and I can see Cleanmgr still running in Process explorer and under 'details' in Task Manager: this shows my explorer window, and the contents of the sagerun script (fwiw !):

This second screen capture shows what PE and TM see:


If I then close the CMD window with the X in the top-rt corner, or end the task with TM, Cleanmgr is left still running:


In this condition, subsequent attempts to run sagerun or indeed sageset have no visible effect - it is broken. This is the result of running sageset:
and


I have to kill the cleanmgr process (from TM or PE) to get back to normal.

I have no idea what is broken, but this explains why I had such trouble yesterday - Cleanmgr was still running, and when I launched it a second, third or fourth time, the behaviour was weird. So this has been fun, but I don't know if I have learnt anything other than to be nice to active windows!
[*] The reason hitting a key works is that, with the Cleanmgr window active (as I have not clicked anything else yet), the input goes to Cleanmgr and it is happy.

mngerhold said:

Denis: running a shortcut or the batch file direct makes no difference for me.

Paul,
Martin,

I assume that if you run the shortcut on its own, albeit just for test purposes, it behaves itself.

I don't have any other suggestions.

I just run CleanMgr on its own from that shortcut when I feel like it, commonly once a month.
I don't even have Task scheduler triggering it.

All the best,
Denis

Martin - I do have a slot in my calendar to post samples of variable-reporting-back [the excellent Tom Lavedas method]. It's just that I've been a bit snowed under so I keep moving the slot to the day after tomorrow.

Denis,

Try3 said:

I assume that if you run the shortcut on its own, albeit just for test purposes, it behaves itself.

Strangely enough, NO.

Martin - I did not see those diagrams in your previous post as I wrote my reply. I'll take a look at them now. Denis

Martin,

I run SageSet as Admin. Perhaps that's what saves me?

Try3 said:

There are two steps & two steps only:-

Step 1 - Once-only setting up command in an elevated command window - the dialog containing checkboxes appears for you to select the items you want cleared in future SageRun:1 operations.

Code:

cleanmgr.exe /sageset:1

Step 2 - Routine command to use in an elevated command window or shortcut thereafter whenever you want to clean disks

Code:

cleanmgr.exe /sagerun:1

Doesn't the dialog of checkboxes appear when you run SageSet:NNN?



It's only speculation but, in case previous attempts have messed things up, check
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches
for all StateFlags0096 entries and delete them.
That, I think, should make the dialog appear again for SageSet so you can start again from scratch



Denis