search

sandboxie-plus / Sandboxie

Sandboxie Plus & Classic
https://Sandboxie-Plus.com
GNU General Public License v3.0
13.69k stars 1.52k forks source link

SBIE2181 and SBIE2112 error when I open Windows Explorer #3805

Closed Editird closed 6 months ago

Editird commented 6 months ago

Describe what you noticed and did

I tried:

  1. Open Sandboxie-Plus v1.13.4
  2. Right-click any box (Default Box, New Box)
  3. Select Run -> Standard Applications -> Windows Explorer
  4. Wait a bit, it shows "WerFault.exe"
  5. Then, the Application is closed

SBIE messages: SBIE2112 Object is not accessible: \KnownDlls\kernel32.dll, call OpenSection (C0000022) access=0000000D initialized=0 SBIE2181 LowLevel.dll detour failed to load SbieDll.dll into target process. SBIE2112 Object is not accessible: \KnownDlls\kernel32.dll, call OpenSection (C0000022) access=0000000D initialized=0

the Sandboxie-Plus app Install Path is in C drive

Spec: CPU: i5-4460 GPU: GTX 660 RAM: 8GB DDR3 SSD: 120GB HDD: 500GB

How often did you encounter it so far?

Always

Expected behavior

Explorer can show folders and files

Affected program

Windows Explorer

Download link

Not relevant

Where is the program located?

The program is installed only inside a sandbox (NOT in the real system anyway).

Did the program or any related process close unexpectedly?

No, not at all.

Crash dump

No response

What version of Sandboxie are you running now?

Sandboxie-Plus v1.13.4

Is it a new installation of Sandboxie?

I recently did a new clean installation.

Is it a regression from previous versions?

No response

In which sandbox type you have this problem?

In a standard isolation sandbox (yellow sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

What is your Windows edition and version?

Windows 10 Pro 22H2 (OS Build 10.0.19045.4291) 64bit

In which Windows account you have this problem?

A local account (Administrator).

Please mention any installed security software

Windows Security

Did you previously enable some security policy settings outside Sandboxie?

No

Trace log

No response

Sandboxie.ini configuration

#
# Sandboxie configuration file
#

[GlobalSettings]
Template=7zipShellEx
Template=Edge_Fix
Template=OfficeClickToRun
Template=OfficeLicensing
Template=WindowsLive
Template=WindowsRasMan
DefaultBox=DefaultBox
FileRootPath=\??\%SystemDrive%\Sandbox\%USER%\%SANDBOX%
KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX%
IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION%

[UserSettings_08DA01C0]
SbieCtrl_AutoStartAgent=SandMan.exe -autorun
BoxGrouping=:DefaultBox,New_Box

[DefaultBox]
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#00ffff,ttl,6
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=10
BlockInterferePower=y
ForceProtectionOnMount=n
UseFileDeleteV2=y
UseRegDeleteV2=y
UseVolumeSerialNumbers=y

[New_Box]
Enabled=y
BlockNetworkFiles=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#02f6f6,ttl
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=10
FileRootPath=D:\MainBox_Sandboxie
UseFileDeleteV2=y
UseRegDeleteV2=y
UseVolumeSerialNumbers=y
AutoRecover=y
Editird commented 6 months ago

I think I found a solution

  1. Various Options -> Compatibility -> Check the option "Disable the use of RpcMgmtSetComTimeout by default"
  2. Advanced Options -> Tracing -> Check all option of Access Tracing