Sandboxie-Plus v1.7.0, v1.7.0c

I've been using FireFox in the Hardened Sandbox with Data Protection for about two months and I haven't encountered such a problem. Windows 10 22H2 64-bit

10+ windows, 100+ tabs, 40+ extensions and 30+ process at startup

 

No, no Firefox failure-to-start issue since weeks, poss. months. Same entry in ini. Windows edition is Home 19045.2546 | 22H2.

Only thing: when having first installed "b," audio was very static-y. By closing and then re-opening Firefox, the issue went away and hasn't returned since.

 

Update 1.7.0c
Added

• added option to create a new sandbox to run from the box picker dialog
• added sandbox creation wizard (not available in Vintage View mode)
• added ability to open all com classes #2448 -- use OpenClsid={00000000-0000-0000-0000-000000000000} to open all
• the SandMan UI now indicates if a sandboxed process has a Elevated(Admin) or System token
• added self removing boxes #1936
• added Ctrl+F search filter to the box picker dialog, this allows quickly to find a particular box
• added menu options to edit the templates.ini and the sansboxie-plus.ini

Changed

• box options now show the expanded paths where apropriate

Fixed

• fixed SandMan crash issue introduced in 1.7.0
• fixed trace log case-sensitive filter
• fixed performance issues with Delete V2
• fixed issue with NtQueryDirectoryFile data alignment #2443
• fixed issue with Microsoft Edge 111 dev build #2631
• fixed issue with run menu entries created from the options/settings window #2610
• fixed issues with start menu when using snapshots #2589

You can download the 1.7.0C installerd from github or run the live updater to only download the changed files.

 

was the previouse build behaving better?

 

Can try with the following code:

Code:

NormalFilePath=|%UserProfile%

 

did you created a new box recently? in 1.7.0c when you use the box creation wizard it wil use DeleteV2 which may not be fully bug free yet
if thats th case these 2 lines are present:
UseFileDeleteV2=y
UseRegDeleteV2=y

 

I have tested the blue box in a clean win 11 VM with 1.6.7, 1.7.0b and 1.7.0c, with Vivaldi installed on the host, and teh following configuration

Code:

Enabled=y
BlockNetworkFiles=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#f88501,ttl
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=9
AutoRecover=y
UseSecurityMode=n
UsePrivacyMode=y
NormalFilePath=C:\Users\Public\Desktop
#NormalFilePath=%UserProfile%
RunCommand=cmd.exe|"C:\Windows\System32\cmd.exe"

and vivaldi seams to start in all 3 tested versions


@stapp i see you have installed vivaldi to your profile folder, i installed mine for all users, will test your configuration next, i overlooked that detail before

 

Thank you for this option in v1.7.0c
I just used it to change NewConfigLayout=2 to NewConfigLayout=1 in sandboxie-plus.ini
and see the "new" layout for sandboxes mentioned in another thread

 

@stapp with this additional options a default blue box works for me with a vivaldi installed to the user profile

NormalFilePath=%UserProfile%\Desktop
NormalFilePath=%UserProfile%\AppData\Local\Vivaldi

the desktop is only to make drag and drop of the desktop shortcut to sandboxie work

 

When I try to use this I get



although it is located at

C:\Program Files\Utils\Sandboxie-Plus\

The links to sandboxie.ini & sandboxie-plus.ini are found/work as expected

 

What is the purpose of the cmd.exe line in the privacy (blue) box config?

Code:

RunCommand=cmd.exe|"C:\Windows\System32\cmd.exe"

 

It adds a run menu item to the right click menu of the sandbox to run CMD.exe. (Plus only)

 

Thanks @busy I always gain from your comments in this forum
There are NormalFilePath (and other) settings that don't show up (are hidden) in the config
if we have UsePrivacyMode=y and I was wondering about why the run command
is explicitly needed and what its function is in this blue (privacy) box.
Perhaps you can shed some light on that.

 

The command line can be accessed more easily by adding a custom menu item. (In three steps instead of four )

For Sandboxie-Plus:
Sandbox right click menu > Run > cmd.exe (3 steps) [Custom item]
Sandbox right click menu > Run > More Tools > cmd.exe (4 steps) [Hardcoded item]

It is also easier to test file access rules using the command line. Or to see which files/folders were created and not in the sandbox.

Spoiler: Unnecessary information

For Files:
"UsePrivacyMode=y" simply means "WriteFilePath=* - Exceptions". (This is only possible with "UseRuleSpecificity=y".)

"WriteFilePath" is an enhanced form of "ClosedFilePath". It will hide files or folders outside the sandbox, while allowing new files and folders to be created in the sandbox.

"NormalFilePath" allows to open locations to be readable and sandboxed. (Reverts to default Sandboxie behaviour, like in yellow/standard box)

Just an example don't use this:

Code:

#Options
UsePrivacyMode=y
UseRuleSpecificity=y

#Hardcoded rules
WriteFilePath=*
NormalFilePath=%SbieHome%\
NormalFilePath=%ProgramFiles%\
NormalFilePath=%ProgramFiles% (x86)\
NormalFilePath=%SystemRoot%\
.
.
.

#User rules
OpenFilePath=%UserProfile%\Downloads
NormalFilePath=X:\Custom\Programs\Folder\MyBrowser\
NormalFilePath=|%UserProfile%\Desktop\*.lnk

 

Thank you for this gold mine of information (including "unnecessary" spoiler)

A question about "NormalFilePath=|%UserProfile%" from your post #32 (and spoiler):
It seems that the "|" is used to suppress wildcards (*) and if so,
is it for just pre-appended *s only or both pre- and post-appended?

 

Only post-appended.

 

Many thanks @busy