Sandboxie-Plus v1.3.1, v1.3.2

As far as I can tell this issue arise because a update notice was saved and then the user updated manually.
So there will be the following changes to the next build to address this issue
1. in addition to the download file, also the version will be saved and upon start it will be checked if it is still newer than the current one.
2. it will be checked if the downloaded installer is still present in temp
3. a new info message will be shown when there is a update available even if its not yet downloaded

 

something "new" with my Edge sbox - and my Edge sbox not emptying?

1.3.1 - Edge 104.0.1293.63
Edit: "new" was a change in an extension setting.

 

why do you start cmd.exe in your edge box?
if you dont do that intentionaly than its very suspiciouse

 

I intentionally toggled Malwarebytes Browser Guard -> Hide duplicate warning On
I imagine Malwarebytes Browser Guard extension then wants to communicate with Malwarebytes Premium.
Hide duplicate warnings On = cmd.exe

I'd forgotten Hide duplicate warnings On = cmd.exe
I'm Hide duplicate warnings Off, now.
I don't run Malwarebytes Premium in real-time...anyway.

 

A short update from the "Opera"-front.

Whereas the latest "production"-version is still at v.90 and still seems to work flawlessly the "Developer"-Version meanwhile has upgraded to v.92.

Since v.91 - and even worse now - the user is overwhelmed with literally hundreds of immediate-recovery download-popups without having intentionally downloaded a single file. And if one clicks all those messages away (quite a nuisance) then upon finally closing the browser all those "download-artefacts" are still there and need to be deleted in Sandman manually.

This is not Sbie's fault but has been introduced by Opera when switching from v.90 to v.91 and up. Also at this time I cannot tell if other Chromium-based browsers are affected by this as well. Only that much I can tell - Chrome itself at its latest version is not. But at least Opera is again running into some compatibility-issues with Sbie in the very near future.

Addendum: Just found out that the problem described may only be triggered after installing "Opera Developer"-browser in "Standalone USB"/portable mode (as I always do for the "preview"-version).

 

I just tried the latest opera and i cant reproduce this issue

 

Ok, my apology. Meanwhile I've discovered that this is not an issue for "Opera Developer" v.91 and upward - but it is rather an issue with Opera installed in "Standalone USB"/portable mode. Hence the "production-version" v.90 is affected in the same way when installed in "Standalone USB"/portable mode.

So at this time I cannot tell since which Opera- or which Sbie-version this issue has started to occur. It must however be a relatively new phenomenon as it did not occur at all approx. 1 month ago.

 

is the portable directroy located in a location designated for file recovery?

 

Now that you mention it - sort of. But it is located in a SubDir of a location designated for file recovery. And it has been in this place for years without triggering the described phenomenon.

Is there a way to exclude specific SubDirs from file-recovery without affecting the parent-Dir? Or can the parent-Dir be exclusively designated for file-recovery without propagating to its SubDirs?

Strange thing though that - if this looks like being the culprit - the issue hasn't occurred all the time then. But shouldn't file recovery only be triggered after intentionally downloading any files by the user - and not by any files temporarily downloaded by the browser itself in the background during ordinary browsing?

 

Ok, found out myself how to do that by excluding the "Opera-Dev" folder specifically. Problem solved.

 

I am going to travel with a laptop and installed SB plus on it. In the past I used a guest account for browsing in windows - given that all browsing will be happening fully sandboxed and via a VPN, is there a still reason to create a special guest account in Windows / without admin rights?

 

Not really.

the only reason for guest accounts is if you intent to allow strangers to use your computer.

 

thank you - I thought in the past it was also to prevent anything to run with admin privileges, so using a limited account would reduce the risk. However, since I am the only one running the laptop and will use SB anyway for general browsing or anything odd, just using my normal login will make it easier.

 

After each Windows restart (or user logout and login again), SandMan reports the following message:

"Default sandbox not found; creating: DefaultBox"

If the DefaultBox is already in the Sandboxie.ini, SandMan should not create it again and display this message, right? This also happens with a new default installation (which I tried in my VM). SandMan doesn't seem to recognize the DefaultBox at the first start...

 

Thank you for your reply. Strange that the issue does not occur on your system.

I can reproduce it at any time. I also noticed during the tests that it is even enough to simply close SandMan via Exit and restart it to trigger the issue.

As already written, the issue can also be reproduced in a clean VM with a fresh install of Sandboxie v1.3.1:

 

I have copied your DefaultBox settings into Sandboxie.ini as a test. Unfortunately, SandMan still reports the allegedly missing DefaultBox.

I think @DavidXanatos would have to take a quick look at why SandMan can't find the DefaultBox, even with a clean reinstall with the default values.

[Windows 10/11 21H2]


Edit: By the way, the video in this post also shows the issue (at 0:37 and 1:12), even though the post is about a different issue:
https://github.com/sandboxie-plus/Sandboxie/issues/2111#issuecomment-1210364368

 

I'm having trouble using Firefox sandboxed while having a program called ReHIPS installed. I added the program just for added security for the things I run outside of sandboxie. Some reason even when I disable everything to do with firefox in rehips, sandboxie is still unable to open firefox. The processes appear to load but nothing ever shows up on my screen. I posted over at the rehips forum and the admin seems to think it's on sandboxies side so I posted here in hopes that maybe you could figure out what was going on.

Windows 10 21H2 (Home)
Firefox 104.0
Sandboxie-Plus 1.3.1

Here's the post I made on rehips forum.
https://forum.rehips.com/index.php?topic=13698.0

 

Not really an issue for the video in your link because the sandboxie.ini
(used for that video and posted there) has no DefaultBox in the settings.

 

Build v1.3.2 is out with variouse minor fixes and improvements

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

Changelog
Added

• added icons to sub tabs in the box options dialog
• recovery and message pop-up menu options are not persisting across UI restarts any more
• added new box color, a white box indicates that its not really a sandbox and is displayed when the user specified OpenFilePath=* or alike

Changed

• Sandboxie no longer issues message 1301 when forced processes are temporarily disabled
  -- the message can be re-enabled with "NotifyForceProcessDisabled=y"
• reworked the "Open COM" checkbox mechanism in the plus UI
  -- Now it uses a template and it can also keep COM closed while OpenIpcPath=* is set

Fixed

• fixed compatibility issue with Proxifier #2163
• fixed encoding issue with Korean translation #2173
• fixed issues with update available message

 

In the video you can clearly see that the DefaultBox is already existing from the beginning. The user then simply installs different versions of Sandboxie over the previous versions. So the DefaultBox is present in the Sandboxie.ini at every step shown.



(And even if the DefaultBox had not been existing from the beginning, it would have been created automatically at the latest after the first installation process, so SandMan should have recognized it at startup after the second installation process.)

 

@APMichael
Is your profile named "User"? Did you check the folder permissons? Are older versions working?

 

+1.