Epic Games can't launch because of SBIE2101 #1872
Comments
It was released more than a year ago, I doubt the lead developer will consider it. |
|
I'll update and see how it goes |
|
try theoption with those two the instalation worked fine |
|
with Tried add "-opengl" start parameter but it crashes with another error: |
My configuration👆 (security enhanced) |
|
@ameaninglessname More specifically:
|
|
I've been running ze Epic Games Launcher in Sandboxie Classic for years. By adding this launch parameter to the shortcut with which I start ze launcher: I've also given EGS its own dedicated box with write access to ze Epic folder, like this: |
|
|
with latest version and only |
|
This is probably not related to here, but after updating, I get this error any time I try to connect: |
|
As it has been 3 months since the last activity, we are automatically closing this issue in 14 days. If it is still present, please respond to help us investigate on newer Sandboxie versions. Thank you for your contribution! |
What happened?
First of all, please don't ask why I put Epic Games in a sandbox.
Each and every time I try to launch Epic, I get this error:
EpicGamesLauncher.exe (18172): SBIE2101 CreateMutant (C0000022) access=001F0001 initialized=1This error also occurs when trying to install it in an empty sandbox.
Download link
https://store.epicgames.com/en-US/
To Reproduce
Expected behavior
I expected the launcher to launch regularly.
What is your Windows edition and version?
Windows 10 Pro 21H2 64-bit
In which Windows account you have this problem?
I use the built-in Administrator account.
Please mention any installed security software
Only Windows Defender.
What version of Sandboxie are you running?
Sandboxie Plus v0.7.2 64-bit
Is it a regression?
No response
List of affected browsers
No response
In which sandbox type you have this problem?
In a Standard isolation sandbox (yellow sandbox icon).
Where is the program located?
The program is installed only inside a sandbox (NOT in the real system anyway).
Can you reproduce this problem on an empty sandbox?
I can confirm it also on an empty sandbox.
Did you previously enable some security policy settings outside Sandboxie?
No response
Crash dump
No response
Trace log
https://pastebin.com/H7yurvxx
Sandboxie.ini configuration
[GlobalSettings] Template=BitDefenderInternetSecurity Template=7zipShellEx Template=LastPass Template=WindowsRasMan Template=Avast_Antivirus Template=WindowsLive Template=OfficeLicensing Template=OfficeClickToRun KnownConflicts={FBEB98F8-64E4-4FA3-A15E-4A9F42FF962E} FileRootPath=\??\%SystemDrive%\Sandbox\%USER%\%SANDBOX% SeparateUserFolders=y KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX% IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION% EditAdminOnly=n ForceDisableAdminOnly=n ForgetPassword=n IpcTrace=ad PipeTrace=ad GuiTrace=ad [UserSettings_11C20283] SbieCtrl_UserName=mikwee SbieCtrl_NextUpdateCheck=1616664728 SbieCtrl_UpdateCheckNotify=n SbieCtrl_ShowWelcome=n SbieCtrl_WindowCoords=1013,257,798,558 SbieCtrl_ActiveView=40021 SbieCtrl_ProcessViewColumnWidths=250,70,300 SbieCtrl_BoxExpandedView=, SbieCtrl_ShouldDeleteNotify=n SbieCtrl_AutoStartAgent=SandMan.exe SbieCtrl_EnableAutoStart=y [Zoom] ConfigLevel=8 AutoRecover=y BlockNetworkFiles=y Template=SkipHook Template=FileCopy Template=AutoRecoverIgnore Template=Firefox_Phishing_DirectAccess Template=Chrome_Phishing_DirectAccess Template=LingerPrograms Template=BlockPorts Template=WindowsFontCache Template=qWave RecoverFolder=%Desktop% RecoverFolder=%Favorites% RecoverFolder=%Personal% RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% BorderColor=#00FFFF,ttl Enabled=y [Epic_Games] Enabled=y ConfigLevel=8 AutoRecover=n BlockNetworkFiles=y RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Desktop% BorderColor=#00FFFF,ttl Template=SkipHook Template=FileCopy Template=qWave Template=BlockPorts Template=LingerPrograms Template=Chrome_Phishing_DirectAccess Template=Firefox_Phishing_DirectAccess Template=AutoRecoverIgnore [iTunes] Enabled=y ConfigLevel=8 AutoRecover=n BlockNetworkFiles=y RecoverFolder=%Desktop% RecoverFolder=%Personal% RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% BorderColor=#00FFFF,ttl Template=AutoRecoverIgnore Template=Firefox_Phishing_DirectAccess Template=Chrome_Phishing_DirectAccess Template=LingerPrograms Template=BlockPorts Template=qWave Template=FileCopy Template=SkipHook [DefaultBox] Enabled=y ConfigLevel=8 AutoRecover=n BlockNetworkFiles=y RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Desktop% BorderColor=#00FFFF,ttl Template=SkipHook Template=FileCopy Template=qWave Template=BlockPorts Template=LingerPrograms Template=Chrome_Phishing_DirectAccess Template=Firefox_Phishing_DirectAccess Template=AutoRecoverIgnore [Epic2] Enabled=y ConfigLevel=8 AutoRecover=n BlockNetworkFiles=y RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}% RecoverFolder=%Personal% RecoverFolder=%Desktop% BorderColor=#00FFFF,ttl Template=SkipHook Template=FileCopy Template=qWave Template=BlockPorts Template=LingerPrograms Template=Chrome_Phishing_DirectAccess Template=Firefox_Phishing_DirectAccess Template=AutoRecoverIgnoreThe text was updated successfully, but these errors were encountered: