Have problems with the new Avast 2016 Free on my Win 7 Pro SP1 64-bit machine. (It’s a Dell Optiplex 7010 with 16GB RAM and an Intel Core i5 3470 with 4 cores, and with hardware virtualization turned ON in my BIOS.)
First, after the reboot, the new (to me) process aswFe.exe runs for a LONG time and consumes 25%± of my CPU. At least an hour.
Second, following other posts here, I checked how (or whether) NG was actually running. See the attached screenshot of my attempts in cmd to check - lots of error messages. You can see I tried to start it although I don’t know these commands and was just “pushing buttons”. But lots of ERRORS. Please open the attachment jpg. (It’s formatted for legal size paper, which was a clearer image.)
So what is happening with NG and this aggressive process aswFe.exe? Is NG even running on my machine? Am I getting the benefit of Avast’s virtualization features? Are the Avast sandbox features running at all? How do I check?
I just re-checked my post above from a different computer (not logged in), and the attachment above had disappeared. But now viewing from my original posting PC (logged in), it’s here now.
My thread is pointless without the attachment. It’s here now, but is it missing for anyone else?
Asyn - Submitted a ticket, but that will take a while, and I doubt the front-line tech team will know anything about my attachment above.
Would much appreciate this forum’s advice - how do I test whether NG is running in this new Avast? Or whether any of the sandbox features are working? (What does NG do anyway?)
Here, instead, ngtool.exe, mftutil.exe, aswFe.exe, every time that the operating system start, cpu usage 36% (on average), again and again, again, again, again, again, again, again, again, again , again, a nuisance monstrous !!!
30 minutes of hard drive and CPU every time !!!
In previous versions, the three tool, were initiated only the installation of avast or a new update of the program. Please solve !!!
Bye to all. :o :o :
Asyn - thanks for info. But from your link to pk’s description, it seems that the “errors” in my cmd screenshot above mean that Avast NG is NOT ABLE to create the VirtualBox VMs on my PC that are part of NG. But my PC definitely has hardware virtualization. I have run the Win 7 machine in XP Mode a few times just for fun. And I have just re-run MS’s havdetectiontool, and it reports that “This computer is configured with hardware-assisted virtualization”.
Also, in Settings for my 2016 Avast, “Enable DeepScreen” and “Use secure virtual machines” are both checked.
So what do we do? How do I test further to determine why there are “errors” in my cmd screenshot above, or to see whether NG is working on my machine?
By the way, aswFE.exe does not seem to re-run on bootups. However, the problem continues with ngtools and the above indications (and cmd results) that NG is not running correctly because Avast is failing to make the needed virtual machines.
Just to add some detail –
In the BIOS for my Optiplex 7010, these are the settings under the caption “Virtualization Support”:
Virtualization - Enable Intel Virtualization Technology is CHECKED
VT for Direct I/O - Enable VT for Direct I/O is CHECKED
Trusted Execution - Trusted Execution is UNchecked.
I have also attached the more detailed hav log file from this morning’s run of MS’s havdetectiontool. Looks good to me.
So how do I test the NG sandbox? Doesn’t Avast have a web link with a fake bad page that would put it to the test?
And yes, NG is a kind of sandbox, mainly to determine the file is malicious or not.
BTW, this is my personal opinion: internal tools (ngtool.exe for example) should only be executed by avast itself, not by user’s intention, even if there is built-in help text.
You don’t know what they perform or what is needed to properly execute these tools.
Playing with these tools might be fun (I can understand it), but it should be done at your own risk using your own knowledge.
Expecting official support for your playing is just not good.
NON - thanks for that link. Unfortunately, Firefox blocks the page and gives me a warning before Avast does anything. No reaction from Avast. So I still have no idea whether NG is running or doing anything.
My purpose was to test whether NG and some kind of sandboxing are working on my PC, not only to have fun. And the idea to try to run the stuff in CMD was from a diferent Avast thread.
RejZoR and NON – NON’s question directly above is a good one, and maybe we’re starting to get somewhere.
Each of you, please run an elevated cmd and then run the ngtool isready test shown in my attachment at the top of this thread, and post here the results. From what I can see, the ngtool isready command is just a test to see whether NG is working on your PC. In my case, the result is an error message that my NG virtual machines aren’t ready. Very curious to see what it tells each of you.
I think you might get there using cd C:\Program Files\AVAST Software\Avast\ng
then type ngtool isready
