Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Lateral on July 19, 2014, 11:55:34 PM
-
Hi guys
I am running 2014.8.0.2021 on a Window XP PC.
Since I upgraded to 2021 a few weeks ago, Avast seems to be telling me it has detected a Threat during my scans and displays the attached screen saying "Threat Detected". When I click on the "Show Results", nothing happens.
I have "High Sensitivity", "Systsem Drive" and "Rootkit FUll Scan" selected.
I then look in the Virus Chest and Scan History and there is nothing...
I have Avast set up to send me an email if a Threat is detected but no email is being sent.
I also have a client with Avast installed on a Windows 7 PC and he has had the same issue as well. He is running 2021.
Any ideas?
Update: I just started a custom scan using just "Rootkit (Full Scan" and it was running for about 10 minutes. i then paused it in order to check the settings on the Weekly scan. When I selected Weekly scan, Avast displayed "Threat Detected" and when I clicked "Display Result" nothing happened. I then clicked the custom scan and the "Threat Detected" message disappeared. I then clicked Weekly scan and still no "Threat Detected" message.....
Regards
Greg
-
What SP version do you have installed?
Is/was there another anti-malware software on the system?
Have you already tried a repair of avast?
-
Hi Eddy,
By "SP" I assume that you mean what version of XP SP I have installed?
I have SP3 and all of the last updates etc.
I also have Malwarebytes installed. It has been installed for a long time without issue. I have run a Malwarebytes scan and it has not found any threats.
I have not tried a repair of Avast. How is a repair done?
I am re-running the same Avast scan that displayed the "Threat Detected" message to see if I can reproduce the issue.
Do you think it could be something to do with the "sensitivity" setting being set to high?
Regards
Greg
-
For a repair:
start > control panel > software > avast > remove > choose repair.
What vps version do you have?
Do you seen anything about this in the log files?
-
Hi Eddy
What is "VPS"?
There is nothing in the logs.
I also just ran the same scan again and no problem.
Regards
Greg
-
VPS refers to the virus update. Are you getting automatic virus updates? If so, tell us what the last update was (it will be a number).
-
Yes, the virus signature file is being updated automatically.
I currently have 140719-1 (Release date 20/07/2014)
Regards
Greg
-
With the updated Avast VPS, re-run the Quick scan to see if it still detects anything. You always want to make sure your virus definitions are updated whether you are using Avast or MBAM or any other security software. Let us know the results. Thanks.
-
Will do
-
It happened again on both my Windows XP Pc and my clients Windows 7 PC.
My PC was running the daily Quick Scan.
I reran the Quick Scan to see if I could reproduce it but no luck.....something strange is going on....
Does AVAST have any sort of "debug/trace" mode that I can turn on to see if we can find out what's going on?
Regards
Greg
-
Hi Guys
It has once again happen this morning when I checked the overnight Quick scan that is done each day.........Threat Detected...
Does anyone have any ideas?
I have not yet done a repair and will do so to see if that stops the issue...
Regards
Greg
-
Hi Guys
It has once again happen this morning when I checked the overnight Quick scan that is done each day.........Threat Detected...
Does anyone have any ideas?
I have not yet done a repair and will do so to see if that stops the issue...
Regards
Greg
There are already at least 2 other threads on this topic.
One user has responded stating that Avast has acknowledged this as a bug and stating that it will be fixed asap.
-
I'm starting to believe the errant pop-open of the Avast UI after a scheduled scan and the misnomer that there is a "THREAT DETECTED!" are one and the same bug, or at least closely related.
I was greeted this morning by the little pop-up scan box at the lower-right of the screen stating "No Virus Found", AND the main Avast UI saying "THREAT DETECTED!" simultaneously. The pop-up message disappeared on a timeout before I could screen grab the obvious disparity, but I did capture the error another way.
First I tried to click the big [ Show Results ] button in the main UI, and nothing at all happened when I did that. That was the first indication that the "THREAT DETECTED!" indication is bogus.
Then I clicked the Scan history link and it showed the scan results I've captured in the attached image, which indicate no malware was found.
I tried choosing "Show the last pop-up message", but it only showed the Scan at 0%, not the "No virus detected" message that was on the screen when I first woke up the monitors.
Avast Engineering, though this is likely not affecting the efficacy of your product to block actual malware, it'd be really nice if you'd fix this bug soon.
Thanks.
-Noel
-
Already acknowledge by Avast
Doesn't really need all this shouting. :(
-
Congratulations on increasing your post count, Captain Obvious.
Now listen very carefully: I'll emphasize what I please.
Stop heckling me, unless you'd like more of the same in return.
-Noel
-
Calm down peoples, there is no need for this.
-
There are already at least 2 other threads on this topic.
One user has responded stating that Avast has acknowledged this as a bug and stating that it will be fixed asap.
Thanks Bob for letting the calm users know :)
-
As far as I know, no one has confirmed that the false "THREAT DETECTED!" indication is tied to the inappropriate pop-open of the Avast UI. If I'm wrong here, please post a link, because I didn't see it. All I heard about was that there has been an acknowledgement that the pop-open of the main UI is a bug (after it having initially been reported as a feature).
We also heard from someone at Avast that it was supposed to have been fixed by last week. In case you haven't figured it out, that time came and went.
Might it be just barely possible that the Avast engineering folks haven't correlated these two things yet, and are having more trouble than originally thought getting it all fixed? Perhaps it might be helpful to those who are working on the problem for users to put up more specific information on what's going wrong.
It seems to me that some of you here seem to want to comment subjectively on other people's posts than on the real issues.
-Noel