Sandboxie-Plus 1.0.22

This build brings a few fixes as well as a few small features, most notably support for the new windows 11 explorer context menu.
For now to get it enabled the setting needs to be manually toggled on windows 11, a later installer update will automate this for win 11.

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.22
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.21


ChangeLog 1.0.22
Added

• added auto update download and silent install option to sandman.exe #917
• trace monitor mode can now also save to file #1851
• trace log now shows ipc object type information
• added support for windows 11 context menus

Fixed

• fixed sandman crash issue #1846
• fixed issue with windows server 2022 build 20348
• fixed translation switching issues #1852

ChangeLog 1.0.21
Added

• added "FuncSkipHook=FunctionName" option to selectively disable individual function hooks

Changed

• improved support certificate entry box
• changing language no longer requires a restart on Plus UI
• fixed issue with high CPU load when using SbieCtrl to change settings

Fixed

• fixed issue when running Firefox/Chromium browsers compiled with MinGW toolchain #538
• fixed issues with folder recovery on Plus UI #1840 #1380

 

David, I bookmarked github awhile ago to get the latest releases.

Do you have any idea why when I go to my bookmark now:

https://github.com/sandboxie-plus/Sandboxie/releases/

I see this - an old version.

 

I have that one bookmarked too. Dunno why he hasn't updated that one.

Also you can bookmark this one:
https://github.com/sandboxie-plus/Sandboxie/tags
It seems more reliable, not sure though.

 

I am seeing the same old version at the top of the page using the same link as g17, which I too, have bookmarked. Choosing "tags" instead of "releases" at the top of the page brought up v1.0.21/5.55.21 though.

Thanks for this update! Version 1.0.21 running beautifully so far on the 2 machines I've installed it on. 5.55.21 running well on the one machine I use Classic on. I read you fixed some CPU spikes, but can't say I ever noticed any on 1.0.20 or 5.55.20, or any previous versions... Not sure what you had to do to provoke the high CPU spikes, but I can say with normal use just web browsing & streaming etc I never saw an issue. The particular Win 10 machine I run Classic on has only 8GB ram and a very old & underwhelming m7-6Y75 CPU, so it's SLOW & gets stressed out quite easily! So I'm not sure if the issue was just something only some folk were experiencing, or I simply wasn't doing whatever it took to provoke it.

Will update here if I notice any unusualness on either version.

 

He did this

 

Bug exists in build 21 as well, FYI.

 

No cpu spikes from SBIE svc to my observation, I have Task Manager open right now and Firefox itself is under 1%. Now, it's zero. Very stable (Plus v.21) I'm liking the recent changes to the security and it's just a pleasure to run it. It's like it's not even there.

 

The reason you didn't see any spikes is because unless you are looking at Sandboxie with a magnifying glass like I am doing at the present time, you wouldn't notice anything.

You wonder what you had to do to trigger the cpu spikes. Read here. If you created a new sandbox or made changes in Sandbox setting, Clicking Apply and/or OK triggered the cpu spikes. The spike would last a few seconds and cpu usage could jump up to somewhere around 70%. Most of the times (for me) cpu usage jumped to around 25%.

Bo

 

Well you're right, I am not scrutinising Sandboxie with a magnifying glass because I don't feel the need to do that; the software just works and acts like it isn't even there.

I can't remember when I last had cause to tinker in Sandboxie Control or made a new sandbox. If there were CPU spikes when I installed Classic and created my sandboxes etc, then I either didn't experience them or simply didn't notice them. If they only happened for a few seconds then I may well just not have noticed, or put it down to that machine being it's usual gutless self, lol. Sandboxie processes have never been anywhere near the top of my CPU usage when I have had cause to check my task manager though, on either version. It's one of the many things I like about it.

 

Once you make your sandboxes and set them up. It would be almost impossible to detect this spikes. Specially, since after you setup things for the first time, you might create only one or two new sandboxes a year, and only make a few changes in settings if any. Very hard to notice.

Bo

 

Does for me now too! Whatever the problem was, it's now resolved.

 

The issue was a bug in github and affected mre than just sandboxie, but it seams they fixed it.

 

I have the [#] indicator in both classic(5.55.21) and plus(1.0.21). Perhaps a reboot might help?

 

Interesting, I had not noticed that. I am running 1.0.21 with Vivaldi and Chrome in the same sandbox. Both of them have the yellow borders but in the task bar only Chrome has the #.

 

For me it works this way with version 1.0.21 (using Firefox and Chrome) :

- The colored border is here with both browsers.

- The # is here in the taskbar for the opened windows of both browsers.

- The # is here in the browser title bar for the windows of Firefox but not for the windows of Chrome.

 

Seems all my processes run with # except for Vivaldi. Thought for whatever reasons it may not be sandboxed but checking sandman it's shown as sandboxed but without # even there. Trying to test how this would appear unsandboxed, I notice that even when pausing forcing programs, Vivaldi opens sandboxed. Does not happen to Firefox.


edit: Just installed V1.0.21 on a different pc (updating from an older version) and here Vivaldi is not working at all. There is like a flash second flickering of the screen and then nothing happens. Vivaldi opens normal when unsandboxed.

 

Salutations/Greetings,

Not working with Avast Secure Browser, can you check into and please, fix!
Would deeply appreciate,
Always the best and kind regards,

 

as test: installed Avast Secure Browser on W10 Home 21H2 (19044.1645)
Made two changes from default setup.
Run Sandboxed - Avast Secure Browser desktop shortcut - [DefaultBox] default settings.

Spoiler: Avast Secure Browser

 

Edge does not use a Title bar, that's why you dot see the # sign in Edge. Programs that don't display a title bar will not show the # sign. It has always being like that.

Bo

 

@bjm_
Salutations/Greetings,
Look the Avast Secure Browser, over in detail and I think that it may one of my extensions.
But, I appreciate the thoughts and feedback. Also, it still not working correctly.

Always the best,

 

Has anyone successfully been able to run and terminate Vivaldi with SBIE lately? I can't. I used to be able to just fine, but now Vivaldi runs fine but does not terminate or delete on close like I expect it to. I'm not sure why. I used to run it no problem. If anyone could help me solve this I'd appreciate it.

Code:

Enabled=y
AutoRecover=y
BlockNetworkFiles=y
CopyLimitKb=1030030
AutoRecoverIgnore=.part
ClosedIpcPath=!<StartRunAccess>,*
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
AutoDelete=y
BorderColor=#000000,off,6
Template=Vivaldi_Sync_DirectAccess
Template=Vivaldi_Bookmarks_DirectAccess
Template=Vivaldi_Force
Template=OpenSmartCard
Template=OpenBluetooth
Template=LingerPrograms
Template=SkipHook
NotifyStartRunAccessDenied=y
BoxNameTitle=y
ClosedFilePath=<BlockNetDevices>,InternetAccessDevices
ClosedFilePath=!<InternetAccess>,InternetAccess
ClosedFilePath=C:\Scripts\
ClosedFilePath=C:\Program Files\IFW
ClosedFilePath=!<InternetAccess>,InternetAccessDevices
ConfigLevel=9
ClosedFilePath=!<InternetAccess>,InternetAccessDevices
BoxNameTitle=n
ShowForRunIn=n
ProcessGroup=<StartRunAccess>,vivaldi.exe,RuntimeBroker.exe,rundll32.exe,plugin-container.exe,<InternetAccess>,dllhost.exe
ProcessGroup=<InternetAccess>,vivaldi.exe
LingerProcess=vivaldi.exe
DropAdminRights=y
FakeAdminRights=n