I can't disable Rootkit detection

[Asyn]

Dev-Info: If you didn't get the UI update yet, there's a workaround. Open and edit avast5.ini

Code: [Select]

[AAVM]
ArPotEnabled=0

[Rundvleeskroket]

What does that do?

Still at .390 btw.

[Asyn]

What does that do?

It disables Rootkit detection.

[Rundvleeskroket]

OK.

Well, when I try to modify that file Windows tells me it is in use and I can't save. Even if I disable Self-Defense. Now, I could edit the file from a Live-CD or something but I shouldn't have to go through all that trouble just because an update won't show up on the 'stable' channel. If it was pushed to stable it should appear, right?

Edit: OK I did it the hard way. Rootkit-detection is now disabled. Also Exploit-detection. Now I can test. However I now have a notification about the disabled Rootkit-detection that I can't dismiss. Slightly annoying but OK.

Also: why is Avast still popping up with a warning about editing Avast-files when Self-Defense has been disabled?

[Asyn]

Also: why is Avast still popping up with a warning about editing Avast-files when Self-Defense has been disabled?

Post a screenshot.

[Rundvleeskroket]

I can't now. It was an alert about editing avast5.ini, by Avast, even though Self-Defense was disabled.

Edit: Avast has now luckily figured out to offer me to ignore the notification about the disabled Rootkit-Detection. It didn't before. So that blue dot is gone. That is something.

[Asyn]

Edit: Avast has now luckily figured out to offer me to ignore the notification about the disabled Rootkit-Detection. It didn't before. So that blue dot is gone. That is something.

Sounds good.

[Rundvleeskroket]

I'm not 100% sure what is going on.

I had disabled Self-Defense. Because i assumed I had to to edit Avast files. I hadn't re-enabled it, but also no notification about it being disabled was visible in the Avast status screen. So that is already weird. I tried to edit the file and it said it was in use and I couldn't save. I tried another method to edit the file and now I could save, but I got the alert popup about if I was sure? Now, still I hadn't re-enabled Self-Defense. But Avast must've re-enabled it itself because when I went to turn it back on I found it on already. So again: weird behavior. Especially because I just disabled Self-Defense again (to test) and now it stays off. So why didn't it earlier? I just don't know.

I hope the update will show up soon so I can use the UI for these changes.

[Asyn]

I hope the update will show up soon so I can use the UI for these changes.

If you're in a hurry, you could install the latest beta: https://forum.avast.com/index.php?board=15

[DavidR]

I can't now. It was an alert about editing avast5.ini, by Avast, even though Self-Defense was disabled.
<snip>

Not only do you have to disable the avast self-defence module, but you have to use notepad.exe the windows text editor (that is the only one allowed) to be able to edit the avast5.ini file.

I don't know if you were using notepad for the edit.

[Rundvleeskroket]

I was using a different editor the first time. What kind of weird restriction is that?

I hope the update will show up soon so I can use the UI for these changes.

If you're in a hurry, you could install the latest beta: https://forum.avast.com/index.php?board=15

Like I said before; i don't feel like beta-testing an AV. Now that I have disabled Rootkit-detection and Exploit-detection via the .ini I'll have to see if the sudden pauses are gone. They might well have nothing to do with Avast, but at least I can test it now to exclude them as possible problems

[DavidR]

I was using a different editor the first time. What kind of weird restriction is that?

It has been like that for as long as I can remember and I have been using Avast (and editing the avast5.ini file) for over 15 years.  Back then there were many settings that could be set in the avast5.ini file.

My guess would be:
A)   it is the default (many will either be using it or it will be on their OS) text editor.
B)   it is a bog standard text editor that doesn't have any formatting, etc. (like some text editors) that could potentially stop the avast5.ini file from working after modification.

[Rundvleeskroket]

Of course you shouldn't have to edit the ini-file if the UI actually works.

[DavidR]

Of course you shouldn't have to edit the ini-file if the UI actually works.

Well there are functions available in the avast5.ini file that aren't available in the UI even when it is working.

[Rundvleeskroket]

Such as?