Sandboxie-Plus 1.15.9

Sandboxie Plus 1.15.9 delivers a robust update centered on security, stability, and compatibility—particularly for users of modern web browsers and those prioritizing privacy and sandbox integrity.

A key highlight is the improved compatibility with Firefox 137 Nightly and later, resolving previous hooking issues that caused instability or functional limitations. Firefox now runs smoothly within sandboxed environments once again.

Security enhancements are another major focus. This release addresses a potential IP leakage vulnerability affecting dual-stack IPv4/IPv6 setups when only one proxy type was configured. Connections now fail gracefully if no proxy is set for the relevant IP type, effectively preventing unintentional bypasses and preserving user anonymity—a critical improvement for users relying on VPNs or proxies.

Additionally, a serious local privilege escalation vulnerability tied to the HostInjectDll mechanism has been patched, thanks to responsible disclosure. This fix strengthens Sandboxie's role as a secure execution layer.

For advanced users, a new debug option OpenAllSysCalls=y has been added, allowing unrestricted system call access for testing purposes. However, due to its permissive nature, it should be used with caution.

Among the usability improvements, users can now duplicate sandboxes and their contents directly from the UI, streamlining environment management. The update also introduces a new developer certificate type that disables user-mode component verification for advanced use cases. This node-locked certificate is available at no additional cost to existing Contributor or Eternal/Huge certificate holders upon request.

Overall, version 1.15.9 brings a thoughtful balance of new features, critical fixes, and user-focused enhancements, reinforcing Sandboxie Plus as a powerful tool for secure application isolation.

For a full list of changes please review the change log.

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

 

@DavidXanatos

A problem with v1.15.9 and earlier versions of Sandboxie Plus and HitmanPro.Alert. Firefox and Edge both wont start sandboxed (Werfault). Its #complicated according to HitmanPro.Alert devs.

 

Errors Sandboxie Classic v5.70.9 when trying to sandbox a browser. Cant upload a jpeg-picture (iPadOS).

Error by Sandboxie:

err=C1020918 GdiDLLInizialize (1) and RegisterClassW (1).

Reverted back to .8, no problems.

Edit: HitmanPro.Alert not installed

 

Win10.

 

A bit strange: Sandboxie suddenly wants to install a driver (both the reverted .8 and .9). Text is in Dutch and a jpeg-photo (iPadOS) wont upload again (not allowed extension).

 

Chrome was blank after the install (classic version) until I closed it and re-opened but it's fine now.

Question - not related to this new build but, I made a sandbox for removable drives awhile back.

When I right click a folder to open it in that sandbox, it takes a good 4-5 minutes to pop up (it does eventually open sandboxed) and I get this error:



Any idea what would cause this? Never had this problem before but I rarely use that sandbox.

I just checked and this same issue affects my default box. When I right click it takes a long time to open and same error. My forced programs open quickly.

 

this is really strange ther is an other report of teh same issue: https://github.com/sandboxie-plus/Sandboxie/issues/4638

but i cant reproduce it firefox runs just fine on my test system when sandboxed and the recent changes hsould improve firefox compatybility actually

 

Is the box located on a removable driver?
does the issue go away when you delete the boxes content

 

Firefox and Zen, which also runs 136.0.4, both run fine for me.

 

I think on 1.15.8 this 2 errors were still present but just failed silently.

 

No - not a removable drive, it's just another box I created on my desktop computer for when I use USB drives.

I do not often clean out the sandbox from within the software ( I use the classic version btw). I typically will use CCleaner and Wise Disk Cleaner. I assume they delete the contents of all sandboxes because their settings are not specific to a particular box.

When I tried to use the delete contents option in SBIE I got these errors:




I have admin privileges in my account so this is puzzling. I do notice multiple instances of sbie things running under different user names - is that odd? I don't mean other people on my system but the different types of accounts under windows.

Here is a screen shot from task manager showing what I mean. Is this part of the reason for this odd behavior? I assumed every sbie element would run under my account but they do not. I am chip by the way.



