![]() |
|
#1
|
|||
|
|||
|
Passive detection turned up fakealerter.m yesterday and supposedly cleaned it... I assumed the problem fixed but ran a full scan anyway, turned up a trojan and cleaned that too, I figured I was done...
Now today, upon turning on the machine the problem is back. Even in safemode, nod32 seems to be having some issues getting at whatever the real infection is here. I'm seeing (what seems to me to be) a ridiculous number of errors in the scan. These errors range from the non-problematic ('error opening' on pagefile.sys) to the potentially troubling (inability to scan registry files like ntuser.dat, again giving 'error opening') to a few things I honestly don't have the experience to hazard a guess on the implications of (quite a few 'Bad archive' errors). Now the safemode scan has just turned up 3 instances of fakealerter.qu, so I'm assuming there's a trojan (or maybe something with a rootkit?) hiding on my machine and bringing these things in. Aside from the unilateral solution of a reformat, can anyone suggest steps I should take to try to get to the root of the problem? |
|
#2
|
||||
|
||||
|
Hello Smcfadden,
Please contact our support engineers here: http://www.eset.com/support/contact.php We will take a look at this for you. Thank you, Richard |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|