Avast Free AV - Program displaying message Anti-Rootkit Module is not enabled

[REDACTED]

Recently updated the Free version of Avast AV to the latest and now the program keeps displaying the problem message that the Anti-Rootkit Module is not enabled even though I have the option checked.

I even repaired the program but the same message keeps appearing with a green ENABLE button. I press that button and nothing happens.

I am concerned that the new version may not actually be protecting me. See attached screenshot.

P.S. The Green Enable button is cutoff in the first screenshot but it is there to the right of the message

[Eddy]

Perform a clean installation of the latest version.

[REDACTED]

Performed a Clean Install, uninstalled completely, then reinstalled, problem solved.

However, be advised that the upgrade came from within the previous version upgrading itself.

I should not have to attempt to perform a repair function, which should have resolved my issue, and then have to post on this forum to get an answer when somehow the problem was self-induced.

Obviously, there is a problem with your upgrade process, and the program's repair function, which needs to be addressed.

Your support despite my critique is much appreciated. Thank you.

[DavidR]

Program Updates have for some time been set to Automatic Update. If you want more control over program updates - AvastUI > Settings > Update > Program Update - Settings set to Ask when an update is available or to Manual update.

As you can see from my image I still have the 17.4.2294 version awaiting my manual update.

[REDACTED]

You miss my point. The upgrade process corrupted the program itself. In other words, when the program automatically updated itself, it created a problem.

Secondly,  the internal repair option should have corrected the issue without me having to post, and wait for a reply on this forum.

I do not mind automatic updates, in fact prefer them so I do not forget.

[bob3160]

You miss my point. The upgrade process corrupted the program itself. In other words, when the program automatically updated itself, it created a problem.

Secondly,  the internal repair option should have corrected the issue without me having to post, and wait for a reply on this forum.

I do not mind automatic updates, in fact prefer them so I do not forget.

Running the repair function is a manual operation not an automatic procedure.

[DavidR]

You miss my point. The upgrade process corrupted the program itself. In other words, when the program automatically updated itself, it created a problem.

<snip, answered by bob3160>

I do not mind automatic updates, in fact prefer them so I do not forget.

If something like this happens on an automatic update, you may not even be aware that it has updated until you experience a problem.

Setting the Program Update to Ask as one of the options I suggested, would mean that you would be notified that one was available. That gives you time to make any backup options that you might have.

Before doing a program update I always backup my program settings and take a backup image of my C:\ drive. If there is a problem, corruption/conflict, then I can restore that update in under 20 minutes.

[Eddy]

Updates happen more often than people notice.
They are not seeing the micro fixes.

[DavidR]

Updates happen more often than people notice.
They are not seeing the micro fixes.

The micro updates/fixes aren't in the program updates though, but in the VPS update. The OPs issue is with a problem 'after a program update' not a VPS update.