This new update is causing my AvastSvc process to chug data within minutes of startup for about 10 minutes and recurs (which is a problem for an old computer like mine), rather than once per session if that (which is more reasonable). Even Repair doesn't work, while it did work last time AvastSvc went on the fritz for me.
(Also, Avast might want to update the Repair FAQ [https://support.avast.com/en-ca/article/Repair-Antivirus] to mention clicking the Uninstall button is how to reach Repair, rather than Change.)
OS: Windows 7 64-bit
RAM: 8 GB (AvastSvc chugs 13% data usage)
SUBSCRIPTION: Free
1:23 AM-ish EDIT: Son of a- AvastSvc is already using 13% CPU again, and it hasn't even been a full hour! Only a few minutes (2-3) this time, but still...
2:54 AM EDIT: Hasn't acted up again, but still something to look into.
10:33 PM October 10th EDIT: AvastSvc is still chugging on my data, multiple times in a single session. Once when starting my computer, then again an hour and a half later, and one other time all in one session. It acts up for 12 minutes at a time a little after initial start-up, then 2 minutes on subsequent times.
I initially installed the "Recommended installation", as well as when I changed Avast before trying Repair.
Disabling all shields while disconnected from the internet did not stop AvastSvc's activity, so the shields or online connections aren't the problem. It must be one of the other "Recommended" components that got borked in the update, causing AvastSvc to scan for 12 minutes for no reason.
I keep looking back at my harddrive space, and it seems to be very subtly shrinking over time. I was at 412 GB last night. I'm at 409 GB now. While I have saved files during today, I doubt they even reach 100 MB. Again, there is definitely something wrong with a component or two of the "Recommended" installation.
11:00 PM EDIT: I couldn't really wait any longer, since I didn't like the idea of dealing with this problem for an elongated period of time. On a hunch, I Changed the installation to a Custom one, omitting the following components: Software updater, Wi-fi Inspector, SafePrice, Passwords and Cleanup. And it seems to have worked for start-up- the early AvastSvc fits didn't happen. So one of those five components is the culprit.
I'll update again if something happens.