Repaired but didn’t change anything
Hello,
I also still have an issue with the certificate in Foirefox and Chrome lastest versins and also on Avast secure browser (online a few hours works, if i start my pc again, doesn´t appear the certificate anymore) on Win10 Pro x64 1809. This certifcate interages as preveting MIM Attacks and now i don´t feel secure in browsers because of that. I already tried mutiple times repair Avast Premier and restart my desktop but nothing works, it seems doesn~t import correctly the security certificate to the browsers.
Can you help me please?
Regards,
What is aswEngSrv.exe and can I disable it? You know how I feel about antiviruses suddenly running new executables.
aswEngSrv.exe isn’t running on my system.
It wasn’t running on my system before this update and now after the update it is, how do I disable it?
You don’t want to disable it. That process is handling the actual virus scanning (right now for File Shield, later most likely for other components).
It’s being rolled out gradually, it’s possible that it’s not used on some systems yet.
I very closely monitor the processes running on my computer and I know this won’t bother like 95% of users but I want to know exactly what is different about this enough that it needed to be a separate executable and process. I’m assuming it was unrolled from AvastSVC.exe into it’s own process, correct?
edit: Also if I’m being used as part of a slow rollout, can I get removed from the list of people “testing” it out.
Thanks for the update Avast 
Only problem is Behavior Shield comes up disabled initially on Windows 10 Home 64 … Also did it with prior version
Otherwise fine … Hope Avast fixes this once and for all
Yes, it was originally running as part of AvastSvc. This is better because it runs with restricted access rights - so if anything goes wrong (there’s a bug in some scanner/parser and someone takes advantage of that bug), the code can’t really do much (as opposed to AvastSvc which can do anything). Also if a crash occurs, it can easily be restarted and continue scanning.
I’m not going to pretend to know how avast scans files, I’m guessing it’s constantly doing it passively in the background and not just when you run a virus scan, so it has to stay running at all times I imagine, explaining it like that makes me understand more about what it is, it just seems to be using a lot of memory on my machine. Is Avast really so susceptible to outside tampering that something like this was needed to be done though or was this just a precaution in the ever changing world of cyber security?
This is definitely a precaution… the scanner contains a lot of archive unpackers and format parsers - which is a complex and sensitive code, more likely to contain security bugs (than say UI-related code).
I’m certainly not saying we’re pushing that code to a separate process so that we don’t have to worry about security - this is another failsafe that can help if something bad happens (a number of bugs was found in the past few years in various antivirus products which might have had rather serious consequences if the bad guys had learned about them first, so this is not just an impossible scenario that can never happen).
I don’t think it should have any significant effect on memory usage; the modules (DLLs) are shared between processes by the operating system, the memory overhead of the scanner itself should be rather small - and the memory used temporarily during the scan (e.g. to unpack archives) would be allocated anyway, just in a different process.
Alright, next time and I know this isn’t your decision, but could you work to include that in the patch notes, seeing something like that suddenly running and claiming to be from avast for sure made me think something had been compromised on my system, since there was NOTHING about the new process in the patch notes on this update.
Transparency is really important to me when it comes to Antivirus companies as we are trusting our systems to them.
Igor, What is Avast going to do about Behavior Shield not coming up as Enabled on Windows 10 Home 64 ? ? ? ?
Please tell the coders to get this fixed … Thanks
I don’t think this has anything to do with transparency - and it also may be kinda too technical for the (usually quite high-level) update notes.
I mean, this is an internal implementation detail - we also don’t announce that X new DLLs appeared in the installation folder or a new driver in system folder (both are basically the same as an EXE and a new process), some other disappeared, new registry key starts being used…
As for the system looking compromised, I get that - but you can easily verify that the executable module is in our installation folder (which should normally be protected by Avast self-defense) and that it’s properly signed with Avast Software digital signature. Now I would say there’s no harm in mentioning it in the release notes - but since it’s released gradually, I guess it might cause confusion in this particular case (people asking why the process isn’t there even though according to the release notes it should be and wondering if the program works properly)… I’m not sure. (But no, I don’t write the release notes )
Thanks for the new release
I have this one too. I want to disable it too. Im using android emulator(Nox Player) and this aswEngSrv.exe suddenly hogged 85-90% of memory. Can i delete it? Any solution to this one please. 
The offline installers doesn’t contain the 2019 GUI yet (at least not the free version one).
Only after Avast has connected to the internet does the new GUI get downloaded.
This results in a tray icon that doesn’t respond for a long time.
The same thing happened last year.
Devs should make sure that the offline installers always comes with the latest GUI by default!
The same happens on Windows 10 Pro 64.
Adam Kertesz
Now I know it was not something I did and that others are seeing the issue as well. Now we just need Avast to fix it