If I go into windows services, the sbiesvc itself is logged in under "LOCAL SYSTEM"

Sorry for the long post...just trying to understand what's going on.

The problem with the window taking forever to open and the errors persist with the boxes cleaned out.

 

Firefox 137, Firefox Beta 138, Thunderbird 137 work perfectly with SB 1.15.9 on Win11,
even after security.sandbox.content.level 7 was reset to level 8 in Firefox.

 

the different users is normal and if you enable some otehr option you wil see even more users like Sandboxie/DefaultBox instead of anonamouse user etc

 

Based on the infos i have currently this is not a new issue, in previouse versins these 2 failed silently.
Also FF does not hook this functions, so you must have some 3rd party tool other then sandboxie that hooks these functions in firefox, could you please download TaskExplorer and post a screenshot of the modules tab for firefox, liek this:


You open TE select a firefox process onthe left then the modules tab on the right and voila,
you can also right click into it and "copy panel" then you will get it all as text thats even better

 

Cant use this specific pc right now (not at my house). Norton 360 installed as 3rd party tool.

 

This one is ok?

 

OK - thanks for the explanation.

So I've been fiddling with settings trying to get the sandboxes to open a folder from the right click menu. I got the default box to work by including a few more files in the start/run list. I added runtimebroker and explorer.exe and the sandboxed folder comes right up.

The 2nd sandbox will still not open for 5-6 minutes. It has no restrictions on it so I can't figure it out.

The error I get has some very odd characters in it - have you seen this before?



I ran Adwcleaner and Malwarebytes and found nothing.

 

Firefox 137 won't stream video on multiple streaming platforms under sandboxie + version 1.15.9. It seems to be a Firefox 137 issue as it now no longer works on SB+ 1.15.8 either (tested on another machine still running 1.15.8 & FF 137.0). The previous versions of Firefox streamed under sandboxie+ with no problems. I can still stream videos on FF 137 non-sandboxed, just not with sandboxie. The problem is on both Windows 10 22H2, and Windows 11 24H2. No Hitman Pro on any machine, just Windows Defender.

The streaming sites include: tvnz.co.nz, neontv.co.nz, amazon prime (primevideo.com), disney plus, & netflix. There are probably others, but they are the ones I've tried. The websites load fine & I can sign into my accounts OK, but I just cannot get shows to play. I installed 1.15.9 over the top of 1.15.8, keeping the same settings. DRM content is enabled in FF. I think the issue seems to be related to DRM, as you can see from the screen snips below. The screen snip if from trying to play an episode on TVNZ OnDemand. The errors are all the same across all streaming platforms as shown in "SBie Messages" in the snip below.



@DavidXanatos - posting here as I don't have a github account, though I notice there is an issue loaded on github tagged as awaiting confirmation (or similar) for someone trying to play stuff on disney plus.

EDIT: Downgraded to Firefox 136.0.4 and I can stream on streaming platforms again with Sandboxie in both 1.15.8 & 1.15.9. Something has clearly changed with the way FF 137 behaves under Sandboxie when streaming DRM content. Youtube plays fine.

 

I can confirm the issue:

Code:

05.04.2025 11:42:56.532   plugin-container.exe: SBIE2180 LowLevel.dll Fehler 0x00FD0060                         
05.04.2025 11:42:56.632   plugin-container.exe: SBIE2180 LowLevel.dll Fehler 0x000D0060                         
05.04.2025 11:43:06.701   PID: 2408: SBIE2336 Fehler im GUI-Server:  [55 / C0000155]                             
05.04.2025 11:43:06.705   PID: 2408: SBIE2335 Initialisierung für Prozess WerFault.exe [88 / 0] fehlgeschlagen

 

To add to previous post, I tried to open a photo sandboxed by right clicking it and it never came up.

The following error did though, and that window was sandboxed. It took 10 minutes for it to appear.



Strange things are afoot at the circle K....

 

This version did not update itself. After clicking yes to update - nothing happened. Had to start the updater manually.