EICAR NOT DETECTED by File System Shield !?!?

[bob3160]

Hi Bob, what does that have to do with this topic? I'm not talking about the "web shield". The problems are with the "file system shield" (and using only that shield).

The file never made it to the file shield. It was blocked before it ever got to my computer.
Proactive is certainly a lot better than after the fact.

[Skakara]

Bob, your posts are off-topic. Sorry. This topic is NOT about protection in general. I repeat:

I've to say that I'm dumbfounded that nobody seems to care.. nor understand. There's obviously an anomaly how the File System Shield works with the "Scan when writing -> scan files with default extensions" default setting.

You, and nobody else, is not interested that one of the protection layers does something odd which is against what the shield is set out to do?! In an AV-product!! I'm losing my faith here.. about Avast, about other users here in forum.

[REDACTED]

Edit:  I have somehow missed reading several pages of this thread, having read only to the bottom of the first page, so the information I posted before here was kind of off topic.  I apologize.

If you are able to get a file on disk that's known malware, even though Avast is supposed to be able to detect it, then you are right for posting it as an issue here.

That said, there is the capability to schedule thorough scans for a reason...

-Noel

[Skakara]

I just can't believe the protectionism and fanboyism here. Your post is too off-topic. Jesus christ, this is frustrating. In general this forum seems to run in a certain way: Avast doesn't answer, and loyal fans drives the OP insane.

ALL, READ THIS POST CAREFULLY: an anomaly how the File System Shield works with the "Scan when writing -> scan files with default extensions" default setting

Though I think that it's a moot point since nobody either does not read it, or doesn't understand it at all. This is really uncanny. Usually people (end users & product team) are interested about possible faults in the product. I'm reporting bugs/etc. with lots of programs/services and this is easily the most "not caring" community that I've EVER seen during these ~15 years that I've been doing this (for the benefit of me, and others).

EDIT: Ok, Noel, thanks for notifying.

[REDACTED]

I have amended my post, not having seen that there were multiple pages to this thread.

-Noel

[bob3160]

Bob, your posts are off-topic. Sorry. This topic is NOT about protection in general. I repeat:

I've to say that I'm dumbfounded that nobody seems to care.. nor understand. There's obviously an anomaly how the File System Shield works with the "Scan when writing -> scan files with default extensions" default setting.

You, and nobody else, is not interested that one of the protection layers does something odd which is against what the shield is set out to do?! In an AV-product!! I'm losing my faith here.. about Avast, about other users here in forum.

You post has been reported to the Mods that's as much as I can do to get your concern noticed.

[Skakara]

You post has been reported to the Mods that's as much as I can do to get your concern noticed.

Ok.. I guess? I'm not sure whether you're being really helpful (if you are, thanks!).. or doing something else.. since the reporting is to "inform the moderators and administrators of an abusive or wrongly posted message" and I don't think that would help the issue here getting noticed.

[bob3160]

You post has been reported to the Mods that's as much as I can do to get your concern noticed.

Ok.. I guess? I'm not sure whether you're being really helpful (if you are, thanks!).. or doing something else.. since the reporting is to "inform the moderators and administrators of an abusive or wrongly posted message" and I don't think that would help the issue here getting noticed.

That depends on who and how the topic is reported.
In this case, it's to draw attention to the topic and hopefully get some input from the folks you're trying to reach.

[Skakara]

Ok, MILLION thanks for the clarification & the help!