Sandboxie-Plus v1.11.3, v1.11.4

No, and this setting has indeed been the culprit!

Still that all seems quite strange as I usually don't mess around with GlobalSettings except when I precisely know what I'm going to do in there. I've always used ForcedFolders and templates forcing several browsers to always start sandboxed within individual/default Sandbox-options - and this alone HAS always BEEN SUFFICIENT at least until v.1.09 or even v.1.10.x.

That whole phenomenon of Sandman not autostarting after an upgrade-procedure must have somehow been introduced with v.1.11.x and I have complained about it ever since not knowing about the true culprit. Anyhow I can state with most certainly that I myself have NEVER purposefully unchecked that option in GlobalSettings as TBH until of today (and your exact description of its location) I haven't even been aware of its existence.

 

@stapp @henryg1

Do you get this error in a clean sandbox?

 

That's odd on my win 10 test VM 1.11.4 starts explorer just fine.
Did explorer worked with 1.11.3 fine?

 

@stapp

Does it crash on all sandbox types?

 

You cannot run explorer.exe directly. You need to run it using 'explorer.exe /e, PATH'. issue#362

 

The second issue (color box grayed out in Box options in sandman UI) is still present:
https://www.wilderssecurity.com/threads/sandboxie-plus-v1-11-2.452365/page-3#post-3163958
No other problems (so far) on my Win7SP1x64 portable install of v1.11.4.

 

For me, both issues are solved (on my Win7 64Bit): The start menu shows the menu entries like it should be, and the colour selector shows the colour on the whole button. Thanks very much for solving these issues!

 

Thanks for confirming that it's ok for you. I'll poke around my settings and
let @DavidXanatos focus on the features to come in the next builds

EDIT (Solved): Checking the following setting is the cause. When I uncheck it, the colors show up
Options>Global Settings>Interface Config>User Interface>Make Box Icons Match the Border Color

 

[Edit] Quick recovery not working for me. Looked at sandboxie.ini and autorecover=y.

No difference with new install/ini & Default Box. BUT I then copied in an old ini file (from January 23) and Quick Recovery is now working. Weird!

 

Perhaps you should check the same setting as @busy has suggested to me.

In my case upon upgrading I must have lost that setting somehow on its own (as I NEVER would have unchecked that box manually myself) - and ever since when starting a (forced) browser after having exited Sandboxie beforehand - it would only start "half-sandboxed" with no colred border, no recovery, neither "auto" nor "instant" and no "emergency-shutdown" via hotkey.

So for me the "bottom-line-question" remains: what good is a checkbox for that would let the user disable the autostart of Sandman together with each new box - when without it running that Sandbox will lose essential parts of its functionality?

 

@henryg1

For File Recovery to work, the following conditions must be met:

1. SandMan.exe must be running.
2. The folder where the files are stored must be set as the File Recovery folder. (e.g. RecoverFolder=X:\SomeFolder)
   
3. The saved file must not match any of the set exclusions. (e.g. AutoRecoverIgnore=.bak or Template=AutoRecoverIgnore)
   
4. The same file must not already be in the sandbox.

 

Yep, all of those were ok. It's ok now once I used an old ini file, but some setting must have got corrupted although how with a clean install that I tried... Oh well.

And thank you @busy and @algol1

 

Me too.

 

Do you still have a copy of that presumably corrupt ini-file? I've made it a custom to keep a copy of each file under investigation for corrupt behavior.

If so it would now be interesting to start a file-comparison between the old - but working - ini-file and the one that did result in the problems described earlier to now identify the exact entry that has caused all that trouble.

 

fwiw ~ my preference

 

With both boxes unchecked - how do you then start a working sandbox - that is one with (for example) yellow border, auto recovery (either immediate or auto on close-down) and emergency-termination via hotkey?

 

Sorry, I overwrote it from the backup.

I do have another problem as I no longer see the old quick recovery window but one below where "Recover & Explore" is no longer an option - bad new for me!

 

SandMan pinned to taskbar (left side)...click+x close = SandMan in systray (right side). I have [shortcuts] for browsers & Explorer. My habit from Sandboxie days was SbieCtrl pinned to taskbar (left side).
So, with Sandboxie-Plus. I've continued my habit. And my sbox's are few n' basic.

 

its strange i did not change anythign on the recovery things, anyone else with that issue?

 

@henryg1 You probably don't have the Show recoverable files as notifications option enabled.
(Sandboxie Plus > Options > General Config > Notifications)

 

Just got a bug report about that sone seams KB5031354 causes it with red boxes (option:
"Use the original token only for approved NT system calls"), should be easy enough to fix.