Sandboxie-Plus 1.16.1 (Pre-release)

With this release, Sandboxie’s core has been modernized to ensure long-term stability and compatibility with today’s development platforms. We’ve upgraded our build environment to the MSVC 2022 toolset—an unavoidable change now that support for the 2019 runner has been discontinued—and migrated our UI framework from Qt 5 to Qt 6. Together, these updates bring improved compiler optimizations and access to the latest Qt features, but in doing so they require us to discontinue support for Windows 7 and 32-bit operating systems. We understand this may impact some users; if there is sufficient demand, we will explore providing a periodic Extended Support Release (ESR) that maintains compatibility with Windows 7.

On the fixes side, this build addresses several noteworthy issues reported in recent weeks: shortcuts now correctly include the full directory path, resolving the incomplete-link problem; binding to a network adapter once again enforces isolation even if the adapter is disabled; file-path resolution no longer fails on paths beginning with a backslash; the UI language bindings have been corrected to honor the installer’s Language ID; the UAC prompt layout has been polished for consistency; and the “Run Un-Sandboxed” option will no longer be ignored when Mark-of-the-Web enforcement is enabled. We appreciate all feedback and bug reports, and hope you enjoy this more robust and future-proof release of Sandboxie.

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

 

Hello David,

Just a couple thoughts, first thanks for keeping a Win 7 version going for so long and It's a big reason I have been a supporter since the early days. However change is inevitable and I totally understand. Speaking of supporting; I have been buying the home version every year + encryption pack (past 2 years). Can there be a subscriber renewal deal similar to the personal license you have going? Or maybe a home+encryption pack for 5-10 less. The reason I ask is purchasing stuff across the pond has been terrible with the weak dollar to euro and what cost 65 last year is going to set me back close to 90 this time. How much would it cost to switch over to personal at this stage? I mean your work is worth it, but I just wanted to hear your thinking and I realize we are all losing to inflation.

 

Has anyone experienced that after upgrading Firefox to 141, they are unable to run it with Sandboxie (ver 1.16.1)?

 

I am running FF141 and after updating Windows 11 today I cannot run FF in Sandboxie. LibreWolf seems fine.

 

Unable to run Firefox 141 under Sandboxie 1.15.12 - it was working with Sandboxie 1.15.12 on FF 140. I have not tried the pre-release 1.16.1 but comments above suggest it isn't working with this either.

I can open FF 141 under Sandboxie just fine, however I can't navigate to anything or open up a bookmark - it's frozen & stays stuck in "not responding" the moment I try to do anything.

EDIT - I now think this may be related to the Windows Update yesterday. (2025-07 Cumulative Update Preview for Windows 11 Version 24H2 for x64-based Systems (KB5062660) (26100.4770)) I have just downgraded to Firefox 139.04, which used to work with Sandboxie, and it produces the same behaviour I described above.

Exact same issue as here: https://github.com/sandboxie-plus/Sandboxie/issues/4920 which is still listed as "confirmation pending". Consider this confirmed on 7 laptops in the house which received the above Windows 11 update, all running a mix of FF 140 & 141, & Sandboxie 1.15.12. This is on Firefox non-portable (github thread above states affecting portable as well).

 

I use Brave, Firefox is no good anymore, not since they added that thing to their ToS

 

What ToS are you referring to GrDukeMalden?

 

the entry in mozilla's ToS where you technically agreed to having all the data you put through FF to be scraped to train their AI

 

Question: If I put all these entries into the global rules

Template=BlockAccessWMI
Template=BlockDNS
Template=OpenBluetooth
HideFirmwareInfo=y
RandomRegUID=y
HideDiskSerialNumber=y
HideNetworkAdapterMAC=y
HideNonSystemProcesses=y
ClosePrintSpooler=y
CoverBoxedWindows=y


do they all apply to every sandbox I have and will make in the future?

 

Me too!


Kiadás Windows 11 Pro
Verzió 24H2
Telepítés dátuma ‎2025. ‎05. ‎03.
Operációs rendszer buildszáma 26100.4770
Minőség Windows-szolgáltatások élménycsomagja 1000.26100.197.0

 

David most likely will be responding.

 

Workaround: (Open COM access, reduced isolation!)

Code:

OpenIpcPath=firefox.exe,\RPC Control\epmapper

 

Thanks for the workaround but more instructions needed. Have scoured Sandboxie options but cannot see "COM access" anywhere or reduced isolation. Please could you start with where to find in Sandboxie Plus GUI, & if it is editing the ini could you please specify if that is global settings ini or just ini for the sandbox being used with firefox. Step by step would be helpful. Thanks.

 

fwiw ~ as test: Firefox sbox
Resource Access -> IPC -> Add IPC Path

Spoiler: related pics

Note: Firefox 141.0 call bookmarks okay with my 1.15.12 Firefox sbox sans

Code:

OpenIpcPath=firefox.exe,\RPC Control\epmapper

Note: 2025-07 Cumulative Update Preview for Windows 11 Version 24H2 not installed.

Edit: correction here #20

 

Thanks heaps @bjm_ Will give it a go.

 

^ Can confirm this workaround works on Windows 11 24H2 build 26100.4770, tested on 3 machines to make sure. I had difficulty adding the code to the IPC path, but found it works by posting code into Firefox sandbox ini & then OKing it. You can see it correctly added to the IPC section after that. Thanks to whoever discovered this workaround!

 

KB5062660 (22-07-2025) is a preview and optional. after a bigger issue here where a preview update was causing it i disabled such updates by GPO. 23H2 has no issues, but 24H2 is known for a lot inside changes, combined with preview updates it could get worse. if you do not want to be a laboratory mouse for ms then its better to turn such optional updates off.

 

Hi, is it enough to disable telemetry in Firefox settings to prevent this?

 

Okay...so, Code should look like:

Spoiler: related pics

[Firefox]
[...]
OpenIpcPath=firefox.exe,\RPC Control\epmapper

Thanks! @catspyjamas

 

So to clarify the issue is related to the update, but is it also related to FF version 140 -> 141 or was that just coincidence and with that update also older FF's break?

 

FUD should be a topic here. the updates tos from mozilla is already in this forum.
https://blog.mozilla.org/en/firefox/firefox-terms-of-use/
and 2 days later
https://blog.mozilla.org/en/firefox/update-on-terms-of-use/
mozilla would go wrong with the CCPA and consequences would go worse for mozilla.
so the new tos are needed to have firefox operated as it would be operated - same as for other software or browsers.
next - firefox does not collect any telemetry on android or ios.
fore sure mozilla drives some ai driven mechanisms, but this is only internal, and never sold.
what firefox offers are ai forms for external engines in the new sidebar which can be disabled -> sidebar.revamp < false
and no, telemetry can not make firefox buggy. what i wrote is what wiindows 24h2 users can expect with the given preview update. its microsoft caused and we all have to sit and wait, how David will resolve it.
there is no change within firefox which can cause this.

the epmapper -> endpoint mapper explained
https://www.thehacker.recipes/ad/recon/ms-rpc
so i assume MS hardened windows this way which is for all apps, not only firefox.

 

I wouldn't assume it's some hardening, sandboxie runs an own sandboxed RPCSS, most likely some windows component firefox uses now wants to use some COM object which is not available in the sandbox and this causes the failure.
If MSFT would have changed something that would break sandboxed RPCSS much more than only firefox would be affected.

PS: I am installing the update into ma Dev VM right now once its installed I'll know more....

 

just another question: is sandboxie using a kernel driver?

 

yes