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… 
It’s always a good idea:
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.
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 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.