Sandboxie Support

Actually it is possible to run several IE versions through non-conventional methods:
http://utilu.com/IECollection/

Wow!
Chapeau...

Hopefully is not: Sandboxie acquired by Invincea acquired by Sophos acquired by Microsoft.

All three installers are marked as clean @virustotal. https://www.virustotal.com/en/file/a93b60a62859acd6dd10b5a8034c77b2f597eb3088208f242bed146765460b42/analysis/1482433465/ https://www.virustotal.com/en/file/22a24d8c78b3bd073dcea4052fe7c21173470b0b4f2fb9890258220088d7b099/analysis/1482333644/ http...

Barb@Invincea wrote:Mr. X,

Any chance you can provide me with repro- steps?

Thank you,
Barb.-

No special repro- steps needed.
I just launched Chrome as usual and it started to hang. Even opening tabs in it.

FYI I've just installed a few moments ago 5.15.3 and it's back to normal.

All, We are still looking into this Chrome issue. We recommend installing Chrome outside SBIE and launching it Sandbox to avoid problems. Mr X., Can you provide more information regarding the problem that you are experiencing? (OS, AV version, any addons/toolbars, ...etc). Thank you, Barb.- Windows...

ssj100 wrote:Thanks for such quick feedback. Hopefully it can be fixed, although it seems like over the years, it's getting harder and harder for web browsers to be installed directly inside the sandbox.

Not only that. Even installing Chrome as usual, now in latest beta 5.15.8 is crashing a lot.

On Windows 8.1 x64 Experiencing crashes in Chrome 55.0.2883.87 m (64-bit). Terminate programs on SBIE control but Chrome remains active but "suspended" according to Process Explorer. SBIE control not displaying its gui. In Process Explorer an instance of Start.exe is "suspended" FWIW, everything I u...

Okay.
Syrinx managed to solve this problem of mine and he will explain in next post.
Honestly and fairly I'd love to see a person like him to give an excellent support to user here in the forums.

Thanks mate.

Still having same issue up to these days. Here's a RAM log:

http://pasted.co/dbc9715b
https://www.upload.ee/files/6274503/RAMlog.txt.html

@Sandboxie User
I agree with Curt. And maybe this sounds rude but I don't believe you. I don't think there was a sandbox escape at all... Until you prove otherwise of course.
You have to give all details needed to replicate your scenario, then we'll talk.

Does the process manage to violate the boundaries of the sandbox or just set itself up that sandboxie has trouble with process persistence and kill permissions? If it's the former, logging out should and restarting the computer would kill it. If it's a sandbox boundary violation, it's a real proble...

What exactly do you mean by fails to stop malware?
That SBIE couldn't stop/terminate the program or prevent from executing it in the first place?

It allows a default deny approach with new boxes [Global rules that close paths] so I don't have to re-add a ton of closed paths upon creation Exactly. This is the point of the whole thing. It's naturally logical to have global rules (templates) to apply for every existing and new created sandboxes...

I don't think you can do that. Once Sbie finds a match, it quits searching. You will have to copy your ClosedFilePath to each desired sandbox. Actually my friend syrinx nailed it again. It is possible Curt, indeed. You could make an exception. eg ClosedFilePath=!program.exe,%path% If you need more ...