Someone is confused here...
"Ignore" is there, it's just called "No action" or "Block".
Why couldn't you configure on-demand scanner differently than on-access one? Sure you can...
first, there's no confusion on my side, you're confused about my interpretation: although the interface itself would be somewhat confusing due to an improper wording, it's not anymore once you've tested it with an Eicar file and seen what it does. To put it simply, the "ignore" command doesn't exist at all. Don't tell me how it was in V4, I have no idea anymore, I tested it once or twice ages ago with Eicar had one FP two years ago so...and no infection in the meantime.
This said, you cannot assimilate "no action" to "ignore" or "block" to "no action" because this wording doesn't make any sense...not in "real" languages anyway
Also, "no action" for manual scans gives you the option in the result panel to "do nothing" if you want, when "no action" when set in file system shield will block files automatically, so there's a major behavior difference. Give it a try
Again, what's needed is a "real" ignore option, that as VLK suggested yesterday, could be called an "add to exclusion list" and avoid the pain of having to restore hundreds of FPs (from Chest, when it works...) in the case of an incident like yesterday. You seem to be very unwilling to add this "real ignore option" from the beginning of the beta testing, referring to dangerous fast clicks for noobs, sorry but we're running our own computers and I do not accept to be left with the choice between, sending to chest, block or delete. In the end the data is mine, and I wanna do what I want with it, especially when it can instantly save my system from being crippled with 10000 FPs... once numerous FPs are in Chest, restoring (again, when it works...) won't necessarily work, especially with systems files...>>> system lockups...reboot... system lockups again etc...etc...I'd rather avoid my system to break than having to attempt a repair through avast Chest sorry...
It's been suggested to many yesterday to wait...no panic...wait and wait...attempt to restore from Chest...you must be kidding
My system wasn't affected I got luck, but if it had happened, you seriously think I would have trusted a system composed with thousands of files restored from the Chest
I would have attempted a sys restore, and if not good enough or fail, reinstalled Windows + programs in no time and waited for the update correction before reinstalling avast. I would have lost two hours, not a minute more. Better than wasting the whole day looking for solutions on the forum.
You know, unfortunately, a majority of the users who logged in to complain yesterday were people who don't have a freaking clue about how to run a computer. For many of them Windows was just broken (really broken) and they will have to pay someone to reinstall their OS. You'll be surprised: I won''t blame Avast for this. these guys must understand that buying a PC is not buying a TV...I guess they'll never make...this difference. Many of them just didn't catch that an FP slaughter was going on, and instead of dealing accordingly, they launched a full scan with Avast, or worse, a bootscan
So may be you can help them, may be you can't, but in all case leave to those who know what a computer is the option to decide what to do when something's detected >>>> IGNORE OPTION... again, thanks.
adding: a useless alternative to "send to chest" is this non-sense called "no action" blocking files for real time shields. How the hell do you unblock files then...again, the option doesn't exist...other then adding the whole system in the exclusion list may be...
also, did you notice that once a file is sent to Chest, after a manual scan, it's just sent to Chest, but when it is by a real time shield, it leaves a zero byte file in the original location? why is that?
