This build adds a new scriptable troubleshooting wizard to help resolve sandboxing and UI issues, the wizard can be directly invoked from the SBIEMSG pop Up dialog. The settings dialog has been slightly restructured to add more space to update options, a bug was fixed causing the updater to run every day and not once per week, and a setting was added allowing to pick the update interval. We have also added an addon manager which allows to install additional components, like a script debugger for the troubleshooting wizard, a file checker, the logapi dll, and a few other usefull addons. This build has also significantly reworked the low level injection mechanism, it should now work better and is much more flexible, although this being a large change requires some testing to ensure it works great on all scenarios. Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.10.0 Added added box scripting engine to make SandMan more flexible added scriptable troubleshooting wizard #1875 added addon manager which helps to install additional and third-party components, available addons: ImDisk Toolkit - used to create RAM Disks and other virtual drives V4 Script Debugger - used to debug troubleshooting scripts Microsoft Debug Help Library - used for the stack trace feature introduced in 1.9.6 signcheck.exe - used to scan files on VirusTotal before recovering them SbieHide.dll - a third-party DLL to hide SbieDll.dll LogAPI.dll - an API logging library used for Buster Sandbox Analyzer added option to set the update interval to 1, 7, 14 and 30 days added What's new in Sandboxie-Plus dialog in SbieCtrl.exe to praise the new features of the Plus UI Note: this is shown after the installation of Sandboxie Classic added "fixdacls" command to KmdUtil.exe, it repairs broken DACL entries on the Sandboxie folder to fix issues where SbieDll.dll fails to load added option to hide Sandboxie's own processes #3054 added functionality to cache Sandboxie messages within the Plus UI #2920 added button to invoke troubleshooting wizard directly from the SBIE message popup Changed setup wizard has now a dedicated update configuration page this page will be shown once for all users who do not have updates enabled split the support page into Sandboxie Support and Sandboxie Updater tabs when the troubleshooting.7z file is available, the script engine will be used to match compatibility templates this allows a better granularity in template selection by using the AppCompatibility.js script reworked low level code injection mechanism to improve flexibility and debugging the main injection detour code is now written in C instead of Assembler and can properly report SbieDll.dll loading errors as SBIE2181 improved session agent startup to be more flexible improved SBIEMSG help handling, the link now contains message details allowing to point to a more exact document (if available) updated certificate validation code Fixed fixed uninstall issue in the Sandboxie Classic installer d1863ff added workaround for Chrome not starting on Windows 11 with KB5027231 #3040 improved compatibility with procmon/stack traces for debug builds fixed issue with non-standard command lines fixed online updater not checking every 7 days, but daily Removed cleaned up duplicate code (thanks lmou523) #3067
Installed over the top of previous build on Win 10 without any issues. Edge and Vivaldi running OK so far.
@DavidXanatos I have been able to run sandboxie in portable mode for versions prior to 1.10.0. I extract files to D:\SbiePlus, and add my sandboxie.ini and sbandboxie-plus.ini from previous build. Then I am good to go. Prior to v1.10.0, this has always worked flawlessly. With plus v1.10.0, there is a problem with regard to Sandboxie-Plus.ini: When sandman.exe starts, it creates a user\appdata\local folder Sandboxie-Plus with the file Sandboxie-Plus.ini in it (this folder and file never got created in previous builds). Changes to sandboxie-plus.ini through the UI are saved only to the user\appdata\local file. The Sandboxie-Plus.ini in my app folder (D:\SbiePlus) is simply ignored. No problems with sandboxie.ini. Back to v1.9.8 for now.
I've just installed the latest version and all appears to be working well. I was hoping it might have coincidentally fixed a problem I was having with the latest version of AssetUPnP but it hasn't so I used the troubleshooting wizard to submit some logs. I've been running AssetUPnP in a sandbox (installed into a sandbox) for a while but the latest version crashes during installation, whereas it's fine outside Sandboxie. I don't know what they've done, but with this version the executable has jumped in size from less than 7MB to now over 15MB. In a default sandbox with the only change being 'Make applications think they are running elevated' I see the following behaviour. 'Normal' & 'Security Hardened': AssetConfig.exe: SBIE2224 Sandboxed program has crashed: AssetConfig.exe 'Application Compartment': Unable to open 'D:\TEMP\SYSTEM\spi9421.tmp' After the installation "completes" you can launch the program, but instead of taking you to a landing page that allows you to select between instances and perform basic maintenance, it takes you straight into the Advanced Configuration, and on clicking 'OK' everything closes rather than going back to the landing page leaving Just to reiterate, this isn't a change to Sandboxie that's caused this but a change to AssetUPnP I believe. Any help would be much appreciated. EDIT: I forgot to say that both the trial and registered versions fail in the same way, so you can use the download from the first link for any testing.
Success Copying Sandboxie-Plus.ini to PlusData works. No user\appdata\local folder/Sandboxie-Plus files are created. Changes to Sandboxie-Plus.ini occur only to the copy in the folder PlusData. Do you know if this is an intentional change going forward? Thank you
@soccerfan I don't know. You may be trying to use the portable version without removing the installed version, or there may be some other bug. Spoiler: use AppFolder/PlusData when present, else fallback to AppFolder Code: https://github.com/sandboxie-plus/Sandboxie/blob/15afaf8399f72d1d16024149121159e6d647f9bc/SandboxiePlus/SandMan/main.cpp#L28-L31
I wanted to make booth possible instal fodler and PlusData apparently there is a bug with that will look into fixing it. I did not want to mix downloaded files with the installed files like a updated troubleshooting.z7 or addons.json, etc...
its strange i cant reproduce the issue for me the instaler proeprly cerated an empty sandboxie-plus.ini in the portable folder and then sandboxie properly picks it
I had already created a PlusData folder in anticipation, based on your post on addons/extensions . https://www.wilderssecurity.com/thr...ng-upcomming-new-feature.451591/#post-3152377 Btw, the install of "sigcheck" components went into D:\SbiePlus\bin and not D:\SbiePlus\PlusData\bin. And thank you @busy for the link in post #7.
@DavidXanatos Some plugins fail to install until I manually create the respective folders. C:\Program Files\Sandboxie-Plus: bin folder for sigcheck sbiehide folder for sbiehide etc.
This is exactly right when the subfolder PlusData is not present in the portable folder. BUT... If folder PlusData is present (e.g. created manually as I had done) , Sandboxie-Plus.ini in portable folder is ignored and two cases arise: CASE 1: If Sandboxie-Plus.ini exists (e.g. copied there) in PlusData, this ini file is always used and written to when changes are made. CASE 2: If PlusData does not contain Sandboxie-Plus.ini, a new folder "user\appdata\local\Sandboxie-Plus" is created and a new Sandboxie-Plus.ini appears in this folder and is used and written to when changes are made. When the folder PlusData is present the main portable folder, it prevents Sandboxie-Plus.ini in the portable folder from being used. Something is amiss.
ah yes that makes sense... About the folders used I decided to use \bin to make installed addons fork for everyone, also files under program files are better protected from tempering
If I already have ImDisk set up do I need to change anything, or even uninstall it and let SB do its thing. Hopefully, not the latter as it works well as is.
Shouldn't the sandboxie-plus.ini in a portable folder always take precedence regardless (of PlusData subfolder being present)? Noted for future reference. Thanks
I get this text in the agreement when I install Classic on this old laptop. Am I just unlucky or perhaps I need to learn another language Happened on the last couple of builds as well.
This is because the language encoding setting that Windows uses for non-Unicode programs doesn't match the language encoding in which the LICENSE file is saved. ( Windows:windowsXXXX / Sbie: LICENSE.TXT, UTF-8 ) Code: https://stackoverflow.com/a/2477480
