4.13 Beta Available (Latest Version 4.13.7)

[vito2]

The 4.13.5 alphas were just an experiment that didn't work out. SbieDll.dll is unable to inject in many situations, which is not good.

The combined 32/64 installer contains the exact same Sbie binaries as the separate installers.

What AV are you using, vito2?

360 Total Security (http://360safe.com/totalsecurity.html). If there is a conflict I think it is a new one and with 4.13.5 beta. I tried this beta only about three hours and this was ice for browsers. I use regularly Norman & Kaspersky & mbam on-demand scanners and I think my pc is clean. Adwcleaner found something from old unused Firefox 25 profile.

I'm using latest Sandboxie alpha and found installer from inside my pc. So there is no need to publish it again or send it for me. I see this so that Sandboxie is one and only but there is a lot of Chrome variants to choose and avoid messages about failed SbieDll.dll injection.

I think Chrome 38 is the big problem now!

[Curt@invincea]

We are unable to reproduce any Chrome crashes with dropped rights. Thus far, no one can produce an actual DMP file showing a Chrome crash. Therefor, we are going to assume that Chrome 37 & 38 are now working under Sandboxie 4.13.5. Time to move on to other issues.

[warwagon]

You wouldn't want to remove the Windows version restriction from a test build so we can test it on Windows 10 would you?

[ayustand]

Does not support Windows 10

[henryg]

You wouldn't want to remove the Windows version restriction from a test build so we can test it on Windows 10 would you?

Ooh, please!!!!

[henryg]

First time in many a beta update/year that I have had any problems, but with beta 5 installed and using Firefox 33 (latest beta), running Adobe Flash (15.0.0.152) totally freezes the browser.

Reverted to 4.13.4 and Flash works fine.

[Stone]

Still having issues with fresh install of 4.13.5

Screenshot.jpg (20.99 KiB) Viewed 4395 times

System not letting me attach rar'd dmp file.

[xszaqw]

Hi,
This is an update of a post in January 2014:
I’m having problems starting applications in the sandbox.
My configuration is Windows 8.1 64bits, Sandboxie 4.13.5 64bits. I deleted the sandbox, uninstalled sandboxie et installed sandboxie version 4.13.5.
Applications fail when I try to run them in the sandbox with an error message like :
Failure of DLL initialization
Exception Processing Message 0xc0000142 Parameters
0x00007FFCB9426640 0x00007FFCB9426640
0x00007FFCB9426640 0x00007FFCB9426640
There is a second error message like :
The application failed to start correctly (0xc150003)

Any ideas ?

Thanks

[bo.elam]

....but with beta 5 installed and using Firefox 33 (latest beta), running Adobe Flash (15.0.0.152) totally freezes the browser.

You can try to workaround your Flash and 4.13.5 problem by disabling Flash protected mode.
http://kb.mozillazine.org/Flash#Disabli ... Flash_11.3

Bo

[henryg]

You can try to workaround your Flash and 4.13.5 problem by disabling Flash protected mode.
http://kb.mozillazine.org/Flash#Disabli ... Flash_11.3
Bo

Thanks Bo, but I think I'll sit out this iteration until they get it right. 4.13.4 works fine for me, and as I don't use Chrome I see little advantage in the point upgrade.

[Dun]

I left computer locked for a while and when came back saw whole Chrome window yellow

Has anyone experienced this and know a way to reproduce? Sandboxie control was minimized and when I bring it back on the top whole window was broken.

I've fixed this by uninstalling Bitdefenter Internet Security 2015. It has too much incompatibilities with software. Even adding Sandboxie processes to BIS active anti-virust control whitelist has not solved this.

Chrome crashes on 4.13.5 beta with dropped rights and gives an "Memory could not be read" error like this: http://forums.sandboxie.com/phpBB3/down ... .php?id=94 . Using 4.13.5 alpha there is a problem with "SandboxieDll.dll failed".
I finally find the way to get Chrome x64 and dropped rights working on Win7 x64. Just make clean install 4.13.5 beta, leave default configuration, close SB control and disable SB service then install 4.13.5 alpha on the top. I did that way few days ago and haven't seen Chrome crashes and "SandboxieDll.dll failed" errors. Adobe Flash Player 15,0,0,152 NPAPI installed inside Chrome sandbox also works.

[Page42]

@Curt
When will SBIE be compatible with the new MBAE 1.4?!
nix

I didn't see a response to this question about MBAE. Has it been addressed?

Per the MBAE product Support page...

Sandboxie may prevent MBAE from injecting its DLL into protected processes.

[Curt@invincea]

@Curt
When will SBIE be compatible with the new MBAE 1.4?!
nix

I didn't see a response to this question about MBAE. Has it been addressed?

Per the MBAE product Support page...

Sandboxie may prevent MBAE from injecting its DLL into protected processes.

I have been working with Pedro at Malwarebytes. Sbie does not prevent any app from injecting into a sandboxed app. As best I can tell, MBAE never even attempts to inject into a Sandboxied application for some reason. Pedro is looking into it.

[Page42]

I have been working with Pedro at Malwarebytes. Sbie does not prevent any app from injecting into a sandboxed app. As best I can tell, MBAE never even attempts to inject into a Sandboxied application for some reason. Pedro is looking into it.

TY, Curt!

[Dun]

Flash player installed in Firefox sandbox tries to write outside of sandbox even if dropped rights are enabled