BudG
41
Just received this from Avast Support Ticket I had created:
06 May 2015 22:35
Hello,
We are currently aware of a problem that’s causing false positives to all our clients.
We’re working on a fix, and will push it out ASAP.
Thank you for your patience,
Avast Corporate
Robert West,
Right click on Computer Catalog
Click on properties.
Click on File System Shield
Uncheck Enable File System Shield
This is simply unacceptable and AVAST needs to fix this immediately, I am glad that so far we have not rolled out to the entire campus. This is the type of thing that causes people to find a new product as the warm and fuzzy feeling is definitely not there at this time.
Thanks for the tip dsstdf. Will do.
Go to your virus chest and restore those files AFTER turning of the file shield, there is nothing wrong with them
is there anything I can do? I restarted my pc and ran avast and deleted a ton of files, then at some point it asked me if I wanted to delete stuff in the windows system which I declined and stopped the scan. It deleted a ton of stuff from my drivers, I saw something about chrome, opera and skype too.
I hope they fix it soon. I partially destoryed one computer because i let it delete everything during a boot scan. Then i started to realize. Hey something was up. When all the sudden my whole network started to get the same virus hit.
My remote users using Logmein were all locked out. And on those systems. They barely do anything except word processing remotely.
Hello from Russia with the same problem. Thanks to this forum for the description of the problem. 
This bad definition file has wreaked more havoc than any other virus/trojan I’ve dealt with.
Users, through no fault of their own, try and do the right thing and quarantine/move to chest/delete the “infected” files and essentially make their PC’s unusable.
It will be a long day/night for many of us.
Even if they release an updated definition, we will still all be dealing with the fallout for hours if not days.
Here is a reply from a ticket I submitted earlier.
//
Hello,
We are currently aware of a problem that’s causing false positives to all our clients.
We’re working on a fix, and will push it out ASAP.
Thank you for your patience,
Max Marak
Avast Corporate
//
BudG
52
Having problems here with a number of computers. Those that aren’t restarted seem to be OK, but if they run a boot time scan that seems to be the start of the real problems.
Anyone have a good fix for what was destroyed during the boot time scan? I don’t know yet what the user may have specified to do with the files, but it sounds like at least one computer isn’t booting now.
@Avast Lab: any news about this?
So far it’s only hit two of the machines I have here, but in both cases it’s flagged ATI driver dll files causing the ATI display manager to throw a fit.
This is a mess, really bad we need this fixed NOW…
Calling an all-hands-on deck here at my department.
This is REALLY bad - second-guessing our decision to go Avast at this point.
is there a resolution to this. I have over 30 computers on the network went all down after they got this message. Avast says you have to clean the machine we click yes it restarted the machine and all i get is a blank screen on all of them
I’m not going to criticize too much; every AV vendor has had major false positive incidents. This one has been the most disruptive I’ve personally had to deal with, though.
If you’ve decided not to turn off file system shield, make sure you tell your end users to click “No” if Avast asks to schedule a boot time scan and restart. Otherwise, you’ll probably end up having to do a System Restore (or worse) to get your machine back to a usable state.
I took the action of notifying them not to have it do the reboot/scan and then went into the AEA and set it so that the Shield took no action on anything related to file scans. I have it emailing me the notifications so I have a list of computers I may need to visit. Just waiting on the updated definition now.
