Sandboxie-Plus v1.5.0, v1.5.1, v1.5.2

Right click, select "Run sandboxed" and select and "Run outside the sandbox".

 

Yes it is, red/white cross overlay icon shows up and effectively pausing forcing programs...

 

B) What C:\Program Files\Sandboxie-Plus\SandMan.exe does and why EIS created a rule? Can I deny the Application?


Thanks
Camelia

 

On Win7 32 bit machine unable to open Firefox or Brave in v1.5.0. Get "SBIE 2112 Object is not accessible: Windows error reporting" error message. No problems opening either browser on Win10 64 bit machines in v1.5.0.

Any advice much appreciated.

 

With Brave Browser:

Code:

SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: connect C0000022
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 30 - brave.exe [C0000080]
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 4 - brave.exe [C0000080]
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 14 - brave.exe [C0000080]

With Vivaldi Browser:

Code:

SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 30 - vivaldi.exe [C0000080]
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 4 - vivaldi.exe [C0000080]
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 19 - vivaldi.exe [C0000080]
SBIE2203 Fehler bei der Kommunikation mit dem Sandboxie-Dienst: *GUIPROXY_00000001; MsgId: 14 - vivaldi.exe [C0000080]

 

Do you have check for updates enabled?

 

Yup, so SandMan.exe is only for to download updates automatically?
I don't want that, I will uncheck it and I will donate

 

When check for update is enabled when the support page is opened it automatically checks for updates on booth channels.
When check for update is NOT enabled when the page is open in row with the current version a clickable link is rendered "Check Now" to trigger the update check.

The 1st start wizard asks if check for updates should be enabled, the option is pre-selected, but unless finish is clicked not applied.

BTW I'm thinking of adding 2 more update mechanisms:

1. Automatic language update after installation, like already requested here https://github.com/sandboxie-plus/Sandboxie/issues/1105 the thing is for logistic reasons the language files are often not quite up to date when a build is released, this would mitigate the issue quite well.

2. Add a mechanism to update the Templates.ini with a check every day or so, as often issues can be mitigated with the right template entry, especially if I broke something with a new restriction I could disable that.

 

Hello,

this is probably not v.1.5.0/v5.60.0 specific because I just installed the classic version. I'm running Windows v10.0.18362.356 (32-bit) in VMWare Player and have installed Sandboxie v5.60.0 (32-bit). When I try to run anything sandboxed I get: "SBIE2112 Object is not accessible: \WindowsErrorReportingServicePort, call AlpcConnectPort (C0000022) access=001F0001 initialized=1".

What could be causing this and how to make it work?

Thank you.

 

So, it seems to be a in issue with 32-bit systems, because as mentioned above, I get the same error message on a Win7 32-bit machine.

 

Update 1.5.1 with various bug fixes is here

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

Changelog 1.5.1

Added

• added SBIE2227 warning when a sandbox is located on a volume without 8.3 name support
• added template for Tencent QQ #2367

Fixed

• fixed issues when renaming a sandbox with a custom path #2368
• properly fixed the Firefox 106 issue 46e9979
• fixed issue with alternative UI modes #2380
• fixed command line corruption with breakout processes #2377
• fixed issues with Privacy Enhanced box types #2342
• fixed issue with boxed object directory initialization #2342
• Sandboxie no longer leaves behind permanent directory objects
• FIXED SECURITY ISSUE ID-21 AlpcConnectPortEx was not filtered by the driver #2396
• fixed issues with program controll options #2395

 

Thank you for the new version. Firefox 106.0.x works flawlessly so far.

However, I noticed that with this Sandboxie version (1.5.1) there is a side effect when using ImDisk. If a sandbox is on a RAM disk (which is formatted NTFS) Sandboxie unfortunately always shows this new error message:

Code:

PID 2224: SBIE2227 'DefaultBox' is located on a volume which does not support 8.3 naming. This can cause issues with older applications and installers.

Is there a global setting to disable this message? At the moment I use "SbieCtrl_HideMessage=2227," as a workaround.

 

@APMichael

Confirmed SBIE2227 (using latest Imdisk Toolkit). Firefox 106.0.2 works sandboxed as intented.

 

The SBIE2227 warning also occurs with any sandbox on a SoftPerfect Ramdisk.
I have hidden this message for every sandbox because my filerootpath is on ramdisk.
I too would like to see a "global" setting to hide/disable this message.

 

SBIE2112 issue persists in 1.5.1 for Firefox and Brave on Win7 32-bit machine. No problems when roll back to 1.4.2.

 

Updated Sandboxie to 1.5.1 and Firefox to 106.0.2--seems OK initially. Just using for the browser and nothing beyond that--haven't had any problems really since SBIE updated to 1.5.0 (with general fix for videos).

 

Confirmed SBIE2227 using latest Imdisk Toolkit here too.

 

Have you read the changelog? This message is intentional!
There is a reason MSFT keeps 8.3 naming enabled for the OS partition, various older software (or new software using outdated components/libraries) may not behave correctly on a volume without 8.3 naming support.
Instead of wondering why some older installer works for me but not for someone else, now I only have to ask if there was message SBIE2227
The proper course of action here is to enable 8.3 naming for all volumes on the system.
see https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-8dot3name

 

Yes I understand, apologies for pointing out the obvious. Set SbieCtrl_HideMessage=2227 in UserSettings hides the messages globally. I have no need to enable 8.3 naming. 'Problem' solved.

 

You are right, I installed an older version over and now I can run stuff sandboxed.

 

Roboform still not working with 5.60.1 and FF 106.0.2, Windows 11 21H2 22000.1098. Error msg 1308.

 

I could not recall ever having problems with 8.3 name support. So I must also honestly admit that I was not aware that this is enabled by default only on the system volume. Please excuse my lack of knowledge in this case. I would recommend including this extended information in the changelog so no one has to ask for it again.

I have enabled the 8.3 name support for the RAM disk, see the following the confirmation:

Code:

C:\WINDOWS\system32>fsutil behavior query disable8dot3 R:

Der Volumestatus ist 0 (8dot3-Namenerstellung ist aktiviert).
Der Registrierungsstatus ist "2" (Standardeinstellung "Pro Volume").

Aufgrund der oben angegebenen Einstellungen ist die Erstellung von 8dot3-Namen auf "R:" aktiviert.

But unfortunately the error message is still shown! What now?


@Mr.X I'm very sorry that you were snapped at, even though I wrote the first post.

 

what was the last configuration roboform worked with?

 

@APMichael
your command is wrong you need something like "fsutil behavior set disable8dot3 R: 0"