Start.exe triggers SBIE2334 Cannot load DLL file

[maxphil]

Hello experts,

I'm having problems using SandboxiePortable on Windows 7 Ultimate 32bits. It's a clean Windows install, without any anti-virus software or any other software for that matter.

I'm using SandboxiePortable to install Sandboxie 3.64 (32bits) on a USB memory stick (drive E). After the installation finished, I execute

Code: Select all

E:\SandboxiePortable\SandboxiePortable.exe

and I can see that sandboxie is silently installed at:

Code: Select all

E:\SandboxiePortable\App\Sandboxie

After waiting for a couple of seconds, SbieCtrl.exe opens and shows on systray. Everything seems to be OK so far, so I right click on the systray icon > DefaultBox > Run Any Program and doesn't matter what application I try to open, even notepad.exe makes a new window pops up saying:

SBIE2334 Cannot load DLL file: ADVAPI32.dll
SBIE2304 Initialization failed for process SandboxieRpcSs.exe
SBIE2204 Cannot start sandboxed service RpcSs (FFFFFFFF)

and this happens every single time. I tried rebooting my system, reinstalling Windows, and nothing seems to solve the problem. I'm also sure that there is a ADVAPI32.dll inside System32.

Resource Access Monitor reports:

(Drive) \Device\CdRom0
(Drive) \Device\Floppy0
(Drive) \Device\HarddiskVolume1
(Drive) \Device\HarddiskVolume2
(Unk) 00000002 \Device\CdRom0
(Unk) 00000022 \Device\SandboxieDriverApi
Clsid -------------------------------
File/Key -------------------------------
File/Key X \Device\Floppy0
File/Key X \Device\HarddiskVolume1
File/Key X \Device\HarddiskVolume1\Program Files
File/Key X \Device\HarddiskVolume1\Users
File/Key X \Device\HarddiskVolume1\Users\Administrador\Desktop
File/Key X \Device\HarddiskVolume1\Windows
File/Key X \Device\HarddiskVolume1\Windows\System32\WindowsPowerShell
File/Key X \Device\HarddiskVolume2
File/Key X \Device\HarddiskVolume2\SandboxiePortable
File/Key X \Device\MountPointManager
Image -------------------------------
Image *:\sandboxieportable\app\sandboxie\sandboxierpcss.exe
Image *:\sandboxieportable\app\sandboxie\start.exe
Image c:\windows\system32\advapi32.dll
Image c:\windows\system32\comdlg32.dll
Image c:\windows\system32\gdi32.dll
Image c:\windows\system32\imm32.dll
Image c:\windows\system32\kernel32.dll
Image c:\windows\system32\kernelbase.dll
Image c:\windows\system32\lpk.dll
Image c:\windows\system32\msctf.dll
Image c:\windows\system32\msvcrt.dll
Image c:\windows\system32\ntdll.dll
Image c:\windows\system32\ole32.dll
Image c:\windows\system32\rpcrt4.dll
Image c:\windows\system32\sechost.dll
Image c:\windows\system32\shell32.dll
Image c:\windows\system32\shlwapi.dll
Image c:\windows\system32\user32.dll
Image c:\windows\system32\usp10.dll
Image c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc\comctl32.dll
Image e:\sandboxieportable\app\sandboxie\sbiedll.dll
Image e:\sandboxieportable\app\sandboxie\sbiemsg.dll
Ipc -------------------------------
Ipc \Sessions\1\BaseNamedObjects\SBIE_DummyEvent_308
Ipc \Sessions\1\BaseNamedObjects\SBIE_DummyEvent_492
Ipc \Sessions\1\BaseNamedObjects\SBIE_ServiceInitComplete_RpcSs
Ipc O \KnownDlls\advapi32.dll
Ipc O \KnownDlls\kernel32.dll
Ipc O \KnownDlls\KERNELBASE.dll
Ipc O \KnownDlls\MSVCRT.dll
Ipc O \Sessions\1\Windows\ApiPort
Ipc O \Sessions\1\Windows\SharedSection
Pipe -------------------------------
WinCls -------------------------------

[tzuk]

You have some X's in the File/Key lines in your log.

Code: Select all

File/Key X \Device\Floppy0
File/Key X \Device\HarddiskVolume1
File/Key X \Device\HarddiskVolume1\Program Files
File/Key X \Device\HarddiskVolume1\Users
File/Key X \Device\HarddiskVolume1\Users\Administrador\Desktop
File/Key X \Device\HarddiskVolume1\Windows
File/Key X \Device\HarddiskVolume1\Windows\System32\WindowsPowerShell
File/Key X \Device\HarddiskVolume2
File/Key X \Device\HarddiskVolume2\SandboxiePortable

Looks like the program in the sandbox is not permitted access to anything on the drive. Obviously if we can't access C:\Windows then it can't load Windows DLLs, and it fails. Either you have Sandboxie settings that block off access to drive C, or you have some conflict with some other software which is causing this.