Full Virus Scan stuck 0%, "The Anti-rootkit monitor is disabled" won't go away

Avast Free Antivirus / Premium Security
1

Hi.

I’m using Windows 7 x64 with newest update of Avast (Free Antivirus).
Full Virus Scan stuck at 0% even after being left for hours.
One problem in notification tray won’t go away. “The Anti-rootkit monitor is disabled.” Went to Troubleshooting under Settings and “Enable anti-rootkit monitor” already checked. Clicking the enable button does nothing so the problem wouldn’t disappear from the tray.

Any help? Much obliged.

2

Repair Avast:

  1. Control Panel → Add/Remove programs → Avast
  2. Click on ‘Repair’.
  3. Follow instructions.
  4. Reboot.
3

Already done that before. Nothing changed.

4
  • Which version of Avast Free…?
  • Other security related software installed…?
  • Which AV(s) did you use before Avast…?
5
  • Which version of Avast Free…? Latest version, 17.5.2303 (build 17.5.3585.182)
  • Other security related software installed…? Malwarebytes Free and MSE
  • Which AV(s) did you use before Avast…? Have only used Avast and the above for a long time now but the problem only surfaced recently.
6

First, be sure to get rid of all remnants of MSE…!!
→ https://www.avast.com/faq.php?article=AVKB11#artTitle

Then;

  1. Download Avast Free Antivirus: https://files.avast.com/iavs9x/avast_free_antivirus_setup_offline.exe
  2. Follow instructions: https://www.avast.com/uninstall-utility (Run this tool for all prior installed Avast versions…!!)
  3. Reinstall Avast with the downloaded installer from point 1.
  4. Reboot.

PS: Regarding Avast & MBAM, see: https://forums.malwarebytes.com/topic/200324-exclusions-for-avast-users/

7

Is it not possible to keep MSE?
As I’ve previously mentioned they both worked smoothly alongside each other for quite a long time before the issues came about.

8

Well, things change…

9

Sorry if my response had cause any offense!
It’s just that I found a few posts on forums saying that the two were quite compatible with each other. Granted, they were old posts.
I simply presumed there were other issues causing this.
Regardless, thank you.

10
  1. Not at all, don’t worry. :slight_smile:
  2. You’re welcome.