Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Tyreman on December 08, 2011, 11:38:23 AM
-
Brother printer software was identified as a threat, its not a threat.
c:Program files/x86/Brother control center 3
-
same problem here - Brother Control Center 3 now keeps being sent to the vault automatically, identified as Malware, false positive
-
Ok, have you submitted as a FP yet? Or are you asking how?
-
Ok, have you submitted as a FP yet? Or are you asking how?
Notifying about the problem.
-
If you have it in the chest, right click on it and report it as FP to avast labs from there.
-
yep, reported it as a FP in the GUI, just wanted to add to the note here in case other folks come searching for info in the forums
-
I got the same trouble on different systems - all from today, all on Auto-Updated Systems!!!
The first Upload to aVast's Virus-Lab are done!
Are there any insights?
Under Win 7/64 the actual manufacture file had 114688 File-size, stamped at 24.12.2008 at 08:46:54 as last modified date and located under C:\Program Files (x86)}Brother\ControlCenter3
Any hints, suggestion, or stuff like this?!
-
Any hints, suggestion, or stuff like this?!
Seems to be a FP. ;)
As it's already reported it should be fixed soon.
-
Same problem here.
Is it necessary to manually exclude brother Brother control center 3 from scanning to be able to use printer at meanwhile? I only got 3 options delete, move to chest and block neither of there allowed driver to start normally.
-
Same problem here.
Is it necessary to manually exclude brother Brother control center 3 from scanning to be able to use printer at meanwhile? I only got 3 options delete, move to chest and block neither of there allowed driver to start normally.
You can add the program file to the exclusions in file system shield for the time being while your waiting for the false positive to be fixed.
-
I did eventually found the correct menus. In case of someone else is recently switched from another AV-product to Avast! as Me. Here is short guide how to repair and exclude.
1. From Avast! main menu go to Maintenance -> Virus Chest
At Virus Chest Click with right mouse button the line:
BrCtrCen.exe | C:\Program Files (x86)\Brother\ControlCenter3
(I got many of the above lines because of multiple driver re-installation attempts they were located just in different directorys)
Select the Restore option from pop-up window.
2. Then go to REAL-TIME SHIELDS menu and click Expert Settings button next to the right border.
From a new pop-up window select exclusions menu and add the the directory mentioned at phase one to the excluded directories by clicking small add button at bottom of the window.
3. Reboot and Brother control center should be back up.
-
I did eventually found the correct menus. In case of someone else is recently switched from another AV-product to Avast! as Me. Here is short guide how to repair and exclude.
1. From Avast! main menu go to Maintenance -> Virus Chest
At Virus Chest Click with right mouse button the line:
BrCtrCen.exe | C:\Program Files (x86)\Brother\ControlCenter3
(I got many of the above lines because of multiple driver re-installation attempts they were located just in different directorys)
Select the Restore option from pop-up window.
2. Then go to REAL-TIME SHIELDS menu and click Expert Settings button next to the right border.
From a new pop-up window select exclusions menu and add the the directory mentioned at phase one to the excluded directories by clicking small add button at bottom of the window.
3. Reboot and Brother control center should be back up.
Those instructions would be fine if:
1_ You can be 1000000% sure it is a FP; AND
2_ you want to keep using it without reporting it.
When you report the FP, avast can correct it and everyone gets the benefit.
So, in addition to that procedure, I would add the right click and report to avast inside the chest.
Finally, return to the chest after the definitions update, right click on the reported file and rescan it with the new definitions. If it turns to be clean this time, then you can restore it (if it hasn't been restored yet), delete it from the chest list and remove the temporary exclusion / exception you added to the File System Shield.
-
Happened to me this morning, Brother Control Center 3, uninstalled drivers and app and reinstalled twice, EVERY TIME Avast would quarantine the app, can' use printer controls, uninstalled AVAST after making 2 FP reports.
Wasted an hour this morning, got the day off to a BAD start, and not-a-happy-camper.
-
:: some stuff ::
Those instructions would be fine if:
1_ You can be 1000000% sure it is a FP; AND
2_ you want to keep using it without reporting it.
When you report the FP, avast can correct it and everyone gets the benefit.
:: some other stuff ::
I agree with "ady4um" - absolutely!
Before it isn't 1000000% sure that this "False-Positive" and NOT a virus, shouldn't use this "evasion". It's also a known technique of several viruses, malware and bad scripts tu search for such False-Positive to exploit this vulnerabilities! I advise my clients and friends rather to dispense for those functions and services, such as to open these "back doors" by himself.
Often, then forget to close again these "security gaps" and thus remains a major risk are still open. Don't do that and use the best, the right way: Send EVER such Files into your Virus container and from there, you can send it up to the virus Labs from aVast.
The avast staffs are really fast and I'd seen by some own Uploads that they came within hours with a corrected update. Here it is worth to act in the sense of community, to send those files up to the Labs and have some patience.
-
Here it is worth to act in the sense of community, to send those files up to the Labs and have some patience.
+1
-
UPDATE YOUR AV-Database!
The FP was fixed tonight by aVast and is not longer shown as a Virus!
Thx 2 the aVast-Crew!
I'm (as always) very proud that "my" aVast again responded so quickly and so fixed (again) so fast what my Protect made so save! As i told your: the aVast-Crew are really FIT and FAST!
- THANK YOU -
-
Thanks for the positive feedback..! :)
-
UPDATE YOU AV-Database!
The FP was fixed tonight by aVast and is not longer shown as a Virus!
Thx 2 the aVast-Crew!
I'm (as always) very proud that "my" aVast again responded so quickly and so fixed (again) so fast what my Protect made so save! As i told your: the aVast-Crew are really FIT and FAST!
- THANK YOU -
Thanks for the heads up. How in the world an app that has been out literally for years gets listed as a virus and rendered useless is a mystery to me.
It would have been a good touch if those of us who posted a FP report would have gotten an email advising us that it's fixed. Perhaps that's coming later today?
This was really not fun, and a black spot on an otherwise positive experience with this product. I have recommended AVAST to many friends and co-workers. Hopefully this will be a once in a lifetime mistake.
-
It would have been a good touch if those of us who posted a FP report would have gotten an email advising us that it's fixed. Perhaps that's coming later today?
No, they don't do that, they would rather spend money elsewhere. Imagine the time sending emails for a false positive that even effected a single percent of their user base of many millions of people.....it would take longer than it is worth.
How in the world an app that has been out literally for years gets listed as a virus and rendered useless is a mystery to me.
No one posted what the specific detection was, but it was probably a Generic signature, they use those so one signature can catch many forms of malware.
Avast! is very low on FPs.....I mean very low....so while it might be a bit much to think this is a "hopefully once in a lifetime event" (if you mean a FP in general), take heart that you have what is at any given day the AV with the lowest false positive rate possible.