AppGuard 3.x 32/64 Bit

Dear Barbara,you said:

Could you please clarifiy what an ETA is?

I am particularly concerned about the lack of a MBR Guard in the new version,so I hope you really will be able to provide at least the same level of protection that 3.5 gave with a separate program to be installed alongside v.4.

What i'm unsure about is:

1-previous MBR guard was useless as threats pierced through it?

2-is it now 'optional' since the malware situation is worse and totally useless or
the new version 4-although apparently less 'granular' to set up- makes it superflous?

I thought it was a very attractive feature of v.3-3.5, in spite of knowing there is no 100% protection.

3-Will the new v.4 work fine with Sandboxie or is there a new research to be made? Will v.4 just inherit all v.3.5 settings about Sandboxie?

(if there are a couple of negatives I'll stick with 3.5 for a while then)

I received today the new license as well for which I thank you very much.

 

@karad

The new version should inherit the settings of the old version. Memory guard exceptions however are no longer applied, because they are no longer needed with Sandboxie and AppGuard 4. There is also no need to make any Sandboxie process a power app. Only your sandbox folder should be listed as a read/write folder under guarded apps.

 

ETA is.....Estimated time of arrival.......now you know....

 

Yes. Thanks Barb. I decided to go ahead with a reformat.

 

Is beta 4.0 license key also valid for the final version?

 

yes the key works fine here for me.....

 

Thank you FleischmannTV, your hints are of paramount importance for me: I'll probably install the new version tomorrow, but i still hope
Barb will tell me something about the MBR Guard questions.

Thanks also to SIR****TMG for explaining ETA, I should have thought about that!

 

Hey Barb, I noticed I got two emails about version 4.0 and a license. One was to one email that I used when purchasing my 3.0 license, and one was to my newer email that I used for the beta, so essentially I ended up with two 4.0 licenses. This is a mistake, so if you want to revoke one of the licenses, I would understand.

 

I was a beta tester but I dint get any emails. My beta license still worked though.

 

I received two too. But the lic. no. is the same.

 

So, does anyone know why the MBRGuard was eliminated in 4.0?

 

I like the concept of this program but can someone please explain to me how to set a password to protect settings,shutdown&uninstall?i have windows 8.1-2 windows user accounts(mine&families).I don't want the families account to be able to mess with appguard settings?thanks

 

Thanks for doing this. I was going to suggest this as well - wasn't sure if I could do or if I needed to get a moderator to do this.

Including link so that others can get there easily: https://www.wilderssecurity.com/showthread.php?t=355206

 

AppGuard version 3.56:

I sometimes get the message in the attached image when on High Protection Level. Is this message anything to be concerned about? Do I need to make any changes?

Thank you.

 

Unless something appears not to be working properly, which in this case is unlikely, you can simply ignore the message.

 

Is it possible to set AG 3.5.6.0 not to start with Windows.

 

First in Appguard, Advanced Tab, enable "Stop Self Protection (Tamperguard)"

Disable the Appguard service and remove the Run Registry Key for Appguard Gui.?

But my question is why do you want to do that ?

 

I thought i might want to do it once in a while but not all the time.

 

You can select the Protection Level "Off"

but you also must deselect the option "Re-Enable <xxxx> level after <xx> minutes.

This will make sure, that even after a reboot Appguard doesn't get enabled.

 

I never saw "Re-Enable <xxxx> level after <xx> minutes before. The version i had before this 3.5.6 might not have had it. A few things i have don't install unless AG is set to off. So if i had to restart..the timeout would be gone and it would be on High again.

 

You can only see that option when you select the "Install" or the "Off" Level, otherwise it's hidden.

 

AppGuard has two MemGuard Write exceptions for Chrome's wowhelper.exe(in Program Files and AppData.) Why is it necessary to make an exception for wowhelper.exe? The new Opera(based on Chromium) also has a wowhelper.exe file, but so far it seems to work fine without adding it to the exceptions. Normally I wouldn't worry about it, but wowhelper.exe has something to do with the Sandbox:
http://productforums.google.com/forum/#!topic/chrome/Jy396DcasP4

 

If you are running AppGuard 4.0, there is no longer any need to make any MG exceptions. If you are running AppGuard 3.5, it may be necessary to have these exceptions. Chrome did not work without specifying them as exceptions (at least at some point - perhaps an update to Chrome fixed the issue and perhaps that is why Opera works). If you're running AppGuard 3.5, you could try removing them from the MG exception list. If you're running AppGuard 4.0, the MG exceptions may still be in your user-defined XML file. If that is the case, you might have to restore defaults in order to get them removed since the GUI controls for MG have been removed from the product.