Avast "SetIFace.dll" is really messing with system restore

[LTS]

Hello,

This problem might take someone who's an expert with the inner workings of Avast.  I've googled and searched this forum...no solution found.   Avast Setiface.dll is a part of Avast and it has been corrupting my system restore over and over for a week now.  I need help please.  I have experimented and tried everything from resetting the maximum's restore holds, to disabling each partition individually and both together, to totally removing System Restore and re-installing, etc., etc., etc.  Because of Setiface.dll, automatic restore points are not created at all and although I can create a manual restore point, the Setiface.dll problem deletes it.  It deletes my manual restore when starting, restarting, and also just while I'm on the computer, whenever it feels like it.   

Here is the error that is created in System Event Viewer:

Event Type:   Error
Event Source:   sr
Event Category:   None
Event ID:   1
Date:      3/5/2006
Time:      5:41:36 PM
User:      N/A
Computer:   MY COMPUTER
Description:
The System Restore filter encountered the unexpected error '0xC0000034' while processing the file 'SetIFace.dll' on the volume 'HarddiskVolume1'.  It has stopped monitoring the volume.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 00 00 04 00 4e 00   ......N.
0008: 00 00 00 00 01 00 00 c0   .......À
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........


This coincides EXACTLY with Avast's "Library Setiface.dll was successfully updated" time in the Avast info log as follows:

3/5/2006   5:41:36 PM   1141609296   SYSTEM   1584   Library Setiface.dll was successfully updated. 


I don't know if it is relevant or not but the info in the Avast log just prior to this is:

3/5/2006   5:39:51 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestInit. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestStart TcpIp=0 Lrpc=1. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestAddSystemFiles. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestOpenListLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestNextFileLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:52 PM   1141609192   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:53 PM   1141609193   SYSTEM   1584   Info from aswChestS: chestGetValueLoc. 
3/5/2006   5:39:53 PM   1141609193   SYSTEM   1584   Info from aswChestS: chestCloseListLoc.

I've googled and experimented till I'm blue in the face.  I can come up with the "unexpected error '0xC0000034' while processing....", other files, but none pertaining to the specific "Setiface.dll" file. 


1) What is Setiface.dll anyway...and what is it's function?

2) I'm assuming this is not in reference to my main system partition, but rather the extra partition based on 'HarddiskVolume1' ('HarddiskVolume0' is my main system partition where windows is installed).  Yet, my manual restore points are removed from the system period!...no matter what I do with restore settings for the partition(s).

3) Are the "from aswChestS" logged notations above normal?...because when I start my other computer (laptop) I don't get these logged, only the "Library Setiface.dll was successfully updated".  I'm also not having this system restore problem on my laptop.

4) Should it take two minutes to complete from the first Avast log entry to the last log entry?.. (5:39 p.m. to 5:41 p.m.).  Could this length of time be holding up and creating problems with system restore?

5) Any clue on why Avast "Setiface.dll" is now causing this problem out of the blue and how to fix it?

6)  Could my Avast on this computer be "corrupt" somehow?  I hope not.  I've read horror stories about uninstall/reinstall problems.

Before anyone suggests it, I know this has nothing to do with lack of space on my hardisk.  I have plenty of free space on my main partition (& have disabled restore monitoring to double check this isn't the issue...no change), I think plenty of space on the extra partition (& I've disabled system restore monitoring on that partition as well, with no change), I'm not getting any system restore warning error regarding lack of space (which I should if that was the problem) and I've never had this problem before and I do not add anything to that extra partition.  My computer came with that partition and the space left on it has not changed.

I've run Spybot and Adaware (many times) and have run a full Avast scan.  No problems reported (as usual)....I try to stay well protected. 

I really want to get this problem resolved.  I can't imagine why this just started happening, but it's definitely related to Avast, so here I am.  I've been a week without a restore point.  That makes me very nervous .  I have had occassion to use system restore in the past and using it has always been successful and saved me.

I've tried to relay everything I think pertinent, but PLEASE, if I need to supply something else, let me know!

Thanks much for any help...
LTS
P.S. Using the current Avast Home (free) Edition, VDB is always current, WinXP SP2, Zone Alarm, SpywareBlaster, SpywareGuard, Spybot, Adaware.  These have always been present (same on my laptop, which isn't having this issue).   

[igor]

Because of Setiface.dll, automatic restore points are not created at all and although I can create a manual restore point, the Setiface.dll problem deletes it.  It deletes my manual restore when starting, restarting, and also just while I'm on the computer, whenever it feels like it.

I'm sorry, but Setiface.dll doesn't have anything to do with System Restore - i.e. it doesn't delete the restore points, or interact with System Restore in any other way intentionally. It rather seems to me like System Restore has some strange problems with this file.

The System Restore filter encountered the unexpected error '0xC0000034' while processing the file 'SetIFace.dll' on the volume 'HarddiskVolume1'.  It has stopped monitoring the volume.

Error 0xC0000034 means "Object Name not found." (which is a NativeAPI equivalent of the common ERROR_FILE_NOT_FOUND - "The system cannot find the file specified."). I have really no idea why System Restore cannot find the file (and what file it actually is).

I've googled and experimented till I'm blue in the face.  I can come up with the "unexpected error '0xC0000034' while processing....", other files, but none pertaining to the specific "Setiface.dll" file.

Yes, it seems that this is not an isolated incident - more people had this problem (without any connection to avast!, so it's probably not the one to blame).

1) What is Setiface.dll anyway...and what is it's function?

avast! module responsible for all updating functions.

3) Are the "from aswChestS" logged notations above normal?...because when I start my other computer (laptop) I don't get these logged, only the "Library Setiface.dll was successfully updated".  I'm also not having this system restore problem on my laptop.

