Sandboxie Support

@Curt

Any update regarding compatibility issue with MalwareBytes Anti-Exploit?!

Nix wrote:@Curt

Any update regarding compatibility issue with MalwareBytes Anti-Exploit?!

The ball is in MB's court. They are investigating why MBAE is not attempting to inject into Sandboxie.

What about the bug which causes Sandboxie to return the path to real folder instead sandbox folder?

You already fixed part of the problem, an issue coming from version 3.x times, but there is still a problem there, in version 4.x.

Buster wrote:What about the bug which causes Sandboxie to return the path to real folder instead sandbox folder?

You already fixed part of the problem, an issue coming from version 3.x times, but there is still a problem there, in version 4.x.

What are the APIs causing problems?

Curt@invincea wrote:What are the APIs causing problems?

It is a problem in Sandboxie but I have no idea where it is located. All I can do is send you a malware you can use for testing and you track down to the origin of the problem.

You know there is a bug because you already found one related to this issue. Somewhere in Sandboxie code there is still a problem.

Curt@invincea wrote:

Nix wrote:@Curt

Any update regarding compatibility issue with MalwareBytes Anti-Exploit?!

The ball is in MB's court. They are investigating why MBAE is not attempting to inject into Sandboxie.

Thanks Curt..

Any update on the dropped rights issues? Running latest version and still get the following error when launching Chrome (38.0.2115.111 m) (on desktop and laptop) with drop rights box checked.

Dropped rights for Chrome is a problem for a few months. Sandboxie fixes something then new Chrome version comes and dropped rights doesn't work again.
In my personal opinion latest Chrome x64 & Sandboxie 4.14 works slower than first x64 Chrome releases and Sandboxie 4.13-3/4 beta. So I switched to pcxFirefox (x64 Firefox), however some sites are broken on Firefox.
Also Chrome with hardware acceleration and flash causes bluescreens for some systems. Not sure if it's the graphics drivers, Chrome itself or something else... I never had bluescreen using Firefox & HTML5 youtube player

Buster wrote:

Curt@invincea wrote:What are the APIs causing problems?

It is a problem in Sandboxie but I have no idea where it is located. All I can do is send you a malware you can use for testing and you track down to the origin of the problem.

You know there is a bug because you already found one related to this issue. Somewhere in Sandboxie code there is still a problem.

I see something similar with Internet Download Manager and Chrome 38 x64:
Chrome is started sandboxed, IDM too (or isn't running at all). But when IDM is started/accessed via Chrome's browser plug-in, another IDM session starts outside of Sandboxie and is able to write outside of the sandbox.
This happens although IDM compatibility is unchecked in Sandboxie.
Dangerous?

Julian wrote:

Buster wrote:

Curt@invincea wrote:What are the APIs causing problems?

It is a problem in Sandboxie but I have no idea where it is located. All I can do is send you a malware you can use for testing and you track down to the origin of the problem.

You know there is a bug because you already found one related to this issue. Somewhere in Sandboxie code there is still a problem.

I see something similar with Internet Download Manager and Chrome 38 x64:
Chrome is started sandboxed, IDM too (or isn't running at all). But when IDM is started/accessed via Chrome's browser plug-in, another IDM session starts outside of Sandboxie and is able to write outside of the sandbox.
This happens although IDM compatibility is unchecked in Sandboxie.
Dangerous?

I worked around the same issue by forcing IDM to run sandboxed but really don't know whether dangerous.

@Julian
This is the right forum to post problems and questions regarding Sandboxie releases.
Look, by reading these two post of rpljhun:
http://forums.sandboxie.com/phpBB3/view ... 63#p104563
http://forums.sandboxie.com/phpBB3/view ... 63#p104563
and what I told you in my previous post you can easily workaround the issue.