Disk cleanup registry changes?

[Craig]

I'm trying to script the Windows 2000 & XP disk cleanup. I
see there's a Q article (253597) that says you run:
cleanmgr.exe /dC: /sageset:n (where n is the identifying
cleanup number). Upon doing this step, registry entries
will be made that will allow you to then issue this
command: cleanmgr.exe /sagerun:n. That's great...but what
I want to know is what registry keys actually get changed
and/or what entries are made so I can skip the goofy
cleanmgr.exe /dC: /sageset:n command and then have to
select which stuff I want to clean up. I'd rather directly
make registry entries in my script and then cruise right
on to the cleanmgr.exe /dC: /sagerun:n command!

Does anyone know which keys are changed/modified? I've
tried examining the registry before and after the
cleanmgr.exe /dC: /sageset:n command using windiff, but I
can't seem to put my finger on what changed.

Suggestions???

Thanks,
Craig

 

[Mike Brown]

I'm trying to script the Windows 2000 & XP disk cleanup. I
see there's a Q article (253597) that says you run:
cleanmgr.exe /dC: /sageset:n (where n is the identifying
cleanup number). Upon doing this step, registry entries
will be made that will allow you to then issue this
command: cleanmgr.exe /sagerun:n. That's great...but what
I want to know is what registry keys actually get changed
and/or what entries are made so I can skip the goofy
cleanmgr.exe /dC: /sageset:n command and then have to
select which stuff I want to clean up. I'd rather directly
make registry entries in my script and then cruise right
on to the cleanmgr.exe /dC: /sagerun:n command!

Does anyone know which keys are changed/modified? I've
tried examining the registry before and after the
cleanmgr.exe /dC: /sageset:n command using windiff, but I
can't seem to put my finger on what changed.

Suggestions???

Thanks,
Craig

I don't know about the registry changes, but I can help you save a few
keystrokes. You only need to run

cleanmgr.exe /sageset:n

to set settings for all drives and

cleanmgr.exe /sagerun:n

to clean all drives.

There are several programs which will monitor and report registry changes
for you, http://www.google.com/search?query=monitor+registry+changes should
get you one pretty quickly.

--

Mike Brown
Asset Forwarding Corp.
EPA-compliant Recycling
DoD 5220.22-M Data Elimination
http://www.assetforwarding.com

 

[David Candy]

StateFlags<sageset number>
under each cleaner
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\VolumeCaches

 

[Jerold Schulman]

I'm trying to script the Windows 2000 & XP disk cleanup. I
see there's a Q article (253597) that says you run:
cleanmgr.exe /dC: /sageset:n (where n is the identifying
cleanup number). Upon doing this step, registry entries
will be made that will allow you to then issue this
command: cleanmgr.exe /sagerun:n. That's great...but what
I want to know is what registry keys actually get changed
and/or what entries are made so I can skip the goofy
cleanmgr.exe /dC: /sageset:n command and then have to
select which stuff I want to clean up. I'd rather directly
make registry entries in my script and then cruise right
on to the cleanmgr.exe /dC: /sagerun:n command!

Does anyone know which keys are changed/modified? I've
tried examining the registry before and after the
cleanmgr.exe /dC: /sageset:n command using windiff, but I
can't seem to put my finger on what changed.

Suggestions???

Thanks,
Craig

See tip 2178 in the 'Tips & Tricks' at http://www.jsiinc.com
See tip 5920.


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com