New Sandboxie-Plus insider build (Feb-20-2025) available

The Sandboxie-Plus Insider Program provides early access to new features and functionality that are not yet available to the public.

To become a participant in the Insider Program and gain access to the private Github repository with new releases, you must contribute to the project in a meaningful way, such as by helping with documentation, development, providing translations, or by submitting exceptional bug reports. Alternatively, you can support the project on Patreon at the GREAT tier or above. All users with CONTRIBUTOR or HUGE certificates are automatically eligible.

This insider build is a bit more experimental them usual, meaning there may be new issues with that one.

The current insider builds contain the following features:

1. Isolated sandbox desktop




If you manover yourself into an empty desktop with no shell, use Ctrl+Alt+Del to start the task manager and run "C:\Program Files\Sandboxie-Plus\kmdutil.exe switchdesk Default" to return to the default desktop

2. Sandboxed clipboard & better clipboard isolation




3. Portable boxes




Changelog in compression to the latest public build:

Added

• Added sandboxed virtual desktop #3591
• Each sandbox can now have an own clipboard "UseBoxClipboard=y" #2385
• Separation of setting the clipboard's read/write access #4361
  • "OpenClipboard=n" "OpenClipboard=r" "OpenClipboard=w"

Changed

• reworked gui server a bit
• reworked ini handling #4492
  • Added ImportBox=C:\path\To\Box.ini
  • Added mechanism to create virtual config section in the driver without the need for an ini file

 

Chatty helped me to improve the insider info page: https://sandboxie-plus.com/sandboxie-insider/
what do you all think?

 

Nice, just one typo I see:

Eternal not "Ethernal"

 

I might contribute to translating things to Spanish. Note that I already have access to Insiders since ages.

 

How does this sandboxed desktop work? For now, in SB-Plus one can hardly try any software due to SB-Plus limitations, is this less limited.
Windows sandbox has the limitation that it is a totally new environment and therefore one can not test things like cleaners on the live Os to see how they perform.

 

it works like this: https://www.youtube.com/watch?v=EMlhObEiYiQ

 

That video did not make me any wiser. So my questions in post #5 still stands.

 

On windows you have such a thing as user sessions each logged in user gets an own session and each session has a Window Station object, and each Window Station contains a Default desktop.
But it can contain additional desktops, and using the SwitchDesktop function the active i.e. currently displayed and interacted with desktop can be switched to an other desktop.
And all the windows applications may have live on a desktop, they can not interact with windows on an other desktop, so desktops are fully isolated from each other.
What is not isolated is the clipboard as its shared among all desktops and belongs to the parent Window Station object.

Sandboxie now can create a new desktop one for each sandbox, and switch between these desktops, what it also can although that is still experimental and does not work quite flawless is to render an inactive desktop in a window on the default desktop.

Sandboxie uses a lot of hooks and a job object based isolation to isolate sandboxed processes on the default desktop from host processes, it renames window classes and does other things that may break things.

All this can be safely disabled when the application lives on an own sandbox desktop therefore in this mode the compatibility should be better, not perfect as other intrusive mechanisms still are in place, but better as one of the bigger once can be bypassed.

 

To go straight to it; does it work in any way as Shadow Defender did?

 

no