Sandboxie Plus 0.9.3

~ regarding Classic 5.51.5
Curious, had you check'd one or both.

 

Thanks, I have the second box checked (as don't need it starting with Windows).

EDIT: Also I use shortcuts to the browsers with this preceding the path to the program:
"C:\Program Files\Sandboxie\Start.exe" [browser path here]

I do that instead of using the internal SBIE settings to "always run sandboxed" because I don't always run them in the sandbox - like if I want to install add-ons or whatever - do things I want to stick. (Browsers are installed outside the sandbox and sb is configured to empty each time the browser is closed.)

 

Okay. I don't use Start Sandboxie Control nor Sandboxie shortcuts.
That said: I do observe as you report regarding Plus UI + Start UI when a sandbox process is started.

 

I assumed I had to have one of those checked. I tried unchecking it before (none checked) and SBIE didn't launch at all... but that could be the other issue. Will try unchecking, rebooting, and starting an instance of a boxed browser to see if at least the window doesn't come up. Will report back...

EDIT... Yes, without that checked the GUI window doesn't open, but neither does SBIE launch. I have to start Sandman manually (which opens the same window... ).... so I guess in Classic the initial process that has to run (but not open a window) is SBIECtrl. exe and in Plus it's Sandman. Would just like SBIE to launch without having to manually start a process or click to close a window. I would revert to an old version but they don't work with Brave.

 

Just sharing. Just me.
Plus install. SandMan & SbieCtrl pin'd to taskbar -> call SbieCtrl from taskbar -> call forced browser.
Classic install. SbieCtrl pin'd to taskbar -> call SbieCtrl from taskbar -> call forced browser.

 

@bjm Thanks for the suggestion. For me, I can't have anything pinned to the taskbar. Too little real estate there and need more than I have as it is for when I'm running three or four open programs and switching between them.

 

I'm sorry I crashed this thread about SBIE-Plus and the new features it has. I didn't realize it until after I posted. (Was reading between multiple tabs / threads on SBIE and picked the wrong tab.)

I've resolved my issues as best as I can for now, so for any readers who might have read my posts and are having the same issue with W764 and Classic (or Plus) not launching SbieCtrl (or Sandman), and so SBIE failing to launch, this is what I did...

Although I don't prefer to launch SBIE at boot, my main concern was not wanting to have to close the GUI window. So created a shortcut to sbiectrl.exe with the flag /background and stuck it in the Startup folder. ("C:\Program Files\Sandboxie\SbieCtrl.exe" /background) Now it starts already minimized to the system tray. So no window to close, and of course SBIE works now that sbiectrl is getting launched.

As for Brave, in my case SBIE (Classic or Plus) will not work without the --no-sandbox flag (and hardware acceleration disabled). But I did find another switch that at least keeps Brave from showing: 'warning, no-sandbox is an unauthorized flag and may cause security issues...' (gist).
The flag is --test-type (probably everyone here already knew that). So it's:
"[path to Brave]" --no-sandbox --test-type

Maybe a future iteration of SBIE will work on W764 the way it sounds like it's working on W10 machines. Meantime I'm very grateful to David for keeping SBIE alive and am happy to have it, finessing or no.