I am currently using the latest beta 6.0.1044 to ‘fix’ a BSOD issue, as advised. However, I have noticed that the File System Shield has been significantly delaying the execution of some exes. One example. There is a freeware tool called ArcConvert by Dirk Paehl which takes up to 13 seconds to appear after I execute it, but once the File System Shield has been disabled it appears instantaneously. This makes the Avast scanning process far from transparent, as it is far from a minor delay.
Having a hunch I checked the exe and it is compressed using a PE compressor. All I can say is that Avast doesn’t have a problem with executable if it is unpacked. Unpacked it appears instantaneously after execution. So Avast seems to have problems scanning some compressed exes. It seems to me there is room for improvement here. A 13 second delay is just horrendous.
mp3Recorder by ACE-HIGH = 3 to 4 seconds delay with FSS on / 0 seconds FSS off.
VideoReDo by DRD Systems = 7 to 8 seconds delay with FSS on / 3 seconds FSS off
Why don't you add your exe file to the exclusion entry in file system shield?
Of course that is what I have done. But defeating the File System Shield by excluding every file Avast takes a while to scan isn’t really a solution, and I would imagine Avast might want to have a look at this issue.
It’s not the end of the world of course, and as the majority of the software I use isn’t affected to any noticeable extent, or is only fractionally (< 1s ) delayed by the scan, I’m hardly going to create a stink about it.
Why does Avast have to scan the same files over and over when they are executed? Is there no way to checksum the clean files to save unnecessary further examination? Didn’t Dr Solomons used to do that?
When you add those files, you can exclude them only for read and execute operations and leave them scanned when writing. So you will still get alerted if somehow they are being tampered with and written back to disk.
I think I’ll start making a list as there are so many. Another file Avast is having fun with is DiskInternals Linux Reader which I installed the other day…well it’s more a resource library in the installation folder. Avast doesn’t like the Alligator.k52 file in the install folder, and hogs the system when it finds it. When I select the file and select properties from the Windows right-click context menu there is another 3 second delay before the properties window appears as Avast scans it again. Once the properties window is visible if I choose a properties sheet such as ‘Version’ there is a further delay as avast then scans the file again…on about invasive. It’s getting on my pip.
On examination the file is a heavily compressed Win32/PE. Unpacked […] and UPXed Avast doesn’t have any problems with it. edit: yes it does. Also delays when UPXed.
I like to be protected, great, but Avast keeps getting in my face.
