Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Rundvleeskroket on July 23, 2019, 04:50:21 PM
-
Hi.
I want to disable the rootkit detection in the Core Shield. To test something. But it won't let me. When I uncheck the box Avast immediately returns me to the main status screen and the setting hasn't been changed.
I can uncheck the nested exploit detection box, but not the main "Enable Rootkit detection" box. It won't work.
The thing I'm trying to test is a weird behavior of my PC where when I start a program it randomly sometimes sits there for about 10 seconds doing nothing. Waiting. No notable CPU activity, no disk activity, no network activity. Seemingly. So I want to test if this is caused by some component of Avast Free.
But as it is I can't seem to even test this.
-
I want to disable the rootkit detection in the Core Shield. To test something. But it won't let me. When I uncheck the box Avast immediately returns me to the main status screen and the setting hasn't been changed.
I can uncheck the nested exploit detection box, but not the main "Enable Rootkit detection" box. It won't work.
Confirmed, same here.
-
Note, the devs are working on a fix...
-
Update, is has been fixed in UI V1.0.394 (released a few minutes ago).
-
Update, is has been fixed in UI V1.0.394 (released a few minutes ago).
How was this released, as a manual program update reports the program is up to date, but the UI is still 1.0.382. Are you talking about the current beta or the regular program version ?
-
Hi Dave, the UI has its own/separate update channel. It might take a while to propagate to all servers.
-
Hi. I just checked for updates manually. UI is version 1.0.390. Still has the bug. I'll check later today.
Thanks for the fast response.
-
You're welcome.
-
Hi Dave, the UI has its own/separate update channel. It might take a while to propagate to all servers.
Thanks, still no joy as yet though.
-
Still no new version available.
-
Still no new version available.
Snap still no change.
-
Still no new version available.
Snap still no change.
Hi guys, same here, I'll report it...
-
I'm still stuck on UI 1.0.387, even after manual update attempts that came to nothing.
Update: Just did a Restart (boot) and now have UI 1.0.390, but not 394 with the fix yet.
-
Same here. 390.
-
Hi guys, I got updated to UI V1.0.394 today.
-
I've manually checked several times during the day, including just now, and nothing. Still 1.0.390.
-
See if it helps to reboot twice...
-
Well I did an About Avast and nothing out of the ordinary, but on going into Settings > Update, it reported virus definitions out of date. I just wondered if this might be the delivery, but still on 1.0.382.
Going to reboot to see if that does anything.
EDIT: 1st reboot went to 1.0.390 about to reboot again.
EDIT2: Nada, still on the slightly newer UI version 1.0.390.
-
Hi. I just checked for updates manually. UI is version 1.0.390. Still has the bug. I'll check later today.
Thanks for the fast response.
Yup still .390 here as well
-
Still 390 after reboot.
-
Well, no idea then. According to the devs it has been released and I can confirm it.
-
Mine is ver. 19.6.2383 - build 19.6.4546.511
Just tried to update. Still the same version from a month ago. June 25th 2019.
Does the release cycle differ between premium and free?
-
Does the release cycle differ between premium and free?
Nope, I'm on beta channel.
-
I'm not. Regular channel (I assume). Free version. Maybe it is still in beta then.
-
According to the devs, they also pushed it to stable channel.
-
Hi. I just checked for updates manually. UI is version 1.0.390. Still has the bug. I'll check later today.
Thanks for the fast response.
Yup still .390 here as well
Yes, I initially checked my Regular channel version installation which is .390
I have subsequently checked my Beta Channel installation and it is .394
So there's the difference :)
Edit: I will be watching for the update on Regular installation
-
Yeah I'm not keen on beta-testing with an AV. I'll wait.
-
@Asyn. Ah you must have got priority treatment :)
Like groundhog day here. Update>Reboot and again 390.
Edit: Sorry guys, I had missed page 2 of the thread, but my comment above is still true status of latest version available here.
-
Still .390 ¯\_(ツ)_/¯
-
Still .390 ¯\_(ツ)_/¯
Same here. I've reported it.
-
Dev-Info: If you didn't get the UI update yet, there's a workaround. Open and edit avast5.ini
[AAVM]
ArPotEnabled=0
-
What does that do?
Still at .390 btw.
-
What does that do?
It disables Rootkit detection.
-
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?
-
Also: why is Avast still popping up with a warning about editing Avast-files when Self-Defense has been disabled?
Post a screenshot.
-
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.
-
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.
-
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.
-
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
-
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.
-
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 :)
-
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.
-
Of course you shouldn't have to edit the ini-file if the UI actually works.
-
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.
-
Such as?
-
Such as?
You can change the delay of update checks beyond what is available in the UI..
This however is neither here or there in relation to why we got here:
Of course you shouldn't have to edit the ini-file if the UI actually works.
-
As far as that goes: still no .394 available.
Sadly it doesn't seem that turning off the Rootkit/Exploit-detection fixes the weird pauses.
-
.394 finally showed up! :)
-
.394 finally showed up! :)
Patience is a virtue. ;)
-
.394 finally showed up! :)
Patience is a virtue. ;)
I'm very virtuous, but it doesn't seem to be helping very much :)
-
.394 finally showed up! :)
Patience is a virtue. ;)
Yup, finally ;)
-
I'm very virtuous, but it doesn't seem to be helping very much :)
Well, as I doubt that you're planning to disable Rootkit detection, it's probably not that urgent. ;)
-
I'm very virtuous, but it doesn't seem to be helping very much :)
Well, as I doubt that you're planning to disable Rootkit detection, it's probably not that urgent. ;)
For me it certainly isn't urgent, which help with the patience, but when it is meant to be released, there is very little middle ground (it is or it isn't).
-
I received 394 yesterday, but only after update and reboot.