Sandboxie-Plus v1.4.0, v1.4.1, v1.4.2

This is a unsigned test build (that is the driver is signed but not the installers), it improves the SandMan UI a lot and adds various new UX oriented features, it also makes the sandman code base Qt6 compatible, that said, the build currently uses still Qt5, a switch to Qt6 is planned for later. With regard to Qt6's no longer present windows 7 support, this won't be an issue as a custom build of Qt6's base components will be used which are windows 7 compatible.

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.4.2
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.4.1
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.4.0


Changelog

[1.4.2 / 5.59.2] - 2022-10-10


Added

• added tooltips to resource access modes #2300
• added UI option to control ApplyElevateCreateProcessFix #2302
• added message 2226 issued when a process may need 'ApplyElevateCreateProcessFix=y'

Changed

• Moved Restrictions tab from the new Security page back to the General page

Fixed

• fixed wrong button captions in the breakout process page
• fixed issue with saving box recovery options
• fixed the display problem of Sandman #2306 (thanks okrc)
• fixed theme not auto changing #2307
• fixed issue with saving sandman window state on windows shutdown
• fixed miscellaneous minor issues #2301
• fixed issue with MSEdge introduced in 106.x #2325
• fixed vivaldi hooking issue, UseVivaldiWorkaround is no longer needed #1783
• fixed issues with misc advanced options page #2315

[1.4.1 / 5.59.1] - 2022-10-05
Added

• 
  
  
  • addes dark title bar support for Windows 11 #2299

Changed

• 
  
  
  • In sbie 5.28 and later WinInetCache is open, this breks IE's source view, hence it can now be disabled with 'CloseWinInetCache=y'

Fixed

• 
  
  
  • fixed WarnProcess and WarnFolder not working with certain configurations

[1.4.0 / 5.59.0] - 2022-09-30
Added

• added integrated run from start menu #1836
• added start menu enumeration #1570
• added UI for breakout processes #1904
• added option to customize double-click action per sandbox
• added new advanced tab in the advanced tab allowing to configure specific processes and other advanced options
• added "SeparateUserFolders=y" and "SandboxieLogon=y" to the sandbox options dialog
• added icons to option section labels

Changed

• prepared for Qt 6.3.1
• restructured the general settings page
• restructured the sandbox options page, added a new tab and moved some of the advanced options there

Fixed

• fixed menu bar issue in Plus UI #2280 (thanks okrc)

 

Did you look into the problem that I reported with Media Player Classic HC not being able to run video files into the default sandbox? I have this problem on Win 10 1909 with Sandboxie Plus v1.3.2 but it also didn't work on older versions, not sure what's going on.

 

Is it ok to do an over-the-top install of v1.4.0 from v1.3.5 in portable mode?
I have been doing this for all older to newer versions with no problems,
but wanted to be sure for this "new" build. Thank you @DavidXanatos

 

yea should work

 

I guess I don't understand. You're using an old OS and expecting support for it from a one-person team? If I remember right, there were users who posted about everything working fine, so the issue is most likely in your config.

 

Indeed it does!! Thanks

 

So as its customary for me there is a lot in the change-log and no documentation, so let me try to improve on that a bit:

• added integrated run from start menu #1836
• added start menu enumeration #1570

What this function does is it scans each time a box is closed (meaning last process terminated) the boxes start menu/desktop locations for shortcuts.
This has to be enabled here:



this gives you something like this:



So instead of the menu option which opens the old picker using start.exe, here the boxed programs are all integrated into a sub menu.
You still have the option to open the old picker using the (Host) Start Menu command.




What you can also do is you can enable start menu integration, to add all your boxed installations to your host start menu



here you have 2 options the first will result in somethign like this, if you select as sub group:




and this if you select full integration:




So in the first case everything is a sub group of your sandboxie folder, in the second case everythign is integrated top level.
Also please note that to get such a nice functional start menu on any modern windows you need one of the folowing 3rd party offerings
https://github.com/Open-Shell/Open-Shell-Menu
https://www.startallback.com/
Start11

• added UI for breakout processes #1904

• added option to customize double-click action per sandbox

This option allows you to define a custom double click action for any of your sandboxes, default is open box options, but you can also pick, recvoery, or run dialog, or any entry from your "Run Menu" list to start any particular application you like

• added new advanced tab in the advanced tab allowing to configure specific processes and other advanced options

This tab ended up being called Miscellaneous it allows to configure options without having to remember their name or what values they take, just clock on Add option and pick one from the drop down list, the list editor will know if to allow you specifying a process or not and if it is a boolean or plaintext option.
All relevant options which did not got their own proper setting should be represented here, although I might have forgot one or two.

• added "SeparateUserFolders=y" and "SandboxieLogon=y" to the sandbox options dialog

They are located at General -> Files and Security -> Advanced pages respectively, and allow to overwrite a global preset, also the tool tips tell you what value is default and global.

• added icons to option section labels

As you have seen in the previous images already the bold labels on the option pages now also feature a nice icon

• restructured the general settings page
• restructured the sandbox options page, added a new tab and moved some of the advanced options there

As you may have noticed some options from the general page were moved on the new Security page as well as a few advanced options making the advanced tab something truly only for advanced purposes.

Further more there is a new structure available as shown in the following image



