So the best freeware classical HIPS is only getting better (Easter be happy, Aigle I kicked out Comodo again due to "Explorer" problems, system frooze in boot process after problem Explorer, unable to do anything, because I cleaned up old images next day problem occurs, have no virtual memory so could not provide Comodo with windows dump info or do any problem tracing myself).

I am only intersted about Sandbox. IMO sanboxes of HIPS are not as good as they are just policy based with no virtualization that leads to limited finctionality. CFP itself has a sanboxing policy, NG also has a policy similar to that but not the same as a proper Sanbox like SBIE, GW, DW, SafeSpace etc.

I expect the new sandbox feature pf EQS to be as good as the 'run safer' option in Online Armor. This means it is better than Drop my RIghts, because it also drops the rights of any called/spawned child process. It means that is less secure than DefenseWall/GeSWall which also remember the status (admin or limited = trusted or untrusted) of files created by processes with limited rights.

Sandboxie and SafeSpace also have file system virtualisation implying that you can purge changes made by applications running in the sandbox very easily. Returnmil and ShadowDefender and Steady state also offer complete disk virtualisation from all aps.

A good policy sandbox (DefenseWall) is as effective as a good application based virtualisation program (SafeSpace). Policy sandbox (GW/DW) is easier to use in normal usage, an application based virtualisation sandbox (SB/SS) has a clearer reverse modus (simply allow or purge ALL). So it is up your preference,

Disk virtualisations are an extended security mechanism: I can understand that some people use DW/GW + Returnil/PowerShadow to benefit both from the ease of use (normal surfing with policy sandbox) and purging of all changes by all programs by disk virtualisation sandbox. I cannot understand people who use GW + Sandboxie (both application based protection) or Sandboxie and Returnil (both have ease of use of purging the virtual sandbox)

EQ4.0 still has some bug need to fix such as BSOD, so you all need more patience to wait for the final.
to the sandbox of EQ, I can say the only thing is that the sandbox use virtualization as well as sandboxie, but still has some problems need to resolve.

EQ4.0 still has some bug need to fix such as BSOD, so you all need more patience to wait for the final.
to the sandbox of EQ, I can say the only thing is that the sandbox use virtualization as well as sandboxie, but still has some problems need to resolve.

Click to expand...

That will be great indeed. Does the sandbox has some pre-coded default rules or u have to make rules urself?

Is it correct that you need 3.41 installed first...then you over-write EQSecure folder in Program Files with this beta before you can get it to run correctly? I tried to follow the beta thread at EQSecure forum but the translation from Chinese left something to be desired.

Is it correct that you need 3.41 installed first...then you over-write EQSecure folder in Program Files with this beta before you can get it to run correctly? I tried to follow the beta thread at EQSecure forum but the translation from Chinese left something to be desired.

Later...

Click to expand...

yes. you need 3.41 installed first, then you over-write EQSecure folder in Program Files with this beta, and most important is you need reboot your system.