Regressions with 5.52.x Classic builds

[Seeadler1]

The second sandbox disappeared in the Classic version after this update. Only the default box is displayed in the Sandboxie control.

Regards

[APMichael]

It is not because it is the second sandbox, but because of the name of the sandbox. If the sandbox is named "Edge", for example, then it disappears. Therefore, it would be important if the name of the disappeared sandbox was also mentioned here.

[Seeadler1]

The name of the second sandbox is: Sandbox2

[ghost]

For me one of few sandboxes also disappeared from classic sandboxie app window. I was still able to run apps in it using previously made shortcut. Reloading, deleting and adding sandbox name didnt fix the issue.

Also after this update I noticed I had Chrome as forced app in 3 sandboxes. It worked for me for many months (Chrome default browser was opening in right sandbox). After the app update, I noticed the Chrome opens on other sandbox, which allowed me to fix the issue in settings.

[DavidXanatos]

https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7b

[isaak654]

https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7b

It doesn't look fixed yet, according to some reports:
https://www.wilderssecurity.com/threads/sandboxie-plus-0-9-7-test-build.440906/#post-3038593
https://www.wilderssecurity.com/threads/released-sandboxie-plus-sbie-fork-versions-with-signed-driver.434924/page-43#post-3038585

[DavidXanatos]

how about this: https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7c

[bjm234]

how about this: https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7c

0.9.7c does not include SbieCtrl
https://www.wilderssecurity.com/threads/sandboxie-plus-0-9-7-test-build.440906/page-2#post-3038734

[DavidXanatos]

Is anyone using it with the plus installation? I thought by now I coudl remove it and no one woudl notice.
But if that's still needed i can add it back with the next release.

[bjm234]

Is anyone using it with the plus installation? I thought by now I coudl remove it and no one woudl notice. But if that's still needed i can add it back with the next release.

Oh? I must of missed the memo.
I like SbieCtrl.
I like Plus installer with SbieCtrl. I can refer to Plus UI and Classic UI to help Plus & Classic users. When Plus UI has glitch. I can run Classic UI and vice versa.
My vote is retain SbieCtrl. I'm using Classic UI...now. I like Classic UI.
I'm okay with what ever works for you & works for users.
Regards w Respect

[isaak654]

Someone has a new issue on 5.52.3 that wasn't present on a clean install with 5.51.6:
https://www.wilderssecurity.com/threads/sandboxie-plus-0-9-7-test-build.440906/page-2#post-3038839

3rd try. Still not working properly.

Classic Sandboxie 5.52.3 (64 bit)
Windows 10 (64 bit)

1. Clean install. Run/open Sandboxie and see there's now a sandbox but has the name of the previous version of Sandboxie when I did a clean install. Strange, I delete ALL directories and files before installing each version. Could be the name. sandbox and maybe settings are being retained in the registry.
2. First thing I clicked when I opened Sandboxie was View, then Files and Folders. Then I went to Sandbox Settings. Clicked on Appearance and tried to disable the last two settings and click Apply. This did not work. Every time I unchecked the boxes and hit Apply, the boxes would be checked again. So I decided to go to Applications and choose Firefox and LibreFox as my browsers. It worked but the browser settings to choose from are still mixed up with other browser settings instead of being grouped together by browser.
3. I went back to Appearance again to uncheck the last two settings and hit Apply. This time it worked. Strange! Went to other sections to select my settings and everything worked.
4. Opened my sandboxed app and there's a big thick yellow border around the app. So unchecking the last two bexes in Sandboxie Appearance did not work. I went back and tried to change the border thickness from 6 to 0 and hit Apply but it didn't work. It would always go back to 6. So there's no way to get rid of the thick yellow border around the sanboxed apps.
5. After all of the above, I decided to click Remove Sandbox and start over. The sandbox was not removed. I tried to rename it and strange things started to happen. I clicked Sandbox on the top menu and now there's invisible options in the dropdown menu.
6. Uninstalled 5.52.3, did a clean install with 5.51.6 (64 bit) and everything works perfectly again with version 5.51.6.

***Maybe some Sandboxie registry settings is interfering with the Sandboxie app?

[DavidXanatos]

I cant reproduce this issues can you?

[isaak654]

I can confirm this one on Classic 5.52.3 / W10 20H2:

After all of the above, I decided to click Remove Sandbox and start over. The sandbox was not removed. I tried to rename it and strange things started to happen. I clicked Sandbox on the top menu and now there's invisible options in the dropdown menu.

In my specific case I attempted to rename a sandbox from Saya to Saya2, but instead of doing it, Sbiectrl.exe created a new sandbox named Saya2 with the same ini lines of Saya in the opposite order (with all Template= references ordered at the bottom of the sandbox section, while these references should be theoretically ordered at the top, after Enabled= and ConfigLevel=). In addition, I tried to rename Saya2 to Saya5 and I noticed that it failed the first time, while the second time it succeeded.

Half of the time the renaming operation fails, and the "Remove Sandbox" operation doesn't get applied to the UI if you don't reload it. I would suggest to create a new sandbox and remove it after a few seconds... in this case you need to refresh the UI manually just to see it disappeared. For this reason, I had to downgrade to 5.51.6.

My Sandboxie.ini is located on the Sandboxie folder in %ProgramFiles% and it's encoded as UTF-16 LE BOM.

About the dropdown menu mentioned from that user, you could ask him if it's related to the visual glitch described here: #913
Even if it's not related, you may want to catch this occasion to fix it too.

[DavidXanatos]

this should fix it fo good: https://github.com/sandboxie-plus/Sandboxie/releases/tag/0.9.7d

[DavidXanatos]

PS: the order being changed is to be expected given how the settings are handled, but i can add a workaround that will preserve the order.
First lets fix all the actual bugs.

[isaak654]

First lets fix all the actual bugs.

One relevant regression left (on both v0.9.7e / 5.52.5):
https://www.wilderssecurity.com/threads/sandboxie-plus-0-9-7-test-build.440906/page-3#post-3039637

Please consider to fix the following Classic issue #913 if possible.
I pushed a fix for it time ago, but it didn't produce any effect (#761).

[DavidXanatos]

this should be fixed with ine of the latest builds so i'll close it

[isaak654]

this should be fixed with ine of the latest builds so i'll close it

This regression is still not fixed on v0.9.7e / 5.52.5, that appears to be the latest public build (till now):

I have installed the new version on all my systems and it actually runs without any problems.
Only on one system there is a small problem. Whenever I open a file dialog (via "Open" or "Save") in a sandboxed program the following error message appears:
SBIE2101 CreateFile (C0000022) access=0012019F initialized=1
The program doesn't matter, it happens e.g. with Notepad, Firefox, Acrobat Reader... The error message can be ignored, everything still works. If the "Explorer" itself is opened in the sandbox, the error message does not appear. The problem occurs only from the current version 5.52.x (also 0.9.7x). With version 5.51.6 or previous versions the error message does not appear.
Any ideas what this could be related to? Thanks!
[Windows 10 21H1 (x64)]

See also the confirmation sent by @APMichael today:
https://www.wilderssecurity.com/threads/sandboxie-plus-0-9-7-test-build.440906/page-4#post-3040149

Unfortunately, the error message is also with the Plus build without further information. :(
(So I could not find a solution myself, except to hide the error message.)
Good to hear that you already have an idea.

[DavidXanatos]

the message will be fixed in the next build