Pleaase note that Avast have responded to your original post here:
https://forum.avast.com/index.php?topic=229840.msg1522084#msg1522084
Have there been emergency updates to resolve such problems as the memory integrity issue? I don’t care to waste my time trying Avast 19.8.2393 unless I read assurances that that has been done.
I cannot believe that Avast 19.8.2393 has not been properly tested if the version has been botched by screwing up over a hardware security feature.
Avast 19.7.2388 works very well and smoothly.
Yes, it has been fixed in build# 19.8.4793.535 a while ago.
Thanks for the green light Asyn.
You’re welcome.
Are you sure about that build number ?
The reason I ask is I have had Avast Free 19.8.2393 (build 19.8.4793.541) for a while, certainly since I last updated my profile.
I haven’t heard of avast build numbers getting lower, it should be higher I would have thought, uness there has been some sort of reversion,.
Yep, I mentioned the build with the fix. It should also work in later builds.
Thanks. Version 19.8.2393 seems to have had the problems sorted. The core isolation feature now continues to function.
I re-installed this version today as was having crazy CPU-usage issues yesterday - re-install seemed to work but now back to same issue, constant 85+% CPU usage, I can just about write this post on my PC as the input lag is so bad now. Has this been an issue for others? It is not doing a scan as Disk I/O is minimal as is RAM usage.
I’m really struggling to do anything on my PC now, reboots and disabling core shields doesn’t make a difference. It’s the AvastSvc.exe for reference.
There are still multiple AvastUI.exe processes. Is this by design?
That has been mentioned before and for the most case you will see two entries. There could be more depending on what you are doing more UI windows open, etc.
I have attempted a re-install over my previous Avast Free, but the problem persists that even with settings turned off, Secure Browser keeps loading on start-up. All the time, every time, I boot up.
When the Avast Free UI is opened, a second and then a third incarnation of AvastUI.exe starts. Before first running the UI after system startup, only a single incarnation of AvastUI.exe is running. After running the UI, two incarnations of AvastUI.exe remain.
See Reply #170 from Dave.
I would say that Avast Free 19.8.2393 requires around an additional 100MB of memory compared with version 19.7.2388 on Windows 10 Pro 64bit.
This is a stupid ill-informed comment. Please take no notice.
If 100 MB is a problem, then you probably need to see what’s going on with your system.
I would say that is very hard to quantify as it also depends on what other programs you are running and the avast components you have installed. Firefox is by far the highest consumer of RAM.
Today, in the greater scheme of things 100MB isn’t that great, my win10 laptop has 8GB of DDR4 RAM (and this figure isn’t unusual), after all RAM is there to be used to aid performance.
I have thought better of my hasty comment David. You are right.
Avast Premium Security ver 19.8.2393
Windows 10 Pro v1903 build 18362.418
I run charting software (sierrachart - https://www.sierrachart.com) that uses multiple windows (both independant floating windows and MDI child windows within the main application).
When moving focus from one window to another, Avast Premium Security (or sometimes Avast Behaviour Shield) is seen in the task manager to spike in CPU usage, whilst also causing my application to become unresponsive for a short period of time. Avast Premium Security is also seen to spike when first opening the program.
I have added the program, it’s folder and associated data files to the exceptions list, but this has no effect at all.
I have also tried disabling the shields for 10 minutes, but this has no effect either - in fact Avast CPU spikes are more apparent even though it is apparently disabled.
To say that the current behaviour and associated performance impact is undesirable would be an understatement, how do I fix this?
edit: I should add that I have already ‘repaired’ the application and also tried to run in passive mode - neither of these options were successful.