How to test if Secure VM is actually working?

[Spec8472]

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.

[bob3160]

Is it not safer to use virtualization (Isolation)  

[REDACTED]

If you want to repair Secure VM manually:

http://public.avast.com/~hnanicek/windows10_10586_x64.zip is for 64bit windows 10 TH2

1) Disable self-defense
2) Extract corresponding archive into "c:\Program Files\AVAST Software\Avast\ng\registry" folder
3) Enable self-defense
4) Launch "ngtool.exe avast install" as admin

Nope:

Code: [Select]

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

[Spec8472]

VM guest timeouted, what OS?

[REDACTED]

From the quote edit it's obviously W10x64.

[Spec8472]

Can you please provide "c:\ProgramData\AVAST Software\Avast\ng\NgBase\Logs\VBox.log" file?

[REDACTED]

Attached.

[Patrick2]

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

[Spec8472]

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

[RejZoR]

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.

[REDACTED]

Screenshot says:

Code: [Select]

BOOTMGR image is corrupt. The system cannot boot. 

[REDACTED]

^^@Spec8472

Bump to get this up after it got buried over weekend.

[Spec8472]

As NG guest is using very same BOOTMGR as host, I don't see how it can be corrupted. Are you using EFI boot? Are you using multiboot (multiple OS installed)?