[quote="Mardorz post:40, topic:703530"]
I made a clean reinstall but no luck, the errors in the log are the same.
I am already in contact with the support, and he stated the problem will be fixed in the next update.
So it seems the current update is not helping my cause, i attached my log.
EDIT:
ngtool isready is resulting in : "NG machines are NOT ready to use, error: 0x00000032
ngtool conditions met results: “CmdConditionsMetWrapper done (result: 0x00000000, bNotMet: 0x00000000)”
[/quote]
Never knew it wasn’t working, why doesn’t Avast check for its status? Re-installed, and everything appears fine, except it fails to protect from AutoSandbox Test Tool.
I get “NG machines are ready to use.” and “CmdConditionsMetWrapper done (result: 0x00000000, bNotMet: 0x00000000)” in the end. And the log looks fine overall (see attached).
I did import my settings and custom installed w/o Mail Shield (use webmail), Avast Remote Assistance (unneeded), SecureLine (paid-only), GrimeFighter (paid-only), Rescue Disk (unneeded), and Avast gadget (unneeded). That shouldn’t matter though, cause the rest including NG is installed.
I discussed it with developers. It seems you have broken VSS (Volume Snapshot Service). Windows System Restore may not work on your machine. Apparently, this is not caused by NG.
Could you confirm that Windows is able to create snapshots? It happens after windows update or when installing some application (e.g. avast)… or you can create your own snapshot (Control Panel - System - System Protection).
I’ve disabled System Restore, because it’d be unnecessary with AX64 Time Machine. Do I have to re-enable it for Avast to work properly? Is there another way? Thanks.
*I’ve temporarily re-enabled it and tried to create a restore point. Backing up previous version of files of my data HDD worked, but once I try my system SSD:
Currently NG needs System Restore to work properly.
I suppose you have system partition on the SSD… NG needs System Restore working on the system partition otherwise it fails to run the virtual environment.
Leaving the Self defense Module on, causes system restore not create a restore point or, using the restore point
created doesn’t work. When an update to the avast program happens, if the selfdefense module is on, the restorepoint just doesn’t happen.
It’s not the Self-Defense Module for me, just can’t create restore points right now. I don’t think other virtual machines or disk imaging programs rely on it, so why does Avast? Can’t it just access the Volume Shadow Copy service directly?
*Well since currently Avast needs it to utilize NG, I’ll try to find a way to fix System Restore.
*Just ran Volume Shadow Copy service without problems, but still no System Restore. Also tried Runtime’s Shadow Copy, which had no issues.
@bob1360…I have Self Defense Module enabled/checked (W7 64bit) and have no problem creating restore points…AND I can revert the system back to a given restore point fine…BUT once restored Avast does not work (shields off & cannot correct, etc.) and I have to clean un-install Avast & re-install. I looked at your video and I had taken it that you had to create a restore point with SDM off as well as if you did a System Restore that you needed to disable SDM…and it took both of these steps for Avast not to be corrupted. For me, my System Restore point creation is done on a schedule so I do not have a chance to disable SDM…thus I just reside myself that I need to disable SDM on a system restore (just to be sure it does not do any other nasty bad things) and will need to un/re-install Avast once my system is restored.
The above does not sound like what you experience ?
NG or no NG…it would trouble me ALOT if using Avast in any way prohibited and/or corrupted a restore point…that would not be acceptable to me and I’m betting not to the masses either.
I haven’t tried all of the steps exactly yet (kinda busy), but from what I can deduce, they probably won’t fix my problem. What I’m wondering is why Avast NG needs System Restore unlike all other similar programs I’ve come across so far? VirtualBox sure doesn’t need it, nor does any disk imager I’ve seen.
But for now, I will try troubleshooting System Restore later. I just hope Avast doesn’t rely on it indefinitely.