System Restore fails and deletes all restore points

[Guest]

I keep getting the following message in event viewer...
The System Restore filter encountered the unexpected error '0xC0000034'
while processing the file '~efe2.tmp' on the volume 'HarddiskVolume3'. It
has stopped monitoring the volume.

When this occurs all of my restore points are deleted. I have Identified the
source of the file as occurring in the temp folder
local settings\temp\Adobelm_Cleanup.0001.

I believe this is adobe license manager temporary file. I have 5 identical
machines in my department (XP Pro SP2) all running adobe acrobat 7 with
latest updates and they all have the same error appearing in the system event
log.

Also I have noticed that when I mount a virtual disk file that system
restore tries to monitor the changes on that virtual drive and it crashes
system restore also, i get the following entry

The System Restore filter encountered the unexpected error '0xC0000010'
while processing the file 'cpfiles.bat' on the volume 'FileDisk0'. It has
stopped monitoring the volume.

I never see the option to enable or disable monitoring of the vitual drive
but SR does it anyway.
Why is system restore so fragile? Is there anything that can be done to
remedy these kinds of problems.

 

[Bert Kinney]

I keep getting the following message in event viewer...
The System Restore filter encountered the unexpected error
'0xC0000034'
while processing the file '~efe2.tmp' on the volume 'HarddiskVolume3'.
It
has stopped monitoring the volume.

Stop System Restore from monitoring drives/partitions other than the one
Windows is installed on. HarddiskVolume3 apears to be a partition other
then the system drive.

 

[Guest]

In this particular instance HarddiskVolume3 is the system drive (F. I find
it difficult to understand why system restore is monitoring the contents of a
temporary folder.

 

[Bert Kinney]

Hi,

System Restore automatically monitors any partition it sees, other than
very small ones. Unfortunately, that is the way it was designed.

A possible work around is to assign a permanent drive letter (the higher
in the alphabet the better) to the external drive via Disk Management.