Author Topic: How to test if Secure VM is actually working?  (Read 13266 times)

0 Members and 1 Guest are viewing this topic.

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re: How to test if Secure VM is actually working?
« Reply #15 on: February 10, 2016, 12:00:53 AM »
I think DeepScreen is currently entirely botched on Windows 10 64bit systems. But since it's so hard getting anyone from avast! to just do a damn checkup on it, we are walking in the dark for days now...
Visit my webpage Angry Sheep Blog

Offline Gopher John

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 2098
Re: How to test if Secure VM is actually working?
« Reply #16 on: February 10, 2016, 02:51:22 AM »
error: NG machines are *NOT* ready to use, error: 0x00000032

I can confirm.

AMD A6-5350M APU with Radeon HD Graphics, 8.0GB RAM, Win7 Pro SP1 64bit, IE11
i7-3610QM 2.3GHZ, 8.0GB Ram,  Nvidia GeForce GT 630M 2GB, Win7 Pro SP1 64bit, IE 11
Common to both: Avast Premium Security 19.7.2388, WinPatrol Plus, SpywareBlaster 5.5, Opera 12.18, Firefox 68.0.2, MBam Free, CCleaner

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re: How to test if Secure VM is actually working?
« Reply #17 on: February 11, 2016, 11:38:07 PM »
I tried these commands on Windows 7 SP1, and the result indicated that it is not working.  I do have avastvboxsvc.exe running in services.

What was exact error code from "ngtool isready"

Re-installed avast just for this. It says:
"error: NG machines are *NOT* ready to use, error: 0x00000032"
Visit my webpage Angry Sheep Blog

Offline DavidR

  • Avast Überevangelist
  • Certainly Bot
  • *****
  • Posts: 89061
  • No support PMs thanks
Re: How to test if Secure VM is actually working?
« Reply #18 on: February 15, 2016, 11:25:01 PM »
Bump - no avast follow up for almost 7 days after suggested test - which appears to be failing with errors.
Windows 10 Home 64bit/ Acer Aspire F15/ Intel Core i5 7200U 2.5GHz, 8GB DDR4 memory, 256GB SSD, 1TB HDD/ avast! free 24.3.6108 (build 24.3.8975.762) UI 1.0.801/ Firefox, uBlock Origin, uMatrix/ MailWasher Pro/ Avast! Mobile Security

Offline schmidthouse

  • VIRUS FREE A Long Time
  • Avast Evangelist
  • Starting Graphoman
  • ***
  • Posts: 7170
  • When you think you know, Think Again
Re: How to test if Secure VM is actually working?
« Reply #19 on: February 17, 2016, 04:59:57 AM »
Is anyone from Avast going to follow up on this?  ???

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re: How to test if Secure VM is actually working?
« Reply #20 on: February 17, 2016, 09:07:00 AM »
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.
Visit my webpage Angry Sheep Blog

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 297
Re: How to test if Secure VM is actually working?
« Reply #21 on: February 17, 2016, 03:07:25 PM »
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
« Last Edit: February 17, 2016, 05:03:49 PM by Spec8472 »

REDACTED

  • Guest
Re: How to test if Secure VM is actually working?
« Reply #22 on: February 17, 2016, 06:26:37 PM »
Code: [Select]
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

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 297
Re: How to test if Secure VM is actually working?
« Reply #23 on: February 17, 2016, 06:38:33 PM »
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.

Offline Patrick2

  • Poster
  • *
  • Posts: 489
Re: How to test if Secure VM is actually working?
« Reply #24 on: February 17, 2016, 07:20:09 PM »
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
Windows 10 Pro 64bit 1909 18363.476, Intel I7 7700 Nvidia Geforce 1050 16gb DDR4, WD 250GBSSD, 1tb Storage, Avast Free 19.8.2393
HP Omen Laptop Intel I7 7700HQ, 8gb Of Ram Windows 10 Home x64 1909 18363.476 128GB SSD, 1tb Storage, Avast Free 19.8.2393

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 297
Re: How to test if Secure VM is actually working?
« Reply #25 on: February 17, 2016, 07:39:08 PM »
Same problem with Windows 10. Registry templates not installed.

Will be fixed in next release, sorry for that

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

Offline Patrick2

  • Poster
  • *
  • Posts: 489
Re: How to test if Secure VM is actually working?
« Reply #26 on: February 17, 2016, 08:24:09 PM »
Ok Thank you

Windows 10 Pro 64bit 1909 18363.476, Intel I7 7700 Nvidia Geforce 1050 16gb DDR4, WD 250GBSSD, 1tb Storage, Avast Free 19.8.2393
HP Omen Laptop Intel I7 7700HQ, 8gb Of Ram Windows 10 Home x64 1909 18363.476 128GB SSD, 1tb Storage, Avast Free 19.8.2393

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re: How to test if Secure VM is actually working?
« Reply #27 on: February 18, 2016, 02:27:57 AM »
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).
Visit my webpage Angry Sheep Blog

Offline Spec8472

  • Avast team
  • Sr. Member
  • *
  • Posts: 297
Re: How to test if Secure VM is actually working?
« Reply #28 on: February 18, 2016, 09:35:51 AM »
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

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

Offline RejZoR

  • Polymorphic Sheep
  • Serious Graphoman
  • *****
  • Posts: 9406
  • We are supersheep, resistance is futile!
    • RejZoR's Flock of Sheep
Re: How to test if Secure VM is actually working?
« Reply #29 on: February 18, 2016, 01:02:27 PM »
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.
Visit my webpage Angry Sheep Blog