sbie2224 sandboxed program has crashed что делать
SBIE2224 Sandboxed program has crashed: CorelDRAWTechnicalSuite2020Installer.exe [CorelTrial] #239
Comments
typpos commented Dec 19, 2020
Unable to run CorelDraw Technical Suite trial installer in sandbox.
Sandbox has network access enabled.
Installer runs fine in Windows Sandbox.
Installer starts, shows a dialog, then crashes.
SBIE2224 Sandboxed program has crashed: CorelDRAWTechnicalSuite2020Installer.exe [CorelTrial]
SBIE2101 Object name not found: \Sessions\1\BaseNamedObjects\windows_webcache_counters_<9B6AB5B3-91BC-4097-835C-EA2DEC95E9CC>_S-1-5-21-798926044-1197067572-4160866668-1001, error OpenSection (C0000022) access=00000002 initialized=1
Win 10 Pro x64 build 19041.685
It’s small and publicly accessible without registering, so you should be able to easily download this to reproduce.
The text was updated successfully, but these errors were encountered:
NewKidOnTheBlock commented Dec 19, 2020 •
typpos commented Dec 19, 2020
1.) Your version of Sandboxie is years out of date
I know. I currently can’t use versions of sandboxie on production systems if not signed by an official cert.
I reproduced the same issue with Sandboxie-Plus-x64-v0.5.1.exe.
Minor notes: Doing so raised a couple of unrelated minor issues:
silvestron commented Dec 22, 2020
Unable to run CorelDraw Technical Suite trial installer
typpos commented Dec 22, 2020 •
Good thought, but I don’t think it does. It starts up, successfully extracts some UI related files (html, js, etc) to AppData\Local\Temp, and shows a dialog (crashes here). Then after user confirmation would download a 1GB zip file.
NewKidOnTheBlock commented Jan 5, 2021 •
Could you try again?
Today, after giving it another try I found that Sandboxie 5.45.2 handles downloader-type installers flawlessly.
Edit: Looks fine here: 
Spoke too soon.
It seems like Corel expects a background service to be running. 
That thing unpacked almost 7000 files in more than 2000 folders weighing in at 6GB+
So at least the downloading and installing part seems to work now.
typpos commented Jan 6, 2021
Thanks for your effort. Looks like 5.45.2 fixed the installer-bootstrapper.
I had problems with TrustedInstaller with other applications in the past, so will just have to keep using a full VM for these cases.
That thing unpacked almost 7000 files in more than 2000 folders weighing in at 6GB+
SBIE2224 Sandboxed program has crashed: steamerrorreporter.exe #231
Comments
idimo commented Dec 12, 2020
can someone help me fix this error?
The text was updated successfully, but these errors were encountered:
roflankotan commented Dec 12, 2020
cocofz commented Dec 13, 2020
Please tell me here if you solve that 🙁 PLEASE SBIE2224 Sandboxed program has crashed
idimo commented Dec 13, 2020 •
noticed that this crash steamerrorreporter.exe occurs when one of the games in the library tries to download an update or download the account configuration from the cloud
idimo commented Dec 13, 2020 •
ok I have even more errors due to running DotA 2 in the sandbox ver0.5.1
cocofz commented Dec 13, 2020
cocofz commented Dec 13, 2020
idimo commented Dec 13, 2020 •
soooo now we know that crashes are related to the latest Windows 10 updates, nice
but this does not negate the fact that these errors are on the latest version of Windows 10
not everyone can solve this problem by such a radical method as reinstalling
cocofz commented Dec 13, 2020
P.S. IF SOMEONE GET SOLUTION PLEASE WRITE THERE> THANKS>
me-20201219 commented Dec 19, 2020
I wasn’t sure if it was Sandboxie because I updated to version 5.45 the same day, but even after I reinstalled Verion 5.43.7, the problem persists.
cocofz commented Jan 19, 2021
cocofz commented Jan 19, 2021
genesisvlzqz commented Mar 31, 2021
Does anyone know if this problem has been fixed?
ntx2611 commented Oct 11, 2021
I got the same problem with my Windows 11
cocofz commented Oct 13, 2021
I got the same problem with my Windows 11
cocofz commented Oct 13, 2021
Does anyone know if this problem has been fixed?
iamb9 commented Oct 15, 2021
Hello I have the same problem in Windows 11, with Bandicam.
bdcam.exe (1016): SBI2224 Sandboxed program has crashed: bdcam.exe [Bandicam]
cocofz commented Oct 15, 2021
Hello I have the same problem in Windows 11, with Bandicam. bdcam.exe (1016): SBI2224 Sandboxed program has crashed: bdcam.exe [Bandicam]
ntx2611 commented Oct 17, 2021 •
Hello I have the same problem in Windows 11, with Bandicam. bdcam.exe (1016): SBI2224 Sandboxed program has crashed: bdcam.exe [Bandicam]
Is there any FIX?
Hello,
Normally, I can open Teams client in windows 10 without issue
but i got error message : SBIE2224 with windows 11
The current version I’m using: sandboxie-plus 0.9.6
iamb9 commented Oct 19, 2021
Hello I have the same problem in Windows 11, with Bandicam. bdcam.exe (1016): SBI2224 Sandboxed program has crashed: bdcam.exe [Bandicam]
Is there any FIX?
Hello, Normally, I can open Teams client in windows 10 without issue but i got error message : SBIE2224 with windows 11 The current version I’m using: sandboxie-plus 0.9.6
Yes. I tried on windows 8.1 pro ( didn’t install windows updates ), there’s no issues. So it’s currently incompatible with windows 11 I guess.
Comments
tutak-kat commented Sep 1, 2020
The text was updated successfully, but these errors were encountered:
FrogsInSpace commented Sep 6, 2020 •
Had the same problem after Sandboxie plus installation
tutak-kat commented Sep 7, 2020
Is it just me or someone else have the same problems?
tutak-kat commented Sep 7, 2020
With plus version I just can’t run anything sanboxed so I deinstalled plus version, rebooted and instaleled again SandboxieInstall64-v5.43 and now I can’t run anything in sandbox and constantly getting errors like this:
The instruction at 0x7739c476 referenced memory at 0x00000008. The memory could not be written.
Click on OK to terminate the program
SBIE2224 Sandboxed program has crashed: basilisk.exe [DefaultBox] by process: 2892
SBIE2224 Sandboxed program has crashed: SandboxieRpcSs.exe [DefaultBox] by process: 8152
SBIE2224 Sandboxed program has crashed: WerFault.exe [DefaultBox] by process: 7976
SBIE2224 Sandboxed program has crashed: Start.exe [DefaultBox] by process: 6124
SBIE2224 Sandboxed program has crashed: SandboxieRpcSs.exe [DefaultBox] by process: 7200
SBIE2224 Sandboxed program has crashed: WerFault.exe [DefaultBox] by process: 7912
|Name| |Process ID| |Status| |Start Time| |Path|
DefaultBox Enhanced Isolation, No Admin C:\Sandbox. \DefaultBox
_ Start.exe 2920 Running 13:16:56 C:\Program Files\Sandboxie-Plus\Start.exe
__ WerFault.exe 7404 Running 13:16:56 C:\Windows\System32\WerFault.exe
SBIE2224 Sandboxed program has crashed: SandboxieRpcSs.exe [DefaultBox]
SBIE2224 Sandboxed program has crashed: Start.exe [DefaultBox]
SBIE2224 Sandboxed program has crashed: WerFault.exe [DefaultBox]
SBIE2224 Sandboxed program has crashed: SandboxieRpcSs.exe [DefaultBox]
SBIE2224 Sandboxed program has crashed: basilisk.exe [DefaultBox]
Looks like I will have an interesting afternoon.
Проблемы с Sandbox
10 May 2018 в 16:05
10 May 2018 в 16:05 #1
Ку, при установке крякнутого сандбокса столкнулся с проблемой: выдай ошибку sbie2314 Отмена процесса WerFault.exe
Очень нужна помощь, готов отблагодарить материально
Либо подскажите, чем можно заменить сандбокс
11 May 2018 в 03:40 #3
11 May 2018 в 04:03 #4
11 May 2018 в 04:29 #5
11 May 2018 в 04:34 #6
Ку, при установке крякнутого сандбокса столкнулся с проблемой: выдай ошибку sbie2314 Отмена процесса WerFault.exe
Очень нужна помощь, готов отблагодарить материально
Либо подскажите, чем можно заменить сандбокс
Надеюсь тебя забанят
11 May 2018 в 04:41 #7
Надеюсь ты не для доты его ставишь, ибо за песок или даже виртуалку в доте активно банят. Инфа 100% проверенная.
11 May 2018 в 04:55 #8
Надеюсь ты не для доты его ставишь, ибо за песок или даже виртуалку в доте активно банят. Инфа 100% проверенная.
А как же теперь фишки с компендоса абузить с 100% вр
11 May 2018 в 09:51 #9
Объясни подробно как появляется ошибка?
1)При запуске стима из песка
2)При запуске доты после запуска стима из песка
SBIE2224 Sandboxed ASF crashes on launch (WindowsCryptographicException) #740
Comments
NewKidOnTheBlock commented Mar 31, 2021 •
Description
I’ve run ASF in Sandboxie for years, but now it crashes on launch.
Thankfully I’ve captured logfiles before and after.
Reproduction steps
Here is the log (31st March 2021):
Expected behavior
This is how the log should look from the last time it worked (March 4th 2021)
System and installed software (please provide the following information):
Windows 10 20H2 64bit
Sandoxie Classic 5.49.5
ASF 5.0.5.6
Additional context
This part specifically seems to be what causes the problem:
Afaik Sandboxie denies ASF access to the «CNG Key Isolation» Windows Service.
The text was updated successfully, but these errors were encountered:
DavidXanatos commented Mar 31, 2021
how do i configure it to do something?
starting without config works
NewKidOnTheBlock commented Mar 31, 2021 •
You need to generate 2 json files for it to work.
First the ASF.json
Head here: https://justarchinet.github.io/ASF-WebConfigGenerator/#/asf
Fill in your SteamID64 (you can find it out here)
Download the file and place it in the ASF\config\ folder
Then your Bot.json
Head here: https://justarchinet.github.io/ASF-WebConfigGenerator/#/bot
Fill in a Name, your SteamLogin (you can leave SteamPassword empty if you like) and switch to Enabled.
Download the file and place it in ASF\config\ folder as well.
-> Launch ASF in Sandboxie
DavidXanatos commented Apr 5, 2021
can you provide a working config file with some dummy account?
NewKidOnTheBlock commented Apr 7, 2021 •
The goal of ASF is to farm the trading cards from your steam account in the background. The games don’t even need to be installed. ASF is way more efficient than manually idling those games in the background.
Here comes the crux:
If I provided my ASF config here, that would mean publicly posting my Steam login name and password. Not a good idea. Besides, Steam insists on 2-Factor-Authentication. So even with the account name and password, you wouldn’t be able to successfully run ASF.
@ Sandboxie Users
Does nobody else use ASF?
NewKidOnTheBlock commented Apr 8, 2021 •
The ASF crash only happens if you have set up your accounts and try to connect
I’ve found someone with the same issue on the Steam forums. He got a reply from Archi himself:
There are a couple other people with the same crash log on the steam forum.
All of them needed to make sure that the CNG Key Isolation windows service was up and running.
Does Sandboxie block this service?
Edit: I triple-checked that the service is running. 
isaak654 commented Apr 8, 2021
There are a couple other people with the same crash log on the steam forum.
All of them needed to make sure that the CNG Key Isolation windows service was up and running.
Does Sandboxie block this service?
Try this on your sandbox:
OpenPipePath=\Device\CNG
NewKidOnTheBlock commented Apr 8, 2021 •
Thanks for the suggestion.
I put the line into the Sandbox’s config and reloaded.
The error remains the same.
NewKidOnTheBlock commented Apr 9, 2021 •
I did some digging.
Since I was absolutely positive that it worked before, I uninstalled SB 5.49.5 and reverted back to 5.47.1
—> now ASF can log in and farm as intended!
Edit: Installed 5.48.0 and found that my guess was correct.
Starting with 5.48.0, SB causes ASF to crash when trying to connect to steam
DavidXanatos commented Apr 9, 2021 •
try 5.48.0
with the following options:
OpenSamEndpoint=y
OpenDevCMApi=y
AllowRawDiskRead=y
they disable all the security fixes
NewKidOnTheBlock commented Apr 9, 2021 •
—> OpenSamEndpoint is the culprit!
DavidXanatos commented Apr 9, 2021
halleluja.
now we just must find out what exactly is the problem, please add
IpcTrace=*
to your sandboxie ini and remove the OpenSamEndpoint=y such that if fails again
than enable logging/»resource access monitor» and run the program
Once I know what opcodes cause the issue I can check if its safe to allow this particular operation generally.
Usually when blocking operations I tent to stay on the safe side, better to break something than to leave a gaping hole open, once I know where its failing I can examine that particular operation closer and research if it safe to open or no.
NewKidOnTheBlock commented Apr 9, 2021 •
Is the log safe to post here? It’s got 448 lines.
DavidXanatos commented Apr 9, 2021
the only thing it may leak is your windows user name in file paths, you can find and replace it if you are worried.
DavidXanatos commented Apr 9, 2021
Did you add IpcTrace=* and removed OpenSamEndpoint=y
because the log is missing the required entries, also i have never testes if the old UI proeprly shows the new log types,
could you use the plus UI to capture the log please.
isaak654 commented Apr 9, 2021
also i have never testes if the old UI proeprly shows the new log types
IpcTrace=* produces a lot of syscalls, so it worked for me on Classic 5.49.5.
NewKidOnTheBlock commented Apr 9, 2021 •
Forgot to add IpcTrace :/ Is this correct now?
Never used Resource Monitor before.