No, not really. It seems you have different sensitivity of logging set on the other computer. Check avast! settings / Logging / Logging level.

4) Should it take two minutes to complete from the first Avast log entry to the last log entry?.. (5:39 p.m. to 5:41 p.m.).  Could this length of time be holding up and creating problems with system restore?

The log entries are written continuously, and are basically independent. So I don't see anything strange in this particular time interval (depends on many things, such as other programs you have on startup, your Internet connection, ...).

5) Any clue on why Avast "Setiface.dll" is now causing this problem out of the blue and how to fix it?

No
I'd guess on some corruption of System Recovery, but I'm really out of ideas on what to do about it.

6)  Could my Avast on this computer be "corrupt" somehow?  I hope not.  I've read horror stories about uninstall/reinstall problems.

I don't think there's any horror here, reinstalling should be rather easy - but no, I don't think avast! is corrupted.

[LTS]

Hi Igor and thanks for trying to address this.

First, how did you get those quote boxes in your response?  That would make this response (and future ones from me) easier to read for sure.

Anyway...

I'm sorry, but Setiface.dll doesn't have anything to do with System Restore - i.e. it doesn't delete the restore points, or interact with System Restore in any other way intentionally. It rather seems to me like System Restore has some strange problems with this file.

I'm still guessing it does in this case as indicated by the event viewer error specifically naming Setiface.dll as the "culprit" and the Avast info log showing "Library Setiface.dll was successfully updated" at precisely the same time (every time).  This is exactly when my restore points get removed.  Yet, my laptop doesn't seem to have a problem with this file in regards to system restore?

Error 0xC0000034 means "Object Name not found." (which is a NativeAPI equivalent of the common ERROR_FILE_NOT_FOUND - "The system cannot find the file specified."). I have really no idea why System Restore cannot find the file (and what file it actually is).

The actual file is indicated in the error (Setiface.dll).  That is what can't be found.  But I've checked and this file is in the appropriate place, appropriate size, version, etc. and a search reveals no others lurking on my computer.  I actually did a scan of Setiface.dll to make sure it wasn't infected.  It isn't according to Avast....smiles.

Yes, it seems that this is not an isolated incident - more people had this problem (without any connection to avast!, so it's probably not the one to blame).

Others do have this "System Restore filter encountered the unexpected error '0xC0000034' while processing the file....".  Admittedly not the Setiface.dll file, but the error refers to this file as the problem in my case.    When Avast does it's "Library Setiface.dll was successfully updated" thingy, my restore points go bye bye.  I just don't know how to fix it. 

avast! module responsible for all updating functions.

So basically, my thinking is that as the avast module is updating it somehow corrupts or conflicts with my system restore functions.

No, not really. It seems you have different sensitivity of logging set on the other computer. Check avast! settings / Logging / Logging level.

Actually my settings for logging are exactly the same on both computers.  But today I noticed my laptop also logged the extra's.  Must just be a random or as needed thing.  Not a problem. 

No
I'd guess on some corruption of System Recovery, but I'm really out of ideas on what to do about it.

I'm hesitant to think so because I've also followed instructions to completely remove system restore, rebooted, re-installed system restore, rebooted, created a manual restore point, rebooted....and same thing.  As Avast does it's updating and logs it, I get the system event viewer error at exactly the same moment (down to the second) and my restore point is then gone.

Again, I appreciate your response.  I didn't want to have to do this but at this point since I've already re-installed system restore with no success, I guess I should try uninstalling and reinstalling Avast.  Tell me, since I want to make sure all reference to Avast is gone before re-installing (in case there's some ugly reference to this problem lingering around my computer) would you suggest I use Add/Remove Programs or the Avast uninstall cleaner?  Can I use both?  Which first?  Does Avast leave anything behind in the computer or the registry after un-installing with either?

It's scary uninstalling/re-installing without restore points!

Thanks Igor...

LTS   

Edit:
Forgot to also ask.  I thought about starting my computer without Avast loading to see what happens.  How do I disengage Avast from loading on startup?  Thanks.