Sandboxie-Plus v1.11.3, v1.11.4

Kind of a catch-22-situation, isn't it? The updater will be fixed in the upcoming release - which will never get installed in the first place as long as the updater isn't working properly.

 

Well not quite new versions with new installers are installed just fine the issue affects only version updates a,b,c, etc...

 

Just to clarify can I consider this resolved after you found the offending setting?

Or is there still a need to change the installer to when the "start the Sandman-UI (checkbox)" on an upgrade instalation is checked it will start the UI in tray only?

 

You are correct in assuming that with the offending setting identified and corrected the installation now works as customary and the browser will start sandboxed and with full functionality.

However - as it stands now - a few minor things still remain (as they always were) that may leave a slightly bitter aftertaste behind:

1. I always had the "offending option" (start UI when a sandboxed process is started) deliberately checked "on" and it is still an open question how the hell this might have been reset automatically to "unchecked" all by itself (presumably during some recent upgrade process). I most certainly didn't purposefully change that myself.

2. If that checkbox can be unchecked, regardless of whether intentional or not, and as a consequence (without Sandman autostarted together with the browser) the sandboxed browser will no longer work correctly (as described e.g. will come up without its colored border, the "emergency-shutdown-hotkey" no longer working and no recovery for downloads offered at all - neither immediate nor together at the end of the browser-session) then the question arises what sense such an options-setting would make in the first place if one of the two possible settings would leave a crippled sandboxed browser/process behind as a consequence?

3. When upgrading from a prior version (and not opening Sandboxie-plus for the very first time) I still hold that I would not like to open Sandman initially as a full window but would rather prefer it to go directly to the SysTray. That is why I've made it a custom to uncheck the option to open Sandman in that last installer-window.

But then Sandman will always somehow auto-close-down some time (30 sec or so) after the installation has finished. Now - and only with the "start UI when a sandboxed process is started"-option properly set - upon the next browser/process-start Sandman will autostart to SysTray together with that process and everything is fine again.

But TBH I've never quite understood why Sandman would first auto-close-down from the SysTray to begin with (only to come up again at first browser-start). So from my perspective it would still be highly desirable that Sandman would go primarily to the SysTray upon upgrade-installation - and stay there open. As I see it there wouldn't even be an installer-option (to start Sandman after installation) required at all - it should simply auto-start to SysTray. Or if that option were indeed necessary for some purpose I don't see right now - then at least it should be preceded by a default-option to auto-start to SysTray in case of an upgrade-installation. Just my 2 cents.

 

I have no idea what happened to your setting that should not be changed on its own,
did anyone else experienced that behavior?

 

Of course I cannot speak for other members but IIRC our colleague @henryg1 has mentioned to having observed behavior like that:
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-11-3-v1-11-4.452487/page-2#post-3166344

Addendum: I think that phenomenon might have been introduced for the first time when upgrading to v.1.11.2 - without me knowing at that time which (if any) changed setting might have caused the problem:
https://www.wilderssecurity.com/posts/3162078/

 

Hi David. A few days ago I updated Firefox (from 115.0.3) to 118.0.2. After doing so I noticed when I run CCleaner, it finds what you see below:



This is something that I never seen before. places.sqlite have to do with Bookmarks. Personally, this doesn't bother me but since this is something that I have never seen before, I am reporting it here.

I was using SBIE 5,63.4. I have updated to 5.66.4. And get the same. Probably, Firefox changed something between 115.0.3 and 118.0.2. I am using an old version of CCleaner, I don't know if new versions flag what the picture shows but probably does.

Greetings

Bo

 

Application name with error: SbieSvc.exe, version: 5.66.4.0, timestamp: 0x651ee53a
Module name with error: ntdll.dll, version: 10.0.19041.3636, timestamp: 0x9b64aa6f
Exception code: 0xc0000005
Error rate: 0x000000000002633c
Id of process with error: 0x351c
Application start time with error: 0x01da18696c2b23c3
Path to application with error: C:/program Files Sandboxie-Plus SandboxieSvc.exe
Path to module with error: C:WINDOWSYSTEM32ndtdll.dll

 

@stapp

Could be. Yet another log, now with both Sandboxie and Hitman.Pro Alert.

Application name with error: SbieSvc.exe, version: 5.66.4.0, timestamp: 0x651ee50f
Module name with error: hmpalert.dll, version: 3.8.24.957, timestamp: 0x644121f4
Exception code: 0xc00000fd
Error rate: 0x0002512d
Id of process with error: 0x1a0c
Application start time with error: 0x01da036b6bd5b516
Path to application with error: C:\program filesandboxie-plus.exe
Path to module with error: C:WindowsSystem32hmpalert.dll

 

each [Edge] launch - Troubleshooting submitted

1.11.4

 

When did the issue start? does it happen only with edge but no other apps?
Do you start edge with run sandboxed or a sbie link, or by forcing it?

 

Geez, I slept since. Just one day recently there was SBIE2326.
Happens with [Edge] [Chrome] [Firefox] discrete sbox's. Not forced. Plus created discrete [browser] shortcuts.
Thanks
Edit: SBIE2326 does not happen with Run Sandboxed at browser shortcuts with DefaultBox.
Edit: so, is SBIE 2326 just me?

 

Well, whatever was causal. I'm not seeing SBIE2326 with 1.12.3.