Avast keeps waking laptop from sleep after a scheduled scan (Win10).

Avast Free Antivirus / Premium Security
21

Some basic hardware and OS info might be useful.

Computer
Model : OEM
Chassis : Desktop
Mainboard : ASUS CROSSHAIR V FORMULA-Z
BIOS : AMI (OEM) 2201 03/23/2015
Total Memory : 30.28GB DIMM DDR3

Processors
Processor : AMD FX(tm)-8350 Eight-Core Processor
Socket/Slot : AM2r2/AM3

Chipset
Memory Controller : AMD F15 (Orochi) CPU HT Hub 2x 1.1GHz (2.2GHz), 2x 16GB DIMM DDR3 2GHz 128-bit

Memory Module(s)
Memory Module : G.Skill F3-2400C10-8GTX 8GB DIMM DDR3 PC3-19200U DDR3-2400 X4

Video System
Monitor/Panel : ACR XG270HU X2

Video Adapter : 2x AMD Radeon (TM) R9 380 Series (28CU 1792SP SM5.1 1.09GHz/990MHz 10% OC, 16kB L2, 8GB DDR3 6.4GHz/5.7GHz 12% OC 256-bit, PCIe 3.00 x16)

Storage Devices
AMD 2+0 Stripe/RAID0 (118GB, RAID, SCSI-4) : 110GB (C:)
AMD 2+0 Stripe/RAID0 (478GB, RAID, SCSI-4) : 445GB (E:) (F:)
Disk (17.2GB) : 16GB (D:)
ASUS    BW-12B1ST   a (SATA150, BD-RE, DVD+-RW, CD-RW) : N/A (G:)

Network Services
Network Adapter : Intel(R) 82583V Gigabit Network Connection (Ethernet, 1Gbps)

Operating System
Windows System : Microsoft Windows 10 Professional 10.00.10586
Platform Compliance : x64
22

Just something to check out:
http://www.tomshardware.com/forum/id-2631828/computer-waking-sleep.html

23

As is the case with ividrine, the event logs are pretty clear, “Wake Source: Timer - AvastSvc.exe”. That and it only happens after I have run a scheduled Avast full scan for which the computer has to wake. At all other times my computer goes to sleep and wakes up appropriately without any issues.

24

While this might not work for everyone, I’ve “solved” this issue simply by turning off the setting to wake my PC. This works for me because, coincidentally, my PC has another wake timer that goes off around the same time to back up my PC (and this wake timer works just fine! unlike Avast).

25

Ya, I could use a script to wake the computer then schedule the scan to run at the same time. Shouldn’t have to resort to that though.

26

Has Avast given up on this problem and the associated problem in this post https://forum.avast.com/index.php?topic=177267.msg1256847#msg1256847 (Avast waking up PC every 4 minutes from sleep. Wake Source Timer AvastSvc.exe)?

There have been umpteen updates to Avast since these problems were first reported back in September last year (8 full months ago), and as of yet there hasn’t even been an hint of the problems being resolved.

27

See this topic - https://forum.avast.com/index.php?topic=186192.0 - this about the current beta version:

+ Removed NG (VHardware virtualization) - moved the technology to cloud, in next betas we will introduce new flow for handling unknown files

I believe it was the NG function or rather some of the elements used by it.

By moving this to the cloud should resolve it, since it won’t be using these local elements.

28

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?)

29

The link in my last post was to the beta, where this should have changed. Unfortunately that beta testing session is still ongoing.

30

I’ve just updated Avast to there latest proper release version 12.1.2272 (build 12.1.3076.0). The problem seems to have stopped!!! Yipee…
I’ve only tested this once, so further testing is required, but this looks very promising.

31

Sounds good, thanks for the feedback.

32

Well it looks like I spoke too soon. The bug is still there…

I should point out the following though.

When I updated Avast to the latest version on 22 June, (Using Update Program from within Avast), apart from the reboot required to complete the installation I didn’t reboot my Laptop.
The imminent 02:15 Wednesday Scheduled Scan didn’t have the Wakeup problem after the scan.
The next 02:15 Sunday Scheduled Scan didn’t have the Wakeup problem after the scan. (I still hadn’t rebooted at this stage).
I updated other software that required a reboot.
After the next (today) 02:15 Wednesday Scheduled Scan, the original reported Wakeup problem is now happening again.