Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: REDACTED on October 05, 2015, 05:18:38 PM
-
I noticed recently that my computer keeps waking up all the time from sleep. From my investigation it looks like the Avast Service is causing it to wake up for some reason. When I look in the Event Viewer it shows the process doing the waking is AvastSvc.exe:
"The system has returned from a low power state.
Wake Source: Timer - AvastSvc.exe
This entry is showing up in the event viewer roughly every 4 minutes. The computer goes to sleep about 3 minutes later and then avast wakes it up a minute after that.
-
As a guess, I'd say streaming updates.
-
I already disabled that. My setting is "automatic updates", but with "enable streaming updates" unchecked.
-
- Which Avast..? (Free/Pro/IS/Premier)
- Which version..?
- OS..? (32/64 Bit..? - which SP..?)
- Other security related software installed..?
- Which AV(s) did you use before Avast..?
-
10.4.2233 - free version.
Windows 10 - 64-bit
Only other security software I installed is Malaware Bytes which I run manually not in the background.
I have always used Avast on this PC.
-
Windows 10 - 64-bit
Which build..?
-
Home edition. Build 10240
-
Repair Avast:
1. Control Panel -> Add/Remove programs -> Avast
2. Click on 'Repair'.
3. Follow instructions.
4. Reboot.
-
I repaired Avast and then rebooted. I then put my computer to sleep and went away for a bit. My PC was awake. It was the same problem.
In the Event Viewer->Windows Logs->System
There was repeated:
1) Kernel Power - the system is entering sleep.
2) About 1 minute later a Power-TRoubleshooter event saying Wake Soure: Timer - AvastSvc.exe
-
I repaired Avast and then rebooted. I then put my computer to sleep and went away for a bit. My PC was awake. It was the same problem.
In the Event Viewer->Windows Logs->System
There was repeated:
1) Kernel Power - the system is entering sleep.
2) About 1 minute later a Power-TRoubleshooter event saying Wake Soure: Timer - AvastSvc.exe
One more thing to try:
(http://www.screencast-o-matic.com/screenshots/u/Lh/1444077701292-79216.png)
Since my computer is set to never sleep, I haven't tested this.
-
I'll give that a try later today or tomorrow morning. This is just status reporting right, and doesn't affect getting actual updates to the virus definitions? Those seem to be under Settings->Update which is set to update every 240 minutes.
-
I'll give that a try later today or tomorrow morning. This is just status reporting right, and doesn't affect getting actual updates to the virus definitions? Those seem to be under Settings->Update which is set to update every 240 minutes.
By disabling Streaming updates, you are actually lessening your computers protection.
Streaming updates make sure that your system is constantly protected against the newest discovered infections, etc.
Virus definitions simply combine these steaming updates but, they only happen every 4 hrs.
I personally never let my computer sleep. I simply turn off my display after a set amount of time.
(http://www.screencast-o-matic.com/screenshots/u/Lh/1444083252398-53067.png)
-
Well, if Avast has to wake to do it's streaming, or wake to do an update that removes all the power savings from sleeping. Avast could trigger to update when the computer wakes from sleep, or start streaming when the computer wakes from sleep. Then if it goes to sleep disable the streaming until the computer wakes and then re-enable it.
-
Well, if Avast has to wake to do it's streaming, or wake to do an update that removes all the power savings from sleeping. Avast could trigger to update when the computer wakes from sleep, or start streaming when the computer wakes from sleep. Then if it goes to sleep disable the streaming until the computer wakes and then re-enable it.
I don't believe that it does otherwise I'm certain we would get many more posts about this.
This system is on all day, but I have fairly tight power settings to go to standby monitor 5mins; HDD 15mins; system standby 20mins. When I bring it out of standby I can check the C:\Program Files\AVAST Software\Avast\defs folder and look for the 99999901_stream folder and the pkg999999999999.bin files received usually coincide from closely after coming out of standby.
My win7 netbook spends most of its time in standby and I never switch it off - I have just brought it out of standby/sleep and I see the 15100501_stream folder just created and all of the pkg9999999.bin files created within the last minute or two.
So it isn't coming out of standby/sleep either. I'm not sure what is going on with your system.
-
Well, if Avast has to wake to do it's streaming, or wake to do an update that removes all the power savings from sleeping. Avast could trigger to update when the computer wakes from sleep, or start streaming when the computer wakes from sleep. Then if it goes to sleep disable the streaming until the computer wakes and then re-enable it.
Submit a support ticket via here https://support.avast.com/Tickets/Submit
-
Glad to hear this is not the basic case, and I agree there would be more complaints. My concern was the last post suggested I leave my PC on all the time when there are events in Windows 10 that deal with going in and out of sleep.
-
Glad to hear this is not the basic case, and I agree there would be more complaints. My concern was the last post suggested I leave my PC on all the time when there are events in Windows 10 that deal with going in and out of sleep.
Not really suggesting that you leave it in sleep all of the time, just that I do and don't see this constant wake up for streaming updates.
Though it is certainly strange, but I don't use win10, so I can't check it.
-
Not you but bob3160, said he leaves his computer on all the time so that he gets the latest streaming. While this would work, it does take some electricity to leave a computer running all the time. I'd like the benefit of the sleep function, since I probably only use the computer 3-4 hours a day, rather than having to do a shut down every time I want to turn it off.
-
That's it, both my systems spend a lot of time in sleep/standby I only shut down my desktop at night and neither experience this when they are on but in sleep/standby. Weird.
-
Not you but bob3160, said he leaves his computer on all the time so that he gets the latest streaming. While this would work, it does take some electricity to leave a computer running all the time. I'd like the benefit of the sleep function, since I probably only use the computer 3-4 hours a day, rather than having to do a shut down every time I want to turn it off.
Since the screen is turned off if the computer isn't used for 20 min. I highly doubt that the difference in electicity usage will be anything to brag about.
It's your computer, so you need to set it up your way. That's what makes us individuals. :)
-
Hi Bob,
Thanks for your help. I submitted Ticket ID #XDR-320-65823. From what I have read the difference is about 2 Watts for sleep mode, and 65+ when awake. While the difference of one light bulb a day isn't a whole lot, there is some cost to it, and if you add that up across all computers that would sleep, especially those who want to maximize their laptop unplugged time that would make a difference.
-D-
-
The op is not the only one experiencing this. I noticed this last night when I put the computer to sleep. I typically put it to sleep and have utilities run at scheduled times on Saturday and Sunday nights. The computer would go to sleep, and then seconds later wake up again. It did that all night, and all day today when I tried to put it to sleep while I was doing other things.
The problem is the avast service:
The system has returned from a low power state.
Sleep Time: 2015-11-01T18:42:41.611788900Z
Wake Time: 2015-11-01T18:44:41.152527300Z
Wake Source: Timer - AvastSvc.exe
My Windows System logs are filled with these notifications.
Not using sleep mode is not acceptable. Leaving your computer full on is a waste of electricity, and beyond the expense it's something no one should be intentionally doing these days. I too tried disabling streaming updates. That made no difference, and disabling automatic updates is also not an acceptable solution.
-
I thinking this has something to do with the time change. It started happening the first time I tried to put it to sleep after the time change. And maybe with the op it had something to do with his computer's time being off.
-
After another day and a reboot the problem fixed itself. I'm pretty sure it was the time change that mucked things up, but probably all that needed to be done was a reboot. Not the first thing I think of these days... :)
-
After another day and a reboot the problem fixed itself. I'm pretty sure it was the time change that mucked things up, but probably all that needed to be done was a reboot. Not the first thing I think of these days... :)
It's always a good idea:
http://bob3160.blogspot.com/2014/11/when-all-else-fails-reboot.html (http://bob3160.blogspot.com/2014/11/when-all-else-fails-reboot.html)
-
After another day and a reboot the problem fixed itself. I'm pretty sure it was the time change that mucked things up, but probably all that needed to be done was a reboot. Not the first thing I think of these days... :)
It's always a good idea:
http://bob3160.blogspot.com/2014/11/when-all-else-fails-reboot.html (http://bob3160.blogspot.com/2014/11/when-all-else-fails-reboot.html)
Well, I've learned to fix a lot of problems with simple scripts that restart services etc. I still reboot every day, except on Saturday and Sunday nights when I leave the computer on to run maintenance apps...
-
It may be that the reboot fixed your specific situation, but back when I did a repair of avast, I reset my computer after the repair and the problem persisted. It went away on its own a day or so later.
In my case I'm wondering if it is due to my network card being slow to reconnect to the internet upon wake from sleep. It sometimes takes a while since I've upgraded to windows 10. If avast was polling as soon as it awoke and couldn't find the avast server, then set another timer to wake try again in a few minutes. Then repeat...
I haven't had it reoccur since. But it happened once before back in August.
-
Mayhap you have wake on lan checked
-
No, had nothing to do with that. I'm pretty sure it was a clock issue related to the time change. But it's fine now.
-
Looking for a common thread, DavidR and myself included are NOT using WIN10 and DO NOT have this problem.
Is there anyone who DO USE WIN10 that DO NOT have the problem?
If the conclusion is that ALL WITHOUT the problem are NOT USING WIN10 then the next question would be are ALL that DO HAVE the problem using WIN10? If the answer is "YES" then we have a common thread, WIN10.
-
Looking for a common thread, DavidR and myself included are NOT using WIN10 and DO NOT have this problem.
Is there anyone who DO USE WIN10 that DO NOT have the problem?
If the conclusion is that ALL WITHOUT the problem are NOT USING WIN10 then the next question would be are ALL that DO HAVE the problem using WIN10? If the answer is "YES" then we have a common thread, WIN10.
Don't have the problem using Windows 10.
Chalk it up to the time change. :)
-
Hi guys, thanks for bringing this issue to us. We've been analyzing the upcoming Avast 2016 version and we've found a place where this phenomenon can occur. It is related to the C++ Boost library, which exhibits this unwanted behaviour in certain waits/timers. Boost has already confirmed this to be a bug and fixes it in the next release.
We have updated the code not to use the said timer from boost, however it seems that this specific case was limited to the Avast 2016 Beta only.
Since y'all report this problem with 2015 R4, we'll continue searching.
-
I don't know if this helps, but a couple of months ago I posted a problem with Avast keep waking my PC up every minute after a scheduled scan. https://forum.avast.com/index.php?topic=176091.msg1249626#msg1249626 (https://forum.avast.com/index.php?topic=176091.msg1249626#msg1249626) Again a wake timer on a Win10 PC problem. I'm sure these problems are related...
-
I have the same problem on two Win 10 machines running Avast 2016 - 11.1.2241 - with the PC's waking up every 4 minutes after a scan. Shame as it's something stopping me recommending it to my clients.
Hope it's fixed in a new release
-
Hi, same problem here: Windows 10 Pro x64 Build 10586.11 + Avast Free 11.1.2241.
The PC keeps waking up from standby after 3-4 minutes.
Event log is full of Power-Troubleshooter entries:
The system has returned from a low power state.
Sleep Time: 2015-11-22T19:28:45.179446400Z
Wake Time: 2015-11-22T19:29:51.868314700Z
Wake Source: Timer - AvastVBoxSVC.exe
Not being able to put the pc to sleep is not acceptable, if this doesn't get fixed, the only option is uninstalling avast.
-
In my experience shutting down the computer fully and starting it up again solves this problem.
-
Avast Pro Antivirus 11.1.2441
I also have this problem in that Avast only allows my Win 10 PC to sleep for 30 to 40 seconds then wakes it again repetitively after it does a scheduled scan.
I made the mistake of upgrading from Free to Pro to try and fix it. Bad mistake!
Yes, restarting the PC does turn off this irritating fault - until the next scan!
(The verification image on this forum is ridiculous!)
-
Hello guys,
thanks for reporting this. We have found another case of a similar waitable timer - this time inside the Virtual Box sources we use for NG. This is going to be fixed in the next refresh. Please watch for the Beta channel.
Thanks a lot,
Lukas.
-
I have the same issue with latest beta (11.1.2244). It happened 6 times already since yesterday (i.e. after updating to 11.1.2244).
Is the fix already included in latest beta, or it is still under development? :-\
Event viewer says "Wake Source: Timer - generic"
-
This issue should be solved in the latest beta - both occurences of the timer, in boost and virtual box have been removed.
-
This issue should be solved in the latest beta - both occurences of the timer, in boost and virtual box have been removed.
Thanks, then I should try clean reinstall. Today I got the same issue again :-X
-
This issue should be solved in the latest beta - both occurences of the timer, in boost and virtual box have been removed.
Thanks, then I should try clean reinstall. Today I got the same issue again :-X
Using which version of Avast ???
-
As I stated above, version is Avast 2016.11.1.2244 (Premier). Win7 SP1 64bit.
-
I have the same problem. In my case it's AvastVBoxSvc on Windows 10.
-
Reinstalled latest beta. Still no good. Computer always wake up within a few minutes.
Without avast, this issue does not happen.
I can't use sleep anymore :(
-
Yes, I am on the latest update and this still happens. I do SEVERAL system restarts and it goes away but returns as soon as I do another scan!
It's about time they fixed it!
-
It could also be related to a Windows 10 bug;
http://www.addictivetips.com/windows-tips/how-to-stop-windows-10-randomly-waking-from-sleep/ (http://www.addictivetips.com/windows-tips/how-to-stop-windows-10-randomly-waking-from-sleep/)
-
That's not a bug, wake timers are SUPPOSED to wake your system up. They're just not supposed to wake up the PC every few minutes. My other wake timers all work fine, it's just Avast that's messed up.
-
I've discovered something interesting. I don't even have to schedule a scan for this to happen. I can schedule a scan, disable the option to wake the computer, use a script to wake the computer, and the sleep/wake cycle will happen every four minutes after the scan, or I can completely disable the scan schedule, and just run a scan and allow the computer to go to sleep normally, and it will fall into the four minute sleep/wake cycle. And it's always the Avast service initiating the wake events.
-
Yea, I'm still having this stupid problem too.
-
It's bad enough that I'm considering dropping Avast.
-
Totally agree. This shouldn't be a problem. Avast doesn't pay my electric bill.
-
Not to mention that a night of cycling through sleep and wake every four minutes is hard on your hardware.
-
Avast doesn't pay my electric bill.
1] Computers do not use as much electricity as people often think
2] If you are worried about the electricity bill, you should not use sleep mode/hibernation at all but just shutdown the system completely.
Not to mention that a night of cycling through sleep and wake every four minutes is hard on your hardware.
No it is not. As long as you don't completely shutdown the system, the hardware is powered.
Besides that, the hardware has no problem with it at all.
Did anyone of you disabled the wake-up timers power management to see if it makes a difference ?
-
Avast doesn't pay my electric bill.
1] Computers do not use as much electricity as people often think
Maybe not *your* computer. Mine uses over 100 watts at idle (used to be 150, but I recently upgraded the CPU), plus having it on also keeps my home server awake (adding another 30 watts to power usage).
2] If you are worried about the electricity bill, you should not use sleep mode/hibernation at all but just shutdown the system completely.
Really? Because that extra CPU usage during bootup is totally going to offset the 4 watts of power my PC uses when sleeping. Not to mention Hibernate DOES NOT USE power.
Not to mention that a night of cycling through sleep and wake every four minutes is hard on your hardware.
No it is not. As long as you don't completely shutdown the system, the hardware is powered.
Besides that, the hardware has no problem with it at all.
What are you talking about? Power cycling through sleep/wake is horrible for hardware. The drives spin up and fans turn on/off. All that wears down life.
Did anyone of you disabled the wake-up timers power management to see if it makes a difference ?
Umm, that would turn off wake timers. That's not what we want. Other wake timers work fine. It's just Avast's. Or are you asking to see if it's really a wake timer that's causing a problem or something else in Avast that's the issue?
Also, please note we've submitted several tickets for this (read through this thread and this other thread (https://forum.avast.com/index.php?topic=176091.15) with no resolution after months).
-
C:\WINDOWS\system32>powercfg /lastwake
Wake History Count - 1
Wake History [0]
Wake Source Count - 1
Wake Source [0]
Type: Wake Timer
Owner: [SERVICE] \Device\HarddiskVolume3\Program Files\AVAST Software\Avast\ng\vbox\AvastVBoxSVC.exe (AvastVBoxSvc)
Avast Free Antivirus 11.1.2253 (def: 160325-0)
(Upgraded) Windows 10 x64 Pro
After successful sleep, my PC wakes up after about 30 seconds :/
Peace!
Devnullius
-
Repair setup gave error about a Dutch language file, but after the reboot all was well and indeed, I'm sleeping again :)
Devvie
-
Awesome tip man. It worked like a charm. My pc is sleeping again. Thanks Devvie
-
Repair installation didn't work for me, all it did is force me to reconfigure all my scans.
-
Still happening with my Win10 system. Like the others have said, If I reboot then sleep mode works normally.... until the next scan. Avast did a scan last night and, TA DA!, sleep mode doesn't work today.
Hello guys,
thanks for reporting this. We have found another case of a similar waitable timer - this time inside the Virtual Box sources we use for NG. This is going to be fixed in the next refresh. Please watch for the Beta channel.
Thanks a lot,
Lukas.
-
Still happening with my Win10 system. Like the others have said, If I reboot then sleep mode works normally.... until the next scan. Avast did a scan last night and, TA DA!, sleep mode doesn't work today.
Hello guys,
thanks for reporting this. We have found another case of a similar waitable timer - this time inside the Virtual Box sources we use for NG. This is going to be fixed in the next refresh. Please watch for the Beta channel.
Thanks a lot,
Lukas.
There have been 5 updates to Avast since Lukas quote, so the so called fix either hasn't been implemented or it hasn't worked... I first reported this problem on this Post https://forum.avast.com/index.php?topic=176091.msg1249626#msg1249626 on 06 September 2015 (8 months ago to the day!!!). I've almost given up with Avast... I'm assuming that they can't find/repeat the bug, or they think it's a Win10 bug and aren't doing anything about it, rather than finding a workround.
-
@ Chris-G
As per Lukas's quoted post, they found the issue in the "Virtual Box sources we use for NG." The current beta session 11.2.2263 sees the NG module removed to be handled in the cloud. See extract below.
See https://forum.avast.com/index.php?topic=186192.0
+ Removed NG (VHardware virtualization) - moved the technology to cloud, in next betas we will introduce new flow for handling unknown files
-
Let's hope this finally fixes this.
-
Let's hope this finally fixes this.
Unless your are running the current beta build, it won't as the fix is in the beta build 11.2.2263.
-
Let's hope this finally fixes this.
Unless your are running the current beta build, it won't as the fix is in the beta build 11.2.2263.
Nice to see that it should be fixed soon, though I think I'll wait for the New Version release rather than trying the beta.
-
Let's hope this finally fixes this.
Unless your are running the current beta build, it won't as the fix is in the beta build 11.2.2263.
Nice to see that it should be fixed soon, though I think I'll wait for the New Version release rather than trying the beta.
Given the length of this topic, I'm sure there are many other who will be happy too.
-
After many, many months Avast have not fixed this.
They have, in the meantime, added lots of security bells and whistles.
If they don't have the technical expertise to fix this fault, should we be trusting their security?
(For me, my Acronis program wakes my computer on schedule, backs it up, then allows it to go back to sleep. Why can't Avast do this? Could they try asking Acronis for some tips?)
-
Apparently the fix is in beta, but it's been in that beta for at least a month now.
-
Thanks for that info :)
-
So still not fixed, because my PC still wakes up minutes after going to sleep and the lastwake output is still telling me it is due to avastsvc.exe?
I guess that as it's been an issue for a very long time (at least since 2015), with several program updates released since it was first reported, it won't (or can't?) be fixed by Avast? :(
-
So still not fixed, because my PC still wakes up minutes after going to sleep and the lastwake output is still telling me it is due to avastsvc.exe?
I guess that as it's been an issue for a very long time (at least since 2015), with several program updates released since it was first reported, it won't (or can't?) be fixed by Avast? :(
Possible avastsvc.exe is scanning an wireless keyboard or mouse? Changing to a PS2 version may fix your issue.
-
Ya, I can confirm this. After the latest update as of June 21, this still isn't fixed. I still can't put my computer to sleep and have it run a full scan at a scheduled time, or even let it run a scan then put itself to sleep.
-
mchain - thanks for that feedback, but surely it is something which should be fixed, rather than advise users to go back to what is now considered a bit old fashioned - ie wires? The (very long) thread keeps on referencing a fix being 'soon' so is it actually being addressed? Is anyone from Avast able to say it is on the bug list, about to be fixed or possibly 'sorry, it's just something we cannot fix', so at least we would then have to option of buying an old mouse and keyboard or adopting an alternative product?
-
@ barnek022,
Doesn't appear to be a bug in avast: http://thehackernews.com/2016/02/mousejack-hack-computer.html (http://thehackernews.com/2016/02/mousejack-hack-computer.html)
Would rather appear to be avast reacting to traffic via avastsvc.exe process running via usb mouse or keyboard transmissions.
Get the latest secure updates from whatever manufacturer you're using and install.
-
This is happening on my PC as well. AvastSVC.exe wakes it up every couple minutes. is there a fix yet, or is it time to look for an alternative?
-
I still have the same problem since I first reported this over 12 months ago. The problem for me started when I installed Win10 on launch day, and have hoped that on every update of Avast or Windows since that the problem would go away.... It hasn't.
The suggestion a couple of posts up that the problem is caused by a wireless mouse/keyboard is wrong in my case. I'm using a laptop, and do occasionally use a Logitech wireless M570 trackball, though the receiver is never plugged in when the problem occurs after a scheduled scan.
I find it quite amazing that Avast has come nowhere near finding a solution to this... It doesn't matter where the bug is, it's Avast that needs to sort the problem out. If it's a Microsoft bug then Avast needs to write a workround... Something that programmers have always had to do.
Of the 4 PC's I have, I've migrated 3 of them to Avira. I must admit that Avira's menus leaves lot to be desired as well as only being able to create one customised scan, but it does work. The only reason I have stuck with Avast on my main 4th PC is that this PC is used for mail and Avast has a mail shield. I don't think it will be long though before I migrate this one either. A pity since I've used Avast since their main interface looked like a car cassette player...
-
If it's a Microsoft bug then Avast needs to write a workround
No, then MS needs to fix it.
Already checked the bios for the power saving and wake-up settings ?
-
If it's a Microsoft bug then Avast needs to write a workround
No, then MS needs to fix it.
Already checked the bios for the power saving and wake-up settings ?
It's a good job that Macrium Reflect don't have your attitude... They'd be out of business by now if they did. They had reported a bug to MS prior to the release of Win10 Anniversary, that there were bugs in the Task Scheduler 1.0 API. MS didn't bother fixing the bugs. Macrium Reflect had to have a major re-write to get the backup scheduling to work again, i.e. a workround.
If you were a programmer working for me with an attitude like that, you'd be sacked on the spot, as the objective is to solve the problem, not pass the blame (even though it might be MS's fault) and solve nothing.
-
With your attitude I don't even want to work for you.
MS has a bug in their software, that means they need to fix it or are you gonna pay all the developers for the work they have to do ?
-
A good discussion , i joined see.
-
A good discussion , i joined see.
Not really. I've said my bit, and I don't want to get involved in a slanging match. What I will say though is that this problem (looking at this thread) affects both the free and paid for versions of Avast, therefore paid for customers especially, expect there to be a fix. The Macrium example I gave also affected both free and paid for customers by the way, not just paid for. (For Eddy's benefit, the paid for customers pay for it as this sort of bug fixing should have already been factored into the price).
Another important point, is that you could be waiting a long time (Possibly Never) for MS to fix the bug (Assuming this is an MS bug). MS tend to concentrate on fixing bugs that affect there own software first, also if the bug is, for example, in code that is to maintain backward compatibility for programs that were written to run on XP, or OS's that MS are trying to discourage, then they will tend to be reluctant to fix it. The Macrium problem was exactly that, as Macrium was specifically using the Task Scheduler 1.0 API so that their software was compatible with OS's XP through to Win10. Has this wakeup problem come about due to Avast, also wanting to be compatible with XP through to Win10? Who knows...
-
So there have been a few program updates since I last tried to schedule a scan and have it wake up my pc to run the scan. I thought I'd try it again.
The scan did run, but when I woke up in the morning my computer was locked up, and after I rebooted and started playing a game, the video subsystem was unstable until I disabled the scheduled scan along with the option to have Avast wake the computer from sleep.
So something is still f*xxored with Avast, scheduled scans and waking from sleep. The fact that it screwed over the video subsystem makes me think that Avast isn't attempting to wake the computer using the standard Winblows functionality. Perhaps it is using a kernel level function, but whatever it is, it isn't working.
It would be nice to see this fixed. The only reason I'm still using Avast is the Webrep browser plugin for Firefox. If it wasn't for that, I'd be using Windows Defender.
In spite of the fact that I appreciate the Webrep plugin, overall in recent years Avast has become a bloated mess, which, to add insult to injury, is now yet another data collection and advertising platform.
-
I also have this issue, have filed a ticket.