Thanks Mike........believe it or not, I was going to suggest resetting
System Restore, but, I was unsure. Thanks for the assist and good advice.
Hope Cheez gets it worked out.
Heirloom, old and going to
bed now....busy day


"Mike M" wrote in message
...
Further to heirloom's post. In normal usage stmgr.exe shouldn't use more
than 1 minute of cpu time in any 24 hour period so if you are seeing
significantly more than this it is likely that you have a massive build up
of files in the C:\_RESTORE\TEMP folder and that the state manager has now
kicked in and is analysing these files, discarding those not required by
system restore and archiving those required for any system checkpoints you
have to FS*.CAB files in the C:\_RESTORE\ARCHIVE folder.

If the state manager's usage doesn't drop back to normal fairly soon and
you are happy with the present state of your system you might want to
think about resetting system restore which will clear out all existing
system restore checkpoints and the C:\_RESTORE archive. You do this as
follows:
System | Performance | File System | Troubleshooting and check "Disable
System Restore", Apply and IMMEDIATELY reboot. This will flush you
restore folder and erase all checkpoints, then,
System | Performance | File System | Troubleshooting and uncheck "Disable
System Restore", Apply and again IMMEDIATELY reboot. This should now
automatically create a new checkpoint immediately following the restart.
Finally adjust the space allocated to the restore folder,
System | Performance | File System | Hard Disk and adjust the restore
slider to your preferred setting. A figure of 200MB is normally more
than adequate for day to day use allowing perhaps a week of checkpoints to
be available although increasing this to perhaps 400-500MB for a few days
during periods of large installs such Microsoft Office is advisable.
--
Mike Maltby MS-MVP



McCheez wrote:

Where has ProcessExplorer been all my life? 2 minutes to download,
install and run the program, 7 seconds to find the culprit, 15
seconds to figure out how to correct it. WOW!
Apparently there was a program called STMGR.EXE running. I'm not sure
what it is, but I'm on the trail now.