It combines various process related pages all on one main tab, and moves the recovery stuff onto the general tab.

You can access this view enabling "Use new config dialog layout" in the global "Interface config" page.

You can also force the opposite view to whatever is set by holding down ALT when opening the box options

I would have posted more images but there is a per post limit LOL

• 
  
  
  
  

 

Haha, ok well I'll wait for the rest, then.

Anyway, 1.4.0 opens Firefox much more cleanly than 1.3.5---there Firefox was opening in "chunks" if that makes any sense. Here, it opens fully intact and ready to go.

Had to get this build past SmartScreen but is expected. For just a simple use scene like mine (boxing Friefox only). it continues to be a good layer of security--don't have to mess with the .ini or anything.

 

This is funny....
because 1.3.5 and 1.4.0 have the exact same core components except for the changed version number and missing signature. LOL

 

Sandbox Config > Sandbox default

Code:

Sandbox file system root: \??\%SystemDrive%\Sandbox\%USER%\%SANDBOX%
Sandbox registry root: \REGISTRY\USER\Sandbox_%USER%_%SANDBOX%
Sandbox ipc root: \Sandbox\%USER%\%SANDBOX%\Session_%SESSION%

When I change it to

Code:

Sandbox file system root: R:\Container\%SANDBOX%

The other two settings remain the same.

Do I need to edit them manually or leave them as they are?

 

you can leave the others unchanged

 

I don't see how using an old version of Windows should interfere with basic functionality of Sandboxie. This stuff has always worked in older SBIE Classic versions and since I switched to SBIE Plus it's all of a sudden broken. This tells me that something is broken in SBIE, no surprise if you see how many changes David Xanatos has made. I guess this was Bo Elam's concern, that the more you keep tweaking the code, the bigger the chance that some things might eventually break.

 

BTW, I haven't tested a sandboxed Vivaldi yet, I know you had some problems with it, but I decided not to use SBIE for browser protection anymore because of certain troubles that it caused on my Win 8.1 desktop. For some reason I couldn't upgrade Vivaldi anymore, perhaps it was because of sandbox corruption, who knows. This was with the old Sandboxie made by Sophos. But to clarify, I do have faith in David Xanatos, I believe he does know what he's doing and has a good understanding of the innerworkings of Sandboxie.

 

Right. But Classic and the Plus versions are two different products at this point. You shouldn't expect them to be interchangeable without some tweaking.

More likely than not, something is wrong with your config. I mean, what's more likely? No one else has confirmed you issues and you're running on an older version of Windows that's two major interactions behind.

Yeah, no. The browser is the one thing you absolutely should without a doubt run sandboxed. Anything that has access to the internet should be sandboxed. I have no problems at all running Vivaldi sandboxed. I may have at one point, but that's why you tweak your config to get things right rather than just give up.

 

That's not what I understood, the engine remains the same right? You are probably talking about the extra features found in SBIE Plus, but those also end up in Classic, but you just don't see them in the GUI.

I guess this might be true. I don't think it's about the configuration in SBIE though, I didn't change anything and in Classic it did work. To clarify, sometimes I listen to music via MPC, but then I want to open another video without sound, while the other video is on repeat. So that's why I need Sandboxie.

I have used Sandboxie for years to protect the browser, but I'm too afraid that this problem will show up once again. And it costs me way too much time to reconfigure Vivaldi, in case I have to completely reinstall, so for now I'm relying on other anti-exploit tools. Of course, for top notch browser security, you can't beat Sandboxie. But for now I only use it on demand to quickly run or install some app.

 

Again, you're thinking of this backwards. Don't reconfigure Vivaldi, or any other app. Tweak your SBIE config. 90% that will. Of course if you are unwilling to do so, you can always continue believing that sandboxie itself is the issue and that you are forced to stop using it. Your choice....

 

Windows 8.1 is still supported, but its technical features are behind Windows 10 or 11.

 

When i open a *.mp4 file using the context menu -> run sandboxed feature in WMP Classic it works just fine for me.

 

Technically I support windows 7 and 10/11 but not 8/8.1 as these versions were particularly terrible plus i wager what works on 7 and 11 should also work on 8.

 

So question to you all: Do you want the new more compact Box Options view to be in future the default?

 

By the looks of it, most of the recent iterations of Sandboxie (+) improvise improvements to GUI preferences, overall functionality, yada, yada,.. As opposed to a potentially "patented" (as in a uniquely stroke of brilliance that should rightfully be protected) breakthroughs
in overall security measures. I wish (upon a star) that there were current and reliable tests of Sandboxie via YouTube or along the lines of AV-Comparatives that would take this puppy out for a spin and see where all of these tweaks have evolved from purely a security
perspective. I have every confidence that Sandboxie would fare exceedingly well. That currently observable empirical evidence by both scrupulous and competent testing sure would be a proverbial feather in the cap to know just how great this app actually ticks.

 

Not true, Sandboxie-Plus v1.3.x introduced not one but two new important security mechanisms SysCall Lock down and restriction of driver endpoint access.

 

I don't really care. If I had a vote, I'd suggest the gui remain somewhat constant. It's important to not feel like you have to keep re-learning the same program over and over. Continuity helps.

 

Yes I like it @DavidXanatos

Also don't miss this issue. Custom columns width get reset to default after a machine restart: