Installing Browsers Directly Into SBIE [Updated 6/06]

[ssj100]

Same issue with Windows 10 64-bit. I suspect Chrome versions from 55 and above are no longer able to be run directly installed within the sandbox?

[Barb@Invincea]

We are able to reproduce this issue with Chrome 55 installed directly into SB.
We'll look into it.

Regards.-

[ssj100]

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.

[ssj100]

Will this be looked into before the next Sandboxie final release?

[Mr.X]

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.

[Barb@Invincea]

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.-

[Mr.X]

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 8.1 x64
No A/V whatsoever.
uBlock Origin, LastPass 4.1.34

[Barb@Invincea]

For Chrome 55 installed inside a Sandbox, please try the following: (Same steps can be used for Opera, but you will also have to set the "Sart section" to the Sandboxed location you selected to install it).

Sbie Ctrl --> View Files and folders, navigate to your Sandboxed Chrome installation
Right click on Chrome --> Create Desktop Shortcut
Go to your Desktop and right-click properties on the newly created Shortcut
Update the target to reflect the following: " --no-sandbox " at the end (no quotation marks)
This should be added after the quotation marks in the Target area, leaving 1 space
Update "Start in" section to reflect the actual installation path (for example C:\Sandbox\User\SboxName\drive\C\Program Files (x86)\Google\Chrome\Application)


Let us know if that works.

Regards,
Barb.-

[Tester100]

By the way, this is also related to this: http://forums.sandboxie.com/phpBB3/view ... 11&t=23754 - The Steam browser is based on Chromium 55 as well. It has problems launching its child process, just like Chrome. That means both are affected, and every other problem using Chrome 55 as their core web browser.

For the curious people, this also affects the old Sandboxie version 3.76, so it's not just because of the changes since Sandboxie 4. But of course there is only the hope for an update with the new version.

[ssj100]

For Chrome 55 installed inside a Sandbox, please try the following: (Same steps can be used for Opera, but you will also have to set the "Sart section" to the Sandboxed location you selected to install it).

Sbie Ctrl --> View Files and folders, navigate to your Sandboxed Chrome installation
Right click on Chrome --> Create Desktop Shortcut
Go to your Desktop and right-click properties on the newly created Shortcut
Update the target to reflect the following: " --no-sandbox " at the end (no quotation marks)
This should be added after the quotation marks in the Target area, leaving 1 space

Let us know if that works.

Regards,
Barb.-

Unable to get that to work. Have you actually tried it? I think adding " --no-sandbox" to the end of that shortcut (which is pointing to a sandboxed Chrome) confuses the address and Windows won't allow it - I can't even add that extra command line in the Target in the first place. Anyone else have any luck?

EDIT: okay it can work, but I don't think those steps you've described are accurate? Unless I'm mis-reading it. You basically have to add the " --no-sandbox" command to a real shortcut for Chrome.exe within the sandbox. Then you create a sandboxed Chrome shortcut to this shortcut. Sounds confusing? Well, then you probably shouldn't be installing Chrome directly into the sandbox haha.
Running Chrome without its associated sandbox is probably significantly reducing security (despite Sandboxie being excellent). And the warning also suggests that there could be stability issues. Doesn't sound ideal, but I'll bite for now haha.

[Barb@Invincea]

ssj100,

Thank you for your feedback.
I have added an extra step to make the process more clear.

Regards,
Barb.-

[ssj100]

ssj100,

Thank you for your feedback.
I have added an extra step to make the process more clear.

Regards,
Barb.-

Thanks. That extra step makes it work well. And it makes good sense too.

[JohnBox]

For Chrome 55 into SBIE there is currently no other way apart from --no-sandbox?

What are the dangers of installing Chrome locally and then running it with SBIE?

Would that mean that for updates Chrome would run un-sandboxed during the update and then I can run it locally and with SBIE again?

[Barb@Invincea]

JohnBox,

Currently, if you want to install Chrome inside Sandboxie, you will need to disable its own sandbox.

You can also install Chrome on your host (we usually recommend doing this instead of installing apps inside SBIE) and run it Sandboxed.
Whenever updates are available, run it un-sandboxed to apply them.

Regards,
Barb.-

[ssj100]

Is there any progress/update on whether this will/can be fixed?