« Reply #251 on: August 12, 2020, 10:11:52 PM »
Well after suffering avastsvc.exe (was avastui.exe before) hogging 50% CPU, I got fed up and removed 18.8.2356 from my WinXP rig.
I then did a clean install of 18.5.2342 (build 18.5.3931.0). Annoyingly that took two attempts.
First time, even when I set Update Program = Manual, it somehow managed to update itself back to 18.8 
Second time it correctly asked if I wanted a Security Update, which I correctly rejected to retain 18.5.
Lets see if this version proves to be a bit kinder to my CPU.
Hi!
That was my experience, too. But I had to go back to 10.4.2233 as you can see in my sig.
BTW: Not using Windows services could make it difficult to keep your version safe.

=Snake=

Logged
Main: AMD LE1620,W7ult SP1|MS-7091,P4,XP pro SP3| AMD-Athlon 1800+ (XP pro SP3,FFesr 45.9,TB 45.8,CC 5.11)|
Laptops: Acer Aspire V5-591G,W10 Home[x64] v1909(Build 18363.959)|HPI_2020M,W8.1 pro[x64]|Amilo Xi2428,W8.1 pro|MD95400,W7ult SP1|MD97400,XP pro SP3|
FF ESR 78.8.0[NS,AOS,ABP],TB 78.8.0,MCS,CC 5.77, Defraggler 2.19.982,MBAM,MBAE,FW (XP+W7): CIS 3.14[FW,D+],AV: Avast Free [XP+W7:10.4.2233] 20.8.2429 |