Apparently not. And neither will I. I simply cannot use avast! anymore if DeepScreen is appearing as working, while it’s really not working and just passes supposedly scanned apps through in 1 second. Which makes me believe it doesn’t scan them at all, it just shows a scanning message and executes them straight away. Considering no one cares to properly address and explain the situation, I’m not taking any chances. I just have no idea what the hell is going on with avast! team and program itself.
Can you please execute command “ngtool.exe avast install”?
There will be an output to console window, which will help to identify the issue.
Thank you
Building process started (normal)
Installing VirtualBox...
Creating snapshot...
BCD volume: \\?\GLOBALROOT\Device\NgVolumeSnapshot1
Windows volume: \\?\GLOBALROOT\Device\NgVolumeSnapshot2
Creating new hive files...
ERROR: Hive cant be generated. res=2{SystÚm nem??e nalÚzt uvedenř soubor.}, name=BCD.
error: ngtool.exe (regbuilder) exited with error: 0x00000002
Building process finished, result=0x00000002
error: CmdAvastInstallWrapper failed, error: 0x00000002
The problem is caused by bug in current (2016R1SP2) installer. The registry templates for Windows 10 are not installed properly. Will be fixed in next release.
Here is what my NG log says
17.02.2016 10:54:39.174 6340 | Creating snapshot…
17.02.2016 10:55:15.037 6340 | BCD volume: \?\GLOBALROOT\Device\NgVolumeSnapshot1
17.02.2016 10:55:15.083 6340 | Windows volume: \?\GLOBALROOT\Device\NgVolumeSnapshot2
17.02.2016 10:55:15.083 6340 | Creating new hive files…
17.02.2016 10:55:16.474 6340 | error: ngtool.exe (regbuilder) exited with error: 0x00000002
17.02.2016 10:55:16.505 6340 | Building process finished, result=0x00000002
17.02.2016 11:44:42.978 7976 | Building process started (idle)
17.02.2016 11:44:43.047 7976 | Creating snapshot…
17.02.2016 11:44:53.439 7976 | BCD volume: \?\GLOBALROOT\Device\NgVolumeSnapshot1
17.02.2016 11:44:53.453 7976 | Windows volume: \?\GLOBALROOT\Device\NgVolumeSnapshot2
17.02.2016 11:44:53.787 7976 | Creating new hive files…
17.02.2016 11:44:54.144 7976 | error: ngtool.exe (regbuilder) exited with error: 0x00000002
17.02.2016 11:44:54.429 7976 | Building process finished, result=0x00000002
17.02.2016 11:46:42.856 1964 | Building process started (idle)
17.02.2016 11:46:42.921 1964 | Creating snapshot…
17.02.2016 11:46:51.279 1964 | BCD volume: \?\GLOBALROOT\Device\NgVolumeSnapshot1
17.02.2016 11:46:51.453 1964 | Windows volume: \?\GLOBALROOT\Device\NgVolumeSnapshot2
17.02.2016 11:46:52.111 1964 | Creating new hive files…
17.02.2016 11:46:52.381 1964 | error: ngtool.exe (regbuilder) exited with error: 0x00000002
17.02.2016 11:46:52.569 1964 | Building process finished, result=0x00000002
Same problem with Windows 10. Registry templates not installed.
Will be fixed in next release, sorry for that
Ok Thank you
I don’t understand how such complex subsystems don’t have ANY self-diagnostics. I mean, if something is broken, user should be notified about it so you don’t surf around with false sense of security.
If it wasn’t for me bitching relentlessly, this would never be noticed and fixed. Or WAY too late. Why is this even needed when avast! could be doing this on its own. It would just be good practice. And same goes for Repair function. Instead of avast! doing self-diagnostics and if problems found, automatic repair, it does neither. Ugh? And often using Repair function fixes thins (well, apart from this case).
Secure VM is not crucial for deepscreen. Avast Repair basically just checks integrity of all installed files and settings and reinstall original file if corruption is detected. As registry templates for Windows 10 were not installed at all, the issue can’t be fixed using the repair method.
If you want to repair Secure VM manually:
http://public.avast.com/~hnanicek/windows10_10586.zip is for 32bit Windows 10 TH2
http://public.avast.com/~hnanicek/windows10_10586_x64.zip is for 64bit windows 10 TH2
- Disable self-defense
- Extract corresponding archive into “c:\Program Files\AVAST Software\Avast\ng\registry” folder
- Enable self-defense
- Launch “ngtool.exe avast install” as admin
If it’s not crucial for DeepScreen, then how come it finishes pretty much everything in under 1 second. It never worked that and that just feels wrong like it’s not even doing anything. And yet, in all this time we never received straight answer whether that’s normal behavior or not. So, it led me to believe it’s not and I removed avast! because of it.
If process exits normally in 1 sec, then it is correct behavior that it exits in 1 sec if it’s virtualized in deepscreen (without secure VM). If secure VM is used for virtualization, it takes much longer even if virtualized process exits immediately, because in Secure VM system wide virtualization is performed, monitoring all processes.
Is it not safer to use virtualization (Isolation) ???
Nope:
Building process started (normal)
Installing VirtualBox...
Creating snapshot...
BCD volume: \\?\GLOBALROOT\Device\NgVolumeSnapshot1
Windows volume: \\?\GLOBALROOT\Device\NgVolumeSnapshot2
Creating new hive files...
Cloning NTFS volumes...
Creating a new VM machine...
Starting VM machine to create initial snapshot, it can take a couple of minutes...
error: PrepareNGSource/HgcmRpcWaitForGuestReady failed, error: 0x000005b4 (state: 5)
error: PrepareNGSource failed, error: 0x800705b4
Building process finished, result=0x800705b4
error: CmdAvastInstallWrapper failed, error: 0x800705b4
VM guest timeouted, what OS?
From the quote edit it’s obviously W10x64.
Can you please provide “c:\ProgramData\AVAST Software\Avast\ng\NgBase\Logs\VBox.log” file?
Attached.
Seems NG didn’t finish creating snapshot on mine either, I think CPU supports AMD-V, can’t find Virtualziation option in Asus UEFI bios, I looked all around it
Can’t seem to find vbox.log file on my system here
System is Asus M52BC_M32BC, AMD FX 8310 Processor (Eight Core Processor) WIndows 10 Home x64bit, 8gb of DDR 3 Ram, 2tb hard drive
Hi, in both cases, guest wasn’t able to load even guest<->host communication driver, which is one of the first drivers to load during guest boot. Could you please provide also screen snapshot of guest?
Screen snapshot can be captured by executing “ngtool.exe png NgBase c:\guestscreen.png”. This command should be executed while there is base snapshot build (“ngtool.exe avast install”) in progress let’s say for ~10 minutes.
Thanks
Why is all of a sudden not working? It used to work fine before you guys introduced the “SSD only” rule. I had avastSandbox thingie in processes and DeepScreen scanning always took longer. Now I have no avastSandbox in processes even if Secure VM is enabled in settings and like I’ve reported, no VM found. Maybe you should check the older builds and see what you have changed there that broke all this.