Used roguekiller earlier just to check my system and this happened…
uhh? can anyone explain this?
Used roguekiller earlier just to check my system and this happened…
uhh? can anyone explain this?
Yes Roguekiller tried to stop Avast
by stop avast what do you mean?
why did it try to stop it? should I be worried? :o
Roguekiller stops all processes when it scans as a safety measure for itself. However, Avast has a protection against being stopped
Nothing to worry about
A lot of malwares uses Process Hacker’s driver to disable avast protection, that’s why we block this driver.
Had a hunch that was the cause, Thanks guys!
So this means that Roguekiller can’t finish scanning, because AVAST shoots it. I think this is a problem for users running both of these products and never used to be a problem until recently, so one of these products changed.
Well, since Roguekiller is meant to resolve malware infections and is run only once, and can used to kill avast services, it would make sense to protect avast from being disabled via avast self-defense module. Roguekiller is not run at every system startup.
Avast self-defense is meant to protect avast from outside attacks.
If you don’t want avast self-defense to be running when you run Roguekiller just disable it temporarily for the duration of your Roguekiller malware cleansing session.
If you disable the SelftDefense Module, Roguekiller will KILL Avast. This isn’t anything new. I reported this some years ago before Roguekiller was being blocked.
It’s something the 2 companies need to work out.
It’s simple:
Roguekiller need to stop killing anti-virus processes and should have a whitelist.