AppGuard 4.x 32/64 Bit - Releases

Yes, I understand. Either Ignore or Exclude. IE seems same with Exclude (now) as with Ignore (before) for these c:\sandbox events.

 

Where is your sandbox. D is OEM Recovery, E is Optical.
I don't have another partition.
C drive has served my Sandbox for 8 years.

 

@guest creates separate partition. It is an added security measure. Something breaks out of C:\Sandbox it is on system partition. Something breaks out of non-system partition, it has a few hurdles to jump in order to mess with system.

 

Okay, I'll google....create partition.

 

It is on D ; i always create 2 non-system partitions right away after clean-installing any newly bought computers. For me C is a "virgin's temple" that should stay free from penetration
not saying i immediately delete the recovery partition.

 

So, I may set Sandbox container on Recovery partition...?
Had not heard (till now) user setting container on D.
And what for example goes to non-system partitions.

 

My system :

C : OS and only necessary programs , i have around 10 installed programs max; mostly security softs, Office, etc...
D : Portables Apps (Cleaners, monitors, media players, etc...) , softwares installers, download Folders, etc...
E: Medias & Docs (movies, music, pictures, etc...)

Compartmentalization is security.

 

So, path becomes D:\Sandbox\%USER%\%SANDBOX%
Hmm, Compartmentalization is security and C is a "virgin's temple".

 

What is that, what sandbox program are you using?
i use Sandboxie and set the container as D:\Sandbox

 

ah yes, i forgot the full path; yes this is it. just select D on the panel.

 

with Sandboxie's container on D , no more problem with Appguard , just put D drive as user-space. that is it.

 

So, d:\ as User Space Yes or d:\sandbox as User Space Yes
and do I still need d:\sandbox Exception (Read/Write).

 

just D:\ as user-space and yes

 

Jeez, someone needs to tell BRN, with Sandboxie's container on D, no more problem with AppGuard.

Okay, no Add Folder Exception and I had already added d:\sandbox Yes before reading just D:\
(I'm using lower case where AppGuard uses lower case e.g., d:\sandbox).
I'll head scratch why just d:\ vs. d:\sandbox
I've removed earlier Ignores and Excludes re IE11.
IE11 sandbox runs with nary a peep from AppGuard.
Thanks!

 

@guest
I've read 2.2, before...but, until you prompted me. The gist of 2.2 went over-my-head.

 

If the sandboxie-folder is on C: (System-Space), there are 2 steps:
1) The System-Space folder to be moved is added to the list in the User-Space tab, setting the Include flag to Yes in order to guard its executables
User-Space: c:\Sandbox Include=Yes
2) The folder is also added as an Exception Folder via the Guarded Apps tab, with the Type flag set to Read/Write in order to unprotect it
Exception-Folder: C:\Sandbox (Read/Write)

But if it's located in User-Space D: you don't have to do these steps.
Edit: Non-system volumes (all except C: ) = User Space

 

Yes, I'm understanding 1) and 2).
Yes, I was holding on to C:\Sandbox because (in short) I did not appreciate nor understand D:\Sandbox #5012
Sandboxie had never presented as having a need for #5012.
And I only recently came back to AppGuard. (I'm resting HMP.A)
The notion to relocate the sandbox container folder never presented nor occurred to me (over-my-head).

Much appreciation and respect to mood and guest and hjlbx for your collective help and hand holding.

 

Can You write what size do You have these partitions ?

 

other layers protection ?

 

Could You write me me the software ?

 

It depends on the level of your paranoia. I feel perfectly safe with Sandboxie on my C: drive.

 

AppGuard activity has been graveyard quiet since move to D: