Sandboxie-Plus 1.13.3, 1.13.4

This release advances the 1.13.x build line from its experimental pre release stage to stable release, it adds significant enhancements to the hooking mechanism associated with SCM-related functions, which enhances compatibility with newer versions of Windows. The revised hooking mechanism now supports API call tracing without the necessity for LogAPI.dll.

Additionally, this update introduces a feature aimed at increasing the privacy of encrypted boxes. When the option IsProtectScreen=y is set, windows of processes operating within boxes with this option enabled will be obscured during screenshot capture or recording, enhancing user privacy.

The release also enhances the compatibility of privacy-focused boxes with Windows Explorer, resolving issues related to the Recycle Bin. To this end a new default compatibility template has been introduced, which uses a new functionality of the wildcard pattern mechanism. Now the "**" pattern is supported, which acts as a placeholder for an arbitrary string without including the backslash ("") character, thus allowing users to apply wildcards to exactly one directory level, unlike the single asterisk ("*") which applies to multiple levels.

The update also introduces compatibility with Windows 11 insider builds up to 26080.
And modifies how the driver manages offset-dependent kernel object changes, the new method now enables loading an offset configuration directly from the registry, allowing offsets to be updated without the need to rebuild the driver.
To increase system stability, Sandboxie will cease using outdated known offsets for new, unrecognized kernel builds. This change applies except in cases where the PC is part of the Windows Insider Program.
In such instances, instead of using outdated offsets, the software will disable token-based security isolation and will display the warning SBIE1207, indicating that it has reverted to an less secure fallback mode of operation.

While this build has been tested and appears functional, users may encounter minor issues in certain edge cases.

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.13.3
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.13.4

Full Changelog: https://github.com/sandboxie-plus/Sandboxie/blob/master/CHANGELOG.md#1130--5680---2024-02-10

1.13.4 changelog: https://github.com/sandboxie-plus/Sandboxie/blob/master/CHANGELOG.md#changelog

 

I have set this build to be pushed by the auto updater for the preview channel
and if no issues arise I'll push it in the stable channel tomorrow or so, and add to the website's download section.

 

With v1.13.3 it takes 22-25 seconds to open a sandboxed Edge (version is up to date). Tried it several times: same result. Also with hardware acceleration ON and OFF.

Edit: no problems with Firefox 123.0.1.

 

Whats the command inside the link?

 

Strange for me edge starts just fine, was the issue present in 1.13.2 or earlier?

 

Same issue with v1.13.2 and v1.12.9. Could be Edge-related.

Microsoft Edge version 122.0.2365.92 (Official build) (64-bits)

 

Could this cause it? From the logs:

Autopilot.dll WIL error was reported.
HRESULT: 0x80070491
File: onecoreuap\admin\moderndeployment\autopilot\dll\dllmain.cpp, line 185
Message: NULL

Win10 22H2 build 19045.4170 x64

Btw Edge starts instantly unsandboxed.

 

In the past I alone had a specific issue with Sandboxie (Plus) and Microsoft Edge.

See: https://www.wilderssecurity.com/threads/sandboxie-plus-v1-8-1.450921/page-2#post-3139343

So no need to investigate further David. Only if other users report this too…

 

Did a fresh/new install of Sandboxie Plus 1.13.3 and everything works smoothly.

Sandboxie Plus 1.13.1 (64-bit)
- (Red Box) Hardened Sandbox with Data Protection
- Snapshot
- Auto Delete enabled
- Virtualization Scheme Version 2
- BlockInterferePower=y
- (Global Setting) Check sandboxes auto delete status when sandman starts enabled
- (Global setting) Use Windows Filtering Platform to restrict network access enabled
Windows 10 22H2 (64-bit)
Firefox 123.0.1 (64bit)
Thunderbird 115.8.1 (64-bit)
Microsoft Edge 122.0.2365.92 (Official build) (64-bit)

 

I'm getting a timed out error on Firefox 123.0.1 when using Sandboxie 1.13.3. I have Google.com set as my homepage in firefox. When unsanboxed it loads instantly, but when starting firefox in the default (yellow) box it takes about 10 second to load the google homepage sometimes, mostly it just give me a time out error and I have to hit the "Try Again" button to get the Google homepage to load. Sandboxie 1.12.9 does not have this issue. Anyone else having this issue with 1.13.3?


