Re: Avast: Ini File Modification screen

[vizio1]

It would be helpful if you could include the name of the process trying to update the avast4.ini file - this appears at the bottom of the popup alert.

windows/system32/zonelabs/avsys/scanningprocess.exe

This is what I'm showing as the requesting program on teh re-write ini popup.

I'm running XP Pr and ZA Security Suite 7.0.470.000

[DavidR]

I believe you need to uninstall/disable the ZA anti-virus module as having two resident AVs on the same system is the recipe for conflict.

[Lisandro]

Pleaswe could Tech advice what I need to do ASAP and when teh update that corrects is being issued.

Can you answer the questions from Alanrf?

[psw]

I install 4.8.1178. It seems to me that the problem with ini file modification was not solved in this pre-release. At least I'm obtaining the same modification warninng during search in Far Manager.

[Vlk]

I install 4.8.1178. It seems to me that the problem with ini file modification was not solved in this pre-release. At least I'm obtaining the same modification warninng during search in Far Manager.

Well, the Far issue...
As a long time Far user, I'm sad to say that this issue is virtually unsolvable.
The problem is that when doing a file search, Far indeed opens all files with full Read/Write access and there's no way for us to distinguish between the Search case and an Edit case.

Vlk

[psw]

Thanks. Will wait the next Far release. At least open sources of next Far release contain correct attributes using during search (FILE_READ_ATTRIBUTES|FILE_READ_DATA|FILE_WRITE_ATTRIBUTES) and this combination works silently with Avast!.

[JWJr]

The problem is that when doing a file search, Far indeed opens all files with full Read/Write access and there's no way for us to distinguish between the Search case and an Edit case.

It's a very small file (10K on my machine). Can't you just save the contents on an unauthorized write open, and then put it back the way it was when the file is overwritten or closed?  -JW

[Lisandro]

The problem is that when doing a file search, Far indeed opens all files with full Read/Write access and there's no way for us to distinguish between the Search case and an Edit case.

It's a very small file (10K on my machine). Can't you just save the contents on an unauthorized write open, and then put it back the way it was when the file is overwritten or closed?  -JW

I understand your wishes... but seems a FAR issue and not avast.
Can't you exclude avast folder into FAR settings?

[mimi1001]

This is part of the new self-defense function in avast 4.8.

At the bottom of that popup message from avast is the name of the process that is trying to make the change.

Next time you see it please post it here.

I'm having the same problem.  the process is: c:\program files\common files\aol\1145386897\ee\aolsoftware.exe.  What to do?

[DavidR]

Same problem, same solutions as previously suggested have you tried any of them ?

If you try a forum search I believe that there has also been a topic even closer to your problem as it directly related to AOL.

[Lisandro]

I'm having the same problem.  the process is: c:\program files\common files\aol\1145386897\ee\aolsoftware.exe.  What to do?

Why the hell AOL software needs write access the avast4.ini file?