Discussion in 'Sandboxie (SBIE Open Source) Plus & Classic' started by bo elam, Apr 22, 2020.
It seams that chrome fails on the CreateProcessW call not sure yet why though
Well, let me take this back. I think I found a workaround that makes chrome v86 work with SBIE.
When I tried this before, I went to the quicklaunch icon in the SBIE folder. The target had the default browser line in there, and when I put the switch in it did not seem to work. Replacing that default browser with the chrome.exe --no-sandbox line does work. The browser launches and gives me a warning about the switch, and I can see it's sandboxed in SBIE due to the window border.
Chrome 86.x works for me with --no-sandbox switch - #472
Thing is we need Sandboxie to work with all Chromium browsers, and to work out out the box.
No changing targets etc. It needs to work like it did with the Chrome 85 branch.
Edge and Vivaldi will be on 86 branch soon.
Yeah, I ended up doing exactly what you posted. For some reason my shortcut from SBIE quick launch had the default browser tag in there instead of the actual chrome.exe and that did not work. Thanks for the info, all is well now. I would just guess Google will not ever fix this issue based on their stellar history of listening to users.
Simple things in chrome make me crazy, like new tab URL's or focus on them, or even the color of visited sites which are hardly distinguishable from the other. You need extensions to make these things work which are memory intensive relatively speaking.
I'm not sure how they exactly managed to break it, inside CreateProcessAsUserW it fails to execute NtCreateProcess that one returns an access_denided error.
I looked through the sandbox lib in the two chrome builds and don't see any changes that would obviously break that :/
By the way, this also works for Vivaldi. Same method as for Chrome mentioned above.
(In case anyone is unsure how to do it)
Go into Program files...Sandboxie and open.
Find Quick Launch.
Right click on it and select create shortcut.
It will say 'cannot do that here' so select Desktop.
Right click on Sbie Quick Launch icon on desktop and select Properties.
Where it says Target replace the words AFTER
"C:\Program Files\Sandboxie\Start.exe" with vivaldi.exe --no-sandbox"
Apply and then OK.
Big Vivaldi user here. Really lots of thanks @stapp for this!
Yes, I was not promoting "--no-sandbox" as workaround.
I was simply responding to #467.
Yes, we need Sandboxie to work like it did with Chrome 85.x.
Regards w Respect
That got Brave working as well.
I just updated Edge to Version 86.0.622.38. The workaround works.
The target I used:
"C:\Program Files\Sandboxie\Start.exe" msedge.exe --no-sandbox"
Thanks to Stapp, bjm, etc.
Appreciate you looking at this issue, David.
Works well here also. thanks Bo.
@stapp, Thankyou as well.
Great. To open Edge in a sandbox other than the DefaultBox, you can add this parameter (/box:Edge) to the target:
"C:\Program Files\Sandboxie\Start.exe" /box:Edge msedge.exe --no-sandbox"
You can change the name of box, to whatever is the name of your dedicated Edge sandbox.
Wolfrun, you can also create a sandboxed shortcut for Edge (Via Windows shell integration) to run in your dedicated Edge sandbox. Change the Target to the one as written in post above. And move the shortcut icon to the taskbar. I just did that, to get rid of the Quick launch icon at the Desktop and to have the shortcut show the Edge icon. Doing this also leaves my Desktop and Taskbar exactly as before the update.
Thanks Bo. Works well. Will be good as my secondary browser. FF will still be the main browser for me.
Target: "C:\Program Files\Sandboxie\Start.exe" /box:Edge msedge.exe --no-sandbox"
Target: "C:\Program Files\Sandboxie\Start.exe" /box:Chrome chrome.exe --no-sandbox"
Still hoping we'll get Sandboxie to work like before 86.x
Thanks > stapp, bo elam, g17, et al
Thanks for getting Edge working again with Sandboxie.
@stapp, thank you very much for your workaround. I can now continue to use Vivaldi. Much appreciated!
We still await a full solution, because the workaround seems to restrict us to the default sandbox. In fact, we have now experienced how fragile our reliance on Sandboxie is. Go the forks!
A tiny detail --- can the final " in your code can be omitted? Leaving it out causes no problems on my system (64-bit Windows 10 Pro). It was puzzling me, and I noticed that others were copying it just as I had done. But there may be some other reason for it.
Not really my workaround, other Sandboxie users above came up with the Chrome one, I just applied it to Vivaldi
Regarding it working only on the default box please read here and substitute another box name you also have and want to use.
We await feedback from the report I entered at Chromium bug reports.
@stapp: Thanks very much for that. It works perfectly, so I now have all my sandboxes back. Apologies for missing the detail.
At what exact chrome build number it stopt working?
David I first noticed it here and posted it straight away so that should be the exact Chrome build number ?
On github someone wrote 85.?? and if i look through the chrome versions in the chromium repo there are many more, more then what gets released as final builds to the public.
I can only go on what the release notes said for that build (scroll down for changelog.)
And something here you will probably understand more than I do
I know new Edge was working with Sbie on Chromium build 85.0.5641.51 and Vivaldi worked on Build 85.
Separate names with a comma.