@pc: "Assistance would be appreciated. Went to do a  System Restore tonight, and 
all previous Restore Points appear to have been deleted. Appears to be now 
working OK, and I have created one as a test, which appears to work. After 
finding problem, I checked the Event Viewer and found the following error 
there.
<The System Restore filter encountered the unexpected error '0xC00000A1' 
while processing the file 'shell32.dll' on the volume 'HarddiskVolume1'. It 
has stopped monitoring the volume.>
Can anyone please explain what this means ? and is there anything I can do 
to ensure it doesn't occur again ?
Kind Regards,
PhilC"
    @MAP: "<quote>
system restore and reboot then turn S/R back on again.This will clean out any 
corrupted files (restore points) that will cause problems with S/R."
    @msnews: "<quote>
-
	Exactly how can one determine when to do this?  My old explore points
just go away as space fills the restore area.  How can I determine when
Windows has stored a corrupted store point?  Seems the only way to detect
a corrupted store point is to try to restore to it, though I've noticed I
seem to have the most problems after intstalling Windows Critical Updates.
	Perhaps some of the Critical updates corrupt the restore points
to disable uninstalling those updates that are supposed to be uninstallable?
-l
-
Email:        to send me email, then my address would be like
                  'earthlink' was 'tlinx' and 'net' was 'org'"
    @bert: "Hi Phil,
What is the Event ID and Source from the Event Viewer?
Regards,
Bert Kinney [MS-MVP DTS]
<url>
<quote>"
    @bert: "<Answer inline>
<quote>
This is not necessary. The only way to tell if a restore point has 
gone bad is to try to restore with it.
The best way to protect restore points is to keep the system free of 
virus and spyware/malware infection. Here are some instruction on 
doing so.
<url>
This is normal. When the store fills up the oldest restore points are 
deleted to make room for newer ones.
It is possible critical updates could cause this, but I suspect it 
would be a bug in the update.
Regards,
Bert Kinney [MS-MVP DTS]
<url>"
{'source': 'USENET', 'other_information': '{"reply_count": 4, "forum_name": "microsoft.public.windowsxp.perform_maintain.20140611.mbox"}', 'file': 'data/output/usenet-microsoft.public.parquet'}