Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: kd5 on April 03, 2008, 03:06:34 PM
-
Just updated to 4.8, now every time I run O&O Defrag 2000 Freeware Edition, avast! pops up a box warning me that O&O is trying to modify an avast! .INI file and (in essence) that modification of this file may result in avast! not working properly.
Thinking about going back to 4.7 until you fix this problem. -kd5-
-
If you click the More information box, what process is said to be responsible for the modification?
Thanks
Vlk
-
C:\WINDOWS\System32\OOD2000.exe
-
Thanks. The issue will be fixed in the next VPS update (due in a couple of hours).
-
Analogous warning about modification avast.ini arises when I'm trying to search in Far Manager (Far.exe) appearence of any string in the files in avast folder/subfolders.
-
The most curious is the similar message from explorer.exe when trying look at properties avast4.ini. May by self-defence is blocking modification of last access time to this file?
-
When Google Desktop Search tries to access the file this also happens.
I highly doubt it actually modifies the file, from the reports it sounds like Avast is complaining about read access.
The feature seems to be implemented very poorly, at the very least the user should have the option to "allow always" or to add exceptions somewhere in the options.
Other then that I like Avast 4.8.
-
No, avast! doesn't complain about read access, only about write access.
Here you can see how many programs request write access even though they don't need it (Explorer Properties, FAR string search).
While I think we can add Explorer to the blacklist (and deny write access automatically), I don't think it's a good idea for FAR... as this one is actually quite likely to be used to modify the .ini file by the user.. :-\
-
The feature seems to be implemented very poorly, at the very least the user should have the option to "allow always" or to add exceptions somewhere in the options.
I think not. Security is in first place. A lot of users will allow anything they're seeing in the screen.
-
No, avast! doesn't complain about read access, only about write access.
Here you can see how many programs request write access even though they don't need it (Explorer Properties, FAR string search).
It is interesting. But why I can load avast4.ini in FAR editor by F4 without any warning??
EDIT: Sorry, edited by mistake
-
It's been several hours and still no fix for the original thread topic RE: O&O Defrag. Am I to expect this will occur every time I try to defrag my computer?
How long will you be supporting 4.7? -kd5-
-
It's been several hours and still no fix for the original thread topic RE: O&O Defrag. Am I to expect this will occur every time I try to defrag my computer?
For any reason they need more than a couple of hours...
Disable self-defense module if the annoying is that much ::) ::)
How long will you be supporting 4.7? -kd5-
I don't recommend downgrade... you'll lose protection and features.
But they will 'support' 4.7, I imagine, until version 5 (unless something changes on their planes...).
-
It's been several hours and still no fix for the original thread topic RE: O&O Defrag. Am I to expect this will occur every time I try to defrag my computer?
For any reason they need more than a couple of hours...
Disable self-defense module if the annoying is that much ::) ::)
No need to be sarcastic, wasn't even aware a "self-defense module" existed. I don't want to have to disable anything and I'd rather not downgrade. I'd really rather have a fully functional avast! that doesn't protest every time I try to defragment my hard drive.
I apologize if I appear ungrateful, I very much appreciate that you offer this exceptional antivirus. Thank you for the hard work, looking forward to the bug fix... ;) -kd5-
-
No need to be sarcastic
Was not my intention. Welcome to forums ;)
-
What Vlk was trying to say is that the problem with OO will be fixed in the next VPS update - whenever it's released.
-
Ah, I didn't realize one thing - FAR is indeed just trying to reset the last access time.
The problem has already been fixed (the same as here (http://forum.avast.com/index.php?topic=34310.msg287448#msg287448)) - but it cannot be fixed in a VPS update (like that OO thing), a program update is needed for that.
So, it will take some time to release...