Hi Derek.
Thank you for reporting this here.
We're glad to hear that the issue has been rectified now.
AVG services start immediately after your windows boots up but they are not hooked to the boot sector.
We'd have to do the root cause analysis to see what exactly caused this. Since everything is working fine now, please contact us back if you experience this issue again which we hope not.
In the first half of May, I updated to the latest release of AVG free, dated 4 May. I followed instructions, allowed windows to do a restart, and all seemed well. ver 20.3.3120
Thereafter, windows became more and more sluggish, and continued this way despite multiple reboots. This culminated in a machine where AVGsvc ran between 90-100% CPU load, and this only let off (down to maybe 25%) when I closed my browser. But basically nothing worked properly.
I read the forums. I confirmed there was only one copy of AVGsvc running. Then I read advice about 'fast reboot' and AVG problems surviving that.
I did a complete power off / power on recycle, and AVG has run properly over the last day or more.
CPU load is minimal, typicall under 1%. Memory is drastically different. Before the power vyvle, AVGsvc had claimed about 5 GB 'working set' memory. Now it's about 200 MB, and stable.
So the advice about a power cycle was good. Thanks to the couple of people who posted about that (years ago)
My question is - why would an AVG upgrade fail to work properly after a soft reboot? Is AVG writing startup code to the boot sector to hook its services prior to windows loading? Just curious ...
Hi Derek.
Thank you for reporting this here.
We're glad to hear that the issue has been rectified now.
AVG services start immediately after your windows boots up but they are not hooked to the boot sector.
We'd have to do the root cause analysis to see what exactly caused this. Since everything is working fine now, please contact us back if you experience this issue again which we hope not.