I don't think you can, and further, if the designer of sdelete thought
about this (and he probably did) he probably would have thought it was a
desirable outcome. The point of sdelete is to securely remove traces of
data from the disk. Some of that data may be preserved in the restore
points, so if you really wanted to be secure about deleting things, you
probably would first disable system restore (thus deleting all of the
restore points) and then use sdelete.
In any case, it's actually surprising that you even keep one restore
point. Are you sure that this isn't a restore point that's newly-made
after sdelete completes?
This is how System Restore is supposed to work:
<quote>
System Restore requires a minimum of 200 MB of free disk space on the
system drive at installation. When the amount of free disk space falls
below 50 MB on ANY monitored drive, System Restore switches to standby
mode and stops creating restore points. All restore points are deleted at
that time. System Restore reactivates and resumes creating restore points
as soon as 200 MB of disk space is free on the system drive.
</quote)
If you want to know more, I suggest you post in microsoft.public.security
or one of the related newsgroups.
--
Lem -- MS-MVP
To the moon and back with 2K words of RAM and 36K words of ROM.
http://en.wikipedia.org/wiki/Apollo_Guidance_Computer
http://history.nasa.gov/afj/compessay.htm