New install of Windows 10 22H2. Getting the same timed out results with firefox on a different PC when using Sandboxie Plus 1.13.3. No issues with 1.12.9 on either computer.

 

what about 1.13.0, 1.131, or 1.13.2?

 

BTW, I have a general question, not specifically about this new version.

But if you give for example Vivaldi full access to the profile folder, how does Sandboxie decide where the profile folder is? Because you can also install a ''portable'' version (it's not fully portable), this means you can install Vivaldi anywhere on the system, like in the Downloads or Documents folder. But then how would Sandboxie know this?

 

The settings in the browser templates are based on the browser's default profile locations. However, you can change these default locations if you wish, or create custom templates for the browser you want.

For Sandboxie Plus:

How to change browser template path:

1. Sandbox Options > App Templates > Select a browser template
   
2. Sandbox Options > App Templates > Template Folders > Select a new folder for the Tmpl.Browser

How to create a custom browser template:

1. Sandbox Options > App Templates > Templates > Add Web Browser template (From the drop-down menu next to the add template button)
2. Follow the steps in the wizard

 

Thanks, will look into this.

 

1.13.0, 1.13.1, and 1.13.2 were also giving me the time out error. I thought it might be a Firefox extension that could be causing the issue, so I opened Firefox unsandboxed and disabled all three of my installed extensions. The issue persists with extensions disabled when running Firefox in the defautbox.

Edit: After further testing, I'm still getting either a 10 delay loading the homepage or a Timed Out error. It doesn't matter what site I have set as my homepage or which extensions I have enabled. Going back to 1.12.9 for now.

 

Firefox seems very slow loading pages on startup when sandboxed, eg compared to Edge. I thought it might be the number of extensions I have installed, but my setup is pretty much duplicated in Edge. I just live with it. I don't think it's related to any recent builds, been that way for quite a while.

 

After using the latest Sandboxie for a few days, I have noticed a 2-3 second delay in opening Firefox and Edge. Just thought I would post about it here. Not a big deal for me but it might be related.

 

Hello,

Where is a moving progress bar, if 2 conditions were met, clean cache and fist FF run? I really missed
Do you know what am I talking about?

With SBIE plus previous version https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.12.9
AND FF v123.0.1
I was able to see that bar, can I activate it again?

Do I have to run this .reg? The information provided in the website is hard to understand for me

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SbieDrv\Parameters]
"AllowOutdatedOffsets"=dword:00000001

Ms Win 10 v22H2 (OS Build 19045.4170) - x64
SBIE-Plus v1.13.3 - x64
Firefox v124.0 - x64

Thanks
Camelia

 

Nope.

It does not need to be used unless the developer specifies otherwise.

 

Hey David!! Firefox just updated to version 124.0 and now everything works properly. No more delay or Timed Out errors with Sandboxie Plus 1.13.3!!!!!!!!!!!!!!!!! It starts up in the defaultbox just as fast as unsandboxed!

Edit: Yup, I just verified on a different computer, updating Firefox to version 124 fixed the issue!

 

Same for me! How wonderful I had, very reluctantly, been thinking of moving to Edge but no longer needed.

 

Solved with Microsoft Edge Stable Channel (Version 123.0.2420.53).

 

New Update, its considered final but for today only in the pre release channel, if no issues appear I'll push it to the updater in the stable channel in a day or two.

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.13.4
Added

• added option to prevent sandboxed processes from accessing the images of the window outside the sandbox #1985 (thanks Yeyixiao)
  • it can be enabled with "IsBlockCapture=y"
  • see the sandbox option "Prevent sandboxed processes from using public methods to capture window images" in SandMan UI
• added "LingerExemptWnds=n" to make the lingering process monitor mechanism no longer exempt lingering processes with windows from termination
• Added option 'SharedTemplate' to Box Wizard #3737 (thanks offhub)
• Added an option to force the protection of an encrypted sandbox to be enabled. #3736 (thanks Yeyixiao)
• Added a menu and button/icon to suspend all processes [#3741] (#3741)

Changed

• option "LingerLeniency=n" now also disabled the 5 sec grace period for freshly started lingerers #1892

Fixed

• fixed issue with symlinks related to startmenu folders