Hi, after I opened the computer and logged in today Avast popped up that it detected a rootkit, but when I tried “Fix/repair/move to chest” it didn’t work and said that the request is not supported.
I subsequently scanned the file on its own with Avast and it came up clean, it was only when I conducted a general scan that it would detect the file as a virus. And again, originally Avast just popped up on its own that it found a rootkit without me doing any scan.
This behavior from Avast is quite strange, since Avast detects the file as malicious in one instance but not in another, and it doesn’t know how to deal with it.
Also keep in mind that Avast never found this file to be malicious before in any of my previous scans.
The executable file in question isn’t used, and its service wasn’t running at the time that Avast detected it.
Attached it a screenshot of Avast’s detection of the file, and it’s inability to deal with it.
Thank you in advance for whomever could help me with this!
Know you knew, but that kind of avast detection is a preliminary one, as the executable is established as to be above board and to be trusted, it can be either allowed or excluded to run.
Also should be interesting to know what triggered that heuristic evo detection. What is your position on that?
Just as I thought from the outset, a minor issue. Like Eddy said not being used for a long time, so a “new” old file detection. And as Pondus remarks this is a kind of “unfamiliarity” detection on avast’s part. So in a sense we all (Eddy, Pondus and little old me) agree here and we have consensus.
Just wondering, why does it keep on asking me for my language preference every step of the way. I had to clicked English at least half a dozen times to get the whole thing done. Strange.
I’m not sure, since I need to do a system scan to see.
If I just scan the file it won’t detect anything, just like I wrote in my original post right after the Avast pop up occurred.