Sandboxie-Plus v1.6.1

This build fixes a few issues and introduces a new update mechanism which allows to update individual files.
On the "Support Tab" in the "Global Options" the user can choose from 2 release channels
Stable - GitHub Releases
Preview - GitHub Pre-Releases
There the user can also select how to behave when a "New Version" (where an installer is available) or a "Version Update" (where only individual files of the existing installation will be updated) is found.

The Stable channel's "Version Updates" normally only contain new Templates.ini (Compatibility) and Translations.7z, binary updates will be only distributed when a critical security fix has been implemented.

The Preview channel's "Version Updates" contain frequent binary updates allowing allowing to test the latest changes before they made their way to a GitHub (Pre-)Release.

The Installers will offer the ability to download the latest Templates.ini and Translations when installing.


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


[1.6.1 / 5.61.1] - 2022-12-04
Added

• added global option to introduce run menu entries to all boxes

Changed

• reorganized command prompt entries #2451
• the "live" update channel is now part fo the "preview" channel for which Version Udpates can now be disabled

Fixed

• fixed issue with support setting drop-down menu multiplying #2502 (okrc)
• added translations folder as deprecated, to be removed upon installation #2500 (lufog)
• fixed issue with disk usage of hidden items not counted #2503 (okrc)
• fixed issue with boolean settings which can also be set per process #2495
• fixed issue with disk usage of hidden items not counted #2503

[1.6.0 / 5.61.0] - 2022-11-26
Added

• added ability to import/export boxes into 7z files
• added new update mechanism allowing for incremental updates
  -- used for nightly test builds in the "live" update channel
  -- used to update Templates.ini and translations after installation #1105

Changed

• restructured the box context menu a bit
• SandMan translations are now compressed and located in translations.7z

Fixed

• fixed issue with recycle icon not updated in time #2457 (thanks okrc)
• fixed issue with "index out of range" #2470 (thanks okrc)
• fixed issue starting SandMan after install #2284
• fixed encoding issue with my_version.h #2475

 

So the updates I have been getting here, inc now 1.6.0.0, would that be Stable, Preview or Live?

 

Maybe it's not a "release" build b/c SmartScreen objected to the installation. (not signed, I guess).

I installed this build as hopefully, Firefox will start consistently now. Prev. there were times I would click on the icon and nothing happened.

 

v1.6.0 is a pre-release build.

 

Sandboxie-Plus-x64-v1.6.0.exe Installer is not signed.

 

Pre-release, that's why.

 

Because its for testing and signing it is an additional afford.

 

I know it's an oxymoron but is there any way at all to allow copy/paste with a security-hardened box (Firefox v. 107)? v. 1.6.0.

Never mind--wish I'd figured it out before posting this. I undid one of the settings "Block read access to the clipboard."

Phew, what a load off!

 

This build fixes a few issues and improves on the new update mechanism.

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

[1.6.1 / 5.61.1] - 2022-12-04
Added

• added global option to introduce run menu entries to all boxes

Changed

• reorganized command prompt entries #2451
• the "live" update channel is now part fo the "preview" channel for which Version Udpates can now be disabled

Fixed

• fixed issue with support setting drop-down menu multiplying #2502 (okrc)
• added translations folder as deprecated, to be removed upon installation #2500 (lufog)
• fixed issue with disk usage of hidden items not counted #2503 (okrc)
• fixed issue with boolean settings which can also be set per process #2495
• fixed issue with disk usage of hidden items not counted #2503

 

Could you please explain a bit more about how this will work.
For example, were there any "live" updates between v1.6.0 and v1,6.1?

 

There were no live updates yet.

The plan is roughly this:
A new Pre-Release Version is prepared (with new features), v1.x.0 this is uploaded to GitHub,
then as further improvements are added they are released as "Version Updates": v1.x.0a, v1.x.0b, v1.x.0c, etc.... using the live updater.
Intermittently a new Pre-Release may be uploaded to GitHub, v1.x.1 but only when also a new driver needed signing
And may be a few more live releases: v1.x.1a, v1.x.1b
Once a version is ready for a final release the version number is increased once more v1.x.2 and a final GitHub release is published.

The goal here is to get new version tested quickly before going through the procedure of signing everything, and to assure a better update quality on the final GitHub releases.

 

Thank you. What confused me is that there was
reference to v1.6.0a on github but nothing appeared
in the "live" update channel and then it disappeared!

 

yea initially i intended to make the current build 1.6.0a but as ich changed the update mechnaism once more i made a full pre release

 

Reporting a BSOD with v1.6.1 (portable) on Win10 Enterprise, 21H2 19044.1826
Happened twice when surfing on chromium browser and then closing it.
Where should I upload the minidump file please; about 901kB (zipped)?

Edit: Win10 is 64bit and Chromium is 64bit
Edit2: Just emailed minidump file to DX (apologies if not the proper way!)

 

Both Norton 360 and HitmanPro.Alert do not like Sandboxie Plus 1.6.1 at all.

 

Dump received looking into it...
@deugniet the pre release is not signed that's why stupid antimalware tools don't liek it.

 

Its a pre-release indeed. Thought it was an official release. Back to v1.5.3.

 

The driver in 1.6.x is teh same as in 1.5.3 so the BSOD is not a new issue

 

Its because it isnt signed (yet). Microsoft Smartscreen wasnt happy either with v1.6.1 (unknown publisher).

 

Short question: When i discover an error, should i post the error report into the thread which belongs to the used version, or should i post it into the thread with the newest sandboxie version? Or should i open a new thread for the error report?
At the moment i'm using version 1.5.3 of Sandboxie-Plus, and i posted a small bug report on 9th November into the thread for "1.5.0 / 1.5.1 / 1.5.2" (at this time i used 1.5.2), but i'm not sure, if this was the right place for it.

 

According to this it's a bug but it won't be fixed.

 

Do I need to allow the installer to access the Internet through my firewall?
UpdUtil.exe and SandMan.exe are already Allowed in my firewall.

 

this should be enough the instalers use UpdUtil.exe to check for updates

 

How do I know whether they were updated, or not? A msgbox would pop up?