AppGuard 4.x 32/64 Bit - Releases

Thanks Pegr, I appreciate it

Lots of helpful information

 

While I mostly absolutely agree with you pegr in regard to AppGuard here I would make an addition.

To include Sandbox container folder to user space or not highly depends on WHAT sandboxes you have or for what you use Sandboxie.

If you have some everyday sandboxes: f.e. for browsing, for multimedia etc. and run programs installed on your real system >> than yes: make those sandbox folders user-space folders for additional protection. (example: C:\Sandbox\Browsing\ )

If you have some test sandboxes, f.e. for testing installations or where you install programs to. >> than no: do not make those sandbox folders user-space folders or it won't work the way it should. (example: C:\Sandbox\Test\)

 

Yes, you are right. Multiple sandboxes used for different purposes may require different configurations.

Thanks for the clarification and for pointing that out.

 

Quick update on V4 and my W7 x64 SP1 machine: It is running invisibly and without a single issue. Thanks for the free upgrade, and best of luck to Blue Ridge Networks and their employees.

 

Is there anything else in general that should be added to "User Space?"

 

System space isn't confined to windir and program files folders by default? I'm a little confused here as to which folders are on system space and which aren't. For instance, SBIE's default sandbox folder is considered a part of system space even if outside of windir and program files folders (C:\Sandbox). Is there a list of locations for system space I can peruse?

 

The Sandboxie container is the main folder that needs to be at least partially in user space as far as reading and writing goes. You probably won't need to make any configuration changes, other than Sandboxie.

 

System Space is anything that isn't considered to be User Space. By default, User Space consists of user profile folders, non-system internal and external hard drives, removable media, and network drives. By default, System Space is every folder on the main system partition, apart from user profile folders.

It is possible to change a folder's default allocation by moving it from System Space to User Space, and vice versa; The Windows and Program Folders may not be moved from System Space to User Space though as they are core components of the trusted enclave. Any attempt to move these will result in an error message being displayed.

Have a look at post #5 in this thread, which explores these subjects in more detail.

 

These Dropbox memory blocking events are causing explorer to crash on system Startup, though explorer does restart itself automatically.

dja2k

 

You will not get this issue if you use AppGuard in medium level. But if you still prefer to use lockdown mode, then you have to exclude this directory from user space. C:\Users\<UserName>\AppData\Roaming\Dropbox\bin. ie., under User Space tab, add this directory and select 'No' option.

 

I am already using AppGuard in Medium, so then what do I have to do?

dja2k

 

Add dropbox.exe to guarded apps. That should solve the problem.

 

Thanks, but I already have that too !!!

dja2k

 

That's strange. Btw I don't have dropbox in my windows startup item. I use it only on demand. Maybe that makes a difference.

 

Yes I have it on Startup and that's probably the difference.

dja2k

 

This is not a criticism as I'm not sure of the way AppGuard intends to protect the *disc* drive. Is it system space? It's certainly not user space; maybe no-mans-land.

If I burn, say, a batch file and program to a CD, I can then insert that disc and can run the batch file, start services (from batch), run the program; all with AppGuard on "Locked Down".

AppGuard does stop me from writing to the C drive but apart from that, not a peep. Personally, I would prefer the disc drive to act more like a USB drive with user space.

 

Yes, c:\sandbox needs to be added as exception folder on the Guarded Apps tab.


I have c:\sandbox added to userspace because Pegr recommended it for security reasons:

 

I could use a little help, please...

I have a couple of old DOS programs that I still use quite regularly with Windows XP. They are not in my Program Files folder, but rather in the root directory (C:\). I load them from desktop shortcuts. However, since upgrading to AG 4.0, these programs will no longer launch. Instead, I get an AG error message that says "...is not a valid Win32 application" -- which is true.

Actually, I cannot remember how I did it, but they worked with AG 3.5.6. Sure hope someone can help me figure this out.

Edit: Think I figured out what needed to be done.

 

Care to disclose what you did ? Could help other people with the same problem

 

Place those files inside some directory and exclude the directory from user-space. Go to user space tab and select the folder and give 'No' under include.

 

I simply moved the DOS shortcut from the desktop to the Program Files folder. Slightly less convenient, but not all that bad. Easy fix and it works for me.

 

Question, if I add "C:\sandbox" to userspace, does the "Include" option need to bet set to "Yes" or "No"?

 

Correct.

 

The desktop folder is located within the user profile of the current user logged on to Windows, and therefore lies in user space.

In order to move the shortcut to a system space location that makes it convenient to use, right-click on the Start button on the taskbar and select Open All Users then move the shortcut to the Programs folder. Unlike the current user profile, which is in user space, the All Users profile is in system space. You should now be able to run your program via Start->All Programs without interference from AppGuard.