Sandboxie-Plus v1.0.11

He didn't give it up, he sold it.

Bo

 

same issue like other user experienced when running software in the box and updates arre not handled - it mostly fails. either you configure openpath exclusions or you stop running discord in the box.

 

he now works as a sw developer for a private company in haifa.

 

Hi Bo
Yes, I know. Just incorrect use of language. Do you know what he did after?

 

As previously stated and verbatim per @imdb: "he now works as a sw developer for a private company in haifa." From what I gleaned, Haifa is the 3rd largest city in Israel. Good luck in finding further specifics re: Ronen Tzuk.

 

I have a Windows 10 Pro 64 bit PC. I just switched from Sandboxie Classic to Sandboxie-Plus 1.0.11. I performed a clean uninstall of Sandboxie Classic and rebooted prior to the install of Sandoxie-Plus 1.0.11. I also rebooted after installing Sandboxie-Plus 1.0.11.

Note: This is a different Windows 10 PC from the one that I was discussing here:

https://www.wilderssecurity.com/threads/sandboxie-plus-1-0-10.443919/page-3

I am having an issue: After successfully running MS Edge in the Default Sandbox (Hardening enabled) Edge does not stop running in the Default Sandbox when I close Edge. I do briefly see some sort of attempt to stop Edge but it seems to regenerate. I have to manually terminate the running processes.

How can I fix this issue?

Thanks in Advance.

 

Out of curiosity, what would "Stop Programs" under Default Box options do re: terminating the browser processes? Does anyone use this feature? By the way, I always have the box set to auto-delete and never have this lingering problem.

Spoiler

 

I do not "Add" Leader/Lingering with my browser sbox/s.

Me Too

 

Make sure you have "Startup Boost" disabled in Edge settings (found in "System & Performance" section). Start up boost means Edge never fully shuts down but kind of hibernates. If that doesn't help make sure that you disable "Continue running background extensions and apps when Microsoft Edge is closed". I suspect your problem lies with Startup Boost being enabled though - they made that on by default when introduced some months ago. It interferes with other programmes like CCleaner too.

 

Thank you. That fixed the problem. I had to reboot for the setting change to take effect.

The PC was a refurbished PC. I guess that the refurbish company thought that it was best to have MS Edge startup boost turned on.

My other Windows 10 Pro 64 bit PC had MS Edge startup boost turned off by default (PC was new build with a Windows 10 Pro 64 bit OEM DVD.). That is why MS Edge was working OK with the Sandbox on that PC.

 

Interesting, thanks.

 

for MS Edge i have disabled here all startup processes (with sysinternals autoruns) and edge wont show up until used. i dont use edge as i use chromium for some special purpose beside firefox.

 

Interesting....well, the fewer settings you would use the better, it seems. Hopefully, one doesn't have to re-enable this setting in the future. I recall Leader/Lingering programs were present for the longest in Sandboxie. Not sure what use cases (except some legacy software) would benefit from them now. Anyone? Just curious.

 

I see this settings like this. The greater the amount of programs that are allowed to run in a particular sandbox, the greater the chances are you might need using Lingering or Leader settings. So, for example, if in your Firefox sandbox you only allow firefox.exe to run, the chances you ll need using Program stop settings are about 0. On the other hand, if you also run in the Firefox sandbox a PDF Reader and you open Word and Excel files while browsing and they open in the Firefox sandbox, the chances you ll need using this settings become slightly greater than 0. If additionally you also run a video download program, etc, the chances grow a bit more. But regardless of what we run, chances of needing this settings are always low.

Bo

 

That makes a lot of sense, then. Thanks bo elam.

Yes, I never felt the need for those two settings, esp. in Plus. As you said, it's only Firefox and nothing extra.

 

Maybe, Show Templates offers some insight.
I do not "Add" Leader/Lingering with my browser sbox/s.

Spoiler: Stop Behaviour pic

https://github.com/sandboxie-plus/sandboxie-docs/blob/main/Content/AllPages.md

 

I always had a little bit different approach to these settings and already a long time ago I determined firefox.exe as "leader process": I realized that in order to start/use Firefox in a sandbox I had to allow other exe.files too (either to allow their start or - in some rare cases - their internet access too). These were in the past (and possibly still are) files like plugin-container.exe, dllhost.exe, ctfmon.exe etc. According with the terminology of Sandboxie such files are processes (not necessarily programs, I assume).

As quoted above by bjm_ , if a leader process is defined (= in my case firefox.exe), "all others are treated as lingering processes". And "lingering programs" (= processes??) "will be automatically terminated if they are still running after all the other processes have been terminated".

To my mind in these descriptions seems to be a certain confusion between the terms "programs" and "processes". It's interesting that in the German user interface the sentence "If leader processes are defined, all others are ..." is translated as "Falls primäre Programme/Prozesse definiert wurden, werden alle anderen ...":



--> The German interface refers to "programs/processes" which seems to me more clear and logical than the mere "processes" in the English user interface.

Anyway, in order to be sure that all the processes like plugin-container.exe etc. - which are connected with (my use of) Firefox - are terminated whenever I terminate the firefox.exe (typically by closing my browser), I defined the firefox.exe as leader process/program.

 

@Peter 123. You don't see this settings differently than how I do. When I wrote, the more programs you allow to run, the greater the chances you ll have a need to use this settings, in the word programs, processes are included.

By the way, earlier, I used Firefox as an example. But this applies to any dedicated sandbox. Like if you are using a dedicated sandbox for an EMail client, if you only allow to run the processes that come with the EMail program, the chances of you needing to use Lingering or Leader settings are lesser than if you also allow to run Chrome, Firefox, a PDF Reader, Word and Excel in the EMail sandbox.

Bo

 

@bo elam. O.k. Let's express it in a little different way:

Is my following assumption correct?

If someone uses a (dedicated) sandbox e.g. for running Firefox (as only program), it is (nevertheless) useful to define the firefox.exe as leader process/program, in case that he/she wants to be completely sure that after terminating Firefox no other processes remain running in the sandbox (like plugin-container.exe etc.).

 

Perhaps a practical example might help. I autodelete my browser-box like many of us do. Now whether you post something on social media or write a contribution to a forum or enter a complaint into the contact-form on a web-shop-site - as things happen that input-mask/window will sometimes close down inadvertently - and all the text you have entered, possibly an elaborate statement, is gone for good. To avoid such cumbersome loss I've switched to composing all of my statements in an editor-program aeons ago. So far, so good as the editor will usually run outside of the sandbox. But I've also set the OS to handle "txt"- or "ini"-files automatically and primarily by this editor. So if the browser encounters/downloads a "txt"-file further processing of that might trigger an instance of the editor running sandboxed, too. When I then used this editor to input long text-statements and for some reason the browser would crash or I closed it down without thinking - now guess what: the editor would close as well and all input was gone again without the editor asking to save it first.

Since one of those early mishaps I've declared the editor as a leader-program in the browser-box, too. So if the browser closes the box will not - as long as the editor is still open and able to offer saving its input to a file. Similar things might be true for a pdf-editor still containing unsaved documents edited in there.

 

In order to avoid what I have marked with bold letters: Wouldn't it be also an option to forbid the sandboxed running of the editor (by adding its exe.file to the start restrictions of the sandbox)?