Sandboxie Support

Curt@invincea wrote:Beta 4.13.6 has been released with several Chrome fixes. I do not know if this fixes the dropped rights problem, as we are still unable to reproduce this.

Many thanks for this 4.13.6 Beta release and now I am finally able to run my Opera Beta 25 and Opera Developer 26 versions in Sandboxie !

Info: My "Drop Rights" box is left blank and unticked.

Anybody else is getting SBIE2303 unable to intercept SetSecurityInfo (1) and SBIE2318 ntmarta initialization failed at chrome 38.0.2125.101 m (64-bit) startup with the 4.13.6?

Dun wrote:Flash freezes using FF 32.0.3 on 4.13.6...

The same problem.
Win 7 SP1 x64.

Curt@invincea wrote:This is getting to be a really tough crowd.

Only telling you the way it is.

Even though this is a beta, denying it is breaking Flash when it clearly is in FF is not too sensible. It wasn't broken in .4 so one assumes you should be able to trace the changes.

SRWare Iron 37.0.2000.0 (Chrome Clone), SBIE 4.13.6 on board.

SE7EN@ If you have this checkbox ticked then untick it http://www.sandboxie.com/index.php?Rest ... tings#drop

I've send you PM

@Dun unchecking doesn't work, Iron still crashes when I open some sites

@Curt

Installed the latest beta 4.13.6, been using SRware Iron and Palemoon browsers. I don't experience any problem regarding Iron, but in the case of Palemoon this comes up by just going to Youtube. Flash 15 Plugin is installed think this is a version for chrome, but this error doesn't show in 4.13.4 and I can watch videos in both browsers w/ no problem except the occasional GUI_proxy something in Iron.

Setting:
Drop rights ticked...
File Access>Read-Only Access>C:\Program Files and Windows...

Nix

Bug reports for the 4.13.6. All of these are tested on Windows 7 x64 SP1

- Firefox 32.0.3 with Flash 15

Firefox hangs/freeze/locks up when Flash is being used on a page (see any Youtube video with Flash for example). This also happen in 4.13.5 but there's no problem in 4.13.4.

Workaround: Disabling Flash ProtectedMode works but i believe this is not the proper way to do it*.

- Chrome 64-bit Stable and Dev (38.0.2125.101 m (64-bit) and 40):

1. When running chrome this message appear:

SBIE2303 Could not hook SetSecurityInfo (1)
SBIE2318 DLL initialization failed for 'ntmarta.dll'

This does not happen on chrome 32-bit stable and dev. Also this does not happen on 4.13.5 for both 32 and 64-bit chrome.

2. Hardware acceleration still not available

The easiest way to test whether Hardware Acceleration is enabled and running please visit this page http://ie.microsoft.com/testdrive/performance/fishbowl/ .

As you can see the FPS is really low because hardware acceleration is not running. Try running that page in another browser (tested on FX32,IE11 and also chrome with workaround) and you'll see big difference in FPS.

Workaround: Use chrome parameter to disable chrome sandbox feature when running chrome, but i believe this is also not the proper way to do it*.

* Because if there's an exploit for chrome/flash it'll cause problem in that sandbox which is bad if each sandbox container is being used for portability/portable use (i.e sandbox is not deleted after each use).

Dun wrote:Anybody else is getting SBIE2303 unable to intercept SetSecurityInfo (1) and SBIE2318 ntmarta initialization failed at chrome 38.0.2125.101 m (64-bit) startup with the 4.13.6?

Yes me.

I've gone back to 4.13.5 for now.

Curt@invincea wrote:Beta 4.13.6 has been released with several Chrome fixes.

Working well now for me on Windows 8.1.1 x64 with Chome 38 64-bit. Thanks. On windows 7 x64, I see the same reported error messages. However, hardware acceleration hits 60 for me using Chrome 38 or IE 11.

bdg2 wrote:

Dun wrote:Anybody else is getting SBIE2303 unable to intercept SetSecurityInfo (1) and SBIE2318 ntmarta initialization failed at chrome 38.0.2125.101 m (64-bit) startup with the 4.13.6?

Yes me.

I've gone back to 4.13.5 for now.

You can ignore this error. It will be fixed in 4.13.7.

henryg wrote:

Curt@invincea wrote:This is getting to be a really tough crowd.

Only telling you the way it is.

Even though this is a beta, denying it is breaking Flash when it clearly is in FF is not too sensible. It wasn't broken in .4 so one assumes you should be able to trace the changes.

The problem with Flash standalone is not being denied, but has been fixed in 4.13.7. As a side note, it looks like the Flash standalone is on its way to deprecation (replaced by Flash add-ons).

Curt@invincea wrote: The problem with Flash standalone is not being denied, but has been fixed in 4.13.7. As a side note, it looks like the Flash standalone is on its way to deprecation (replaced by Flash add-ons).

Both are good news AFAIAC.

And what about this problem?
http://forums.sandboxie.com/phpBB3/view ... 11&t=19688