AppGuard 4.x 32/64 Bit - Releases

@XhenEd i guess you tried from SUA ?

 

No, I'm using MS Admin account.

I realize just now that being an MS account may be the culprit.

 

Yes, I had that same exact thing in mind when thinking about functionality that Sandboxie has that AG does not. That's a clear advantage in using Sandboxie for containment versus some other products.

 

If i'm not mistaken wasn't this suggested when using AG and SBIE couple of years ago in BRN support then it was change to just adding sandbox folder>exception... what's the benefit having the sandbox folder in user space?!

@Lockdown and why can't I add R: which is a RAMdisk to either of the two?!

 

I'm not going to get into this debate. The question has been beaten to death on this forum over the years. Search this sub-forum for pertinent discussions.

The standard answer always has been, and shall remain, make C:\Sandbox a Read\Write exception folder.

It is unclear what you are asking.

 

I am still confused ...

I can add the path to Video.UI.exe, and it comes up in Guarded Apps as 'Video Application' ...

but am unable to * wildcard it in the Guarded Apps dialog, as one can for User Space entries?

 

The name that gets added to Guarded Apps tab is Properties > Description > Video Application. Video Application is what Microsoft put in the description field.

Just use the explicit path; the * wildcard doesn't work for Guarded Apps.

 

Can't use the * wildcard for Guarded Apps file path.

 

You can try appguardpolicy.xml modification as the end-user, but there is no official BRN support for it. I don't think a manually edited xml using the * wildcard will work for a Guarded App since the explicit file path won't resolve.

 

My container folder is in (RAMDISK) r:\, I've tried to add r:\sandbox to either user space and guarded folder(exception) but this is what I get http://tinypic.com/r/kbaib4/9.

 

AppGuard will block executable code in the sandbox if it's added to the user-space, including scripts. All code will be able to execute depending on Sandboxie's settings if the sandbox folder is not added to the user-space. If some malware is capable of breaking out of the sandbox it will not be able to if it can't execute at all. The possibility of encountering some malware that can break out of the sandbox will be remote, but nothing offers 100% protection.

 

@Cutting_Edgetech
Thanks for the info!

 

Not supported

 

With the file-dialog in the category "User Space" it is possible to add wildcards, but not with the file-dialog in "Guarded Apps"

 

I purchased AppGuard 4.xxx in 2014 when it wasn't a yearly license.

1) Can I still use the older version with the lifetime license

2) How/where do I download the latest version (Before it was updated and became yearly)

Thanks

 

1. You can always use AppGuard 4 since you have a lifetime license.
2. @Lockdown said to ask BRN Support for the download link. I mean the AppGuard 4, not AppGuard 5. AppGuard 5 is the latest version, and it's available in the AppGuard website.

 

1. Yes
2.

Code:

http://www.appguardus.com/support/products/AG44/AppGuardSetup-4-4-6-1.exe

 

Extremely helpful, thank you.

 

Is there no longer a trial version of AppGuard?

 

The current version of AppGuard consumer, 5.X, has no trial.

At the moment there is no significant difference between version 4.X and 5.X. There should still be a 30-day trial associated with 4.X. You can download it via this link: http://www.appguardus.com/support/products/AG44/AppGuardSetup-4-4-6-1.exe

I am not sure how much longer the 4.X installer will be available at the above download link. At some point I expect that it will be take down, and only those with a valid 4.X license will be able to obtain the 4.X installer by contacting support.

 

Just my opinion, for those who have no AppGuard yet, invest in AppGuard 5, not AppGuard 4. The "4th" version is end-of-life. So, I suggest that you ignore the 4th version installer offered here, and pay for the 5th version, if you want.

 

Thanks for pointing it out @XhenEd .

4.X can no longer be purchased; it is end-of-life.

Those with existing valid 4.X licenses will only receive pushed vulnerability fixes.

Only 5.X will be actively developed and receive future upgrades.

 

No trial = no try = no reports from Wilders members...