Fallout76 crashes/exits shortly after launch with one instance already running

[Yasha613]

Describe what you noticed and did

1. Deleted content of existing sandbox
2. new sandbox with prior mimicked settings
3. 1 instance WILL function, just not more than one in or outside of the sandbox
4. Various compatablity flags set to try and return functionality.

How often did you encounter it so far?

A few seconds after launching a second instance, either inside or from outside of a sandbox

Affected program

steam game "fallout76"

Download link

Not relevant

Where is the program located?

The program is installed both inside and outside the sandbox.

Expected behavior

Expected is a very buggy game...But that can run multiple instances of.

Prior updates required using Tracelog to find files that had a seen status code of (5) with, meaning the application would crash upon not finding it, but was fast rectified. Now however I see no files at issue, it appears as though it's breaking isolation somehow and experiencing some kind of conflict upon the latest update of the game.

What is your Windows edition and version?

Windows 10 Enterprise 22H2

In which Windows account you have this problem?

A local or Microsoft account without special changes.

Please mention any installed security software

none

What version of Sandboxie are you running?

1.5.3

Is it a new installation of Sandboxie?

I have been using the same version for some time.

Is it a regression?

No response

In which sandbox type you have this problem?

In an Application Compartment sandbox with no isolation (green sandbox icon).

Can you reproduce this problem on a new empty sandbox?

I can confirm it also on a new empty sandbox.

Did you previously enable some security policy settings outside Sandboxie?

No response

Crash dump

No response

Trace log

https://ufile.io/ghzcefa2

Sandboxie.ini configuration

[GlobalSettings]
FileRootPath=\??\%SystemDrive%\Sandbox\%USER%\%SANDBOX%
KeyRootPath=\REGISTRY\USER\Sandbox_%USER%_%SANDBOX%
IpcRootPath=\Sandbox\%USER%\%SANDBOX%\Session_%SESSION%
Template=Edge_Fix
Template=WindowsRasMan
Template=WindowsLive
Template=OfficeLicensing
Template=7zipShellEx
ForceDisableSeconds=99999
NotifyForceProcessDisabled=y
NetworkEnableWFP=y
SandboxieLogon=y

[UserSettings_0C5801E2]
SbieCtrl_AutoStartAgent=SandMan.exe
SbieCtrl_EnableAutoStart=y
SbieCtrl_HideMessage=2203, *GUIPROXY_00000001; MsgId: 9 - explorer.exe [C0000034]

[DefaultBox]
Enabled=y
AutoRecover=y
BlockNetworkFiles=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#00FFFF,ttl
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=9

[steamedshit]
Enabled=y
RecoverFolder=%{374DE290-123F-4565-9164-39C4925E467B}%
RecoverFolder=%Personal%
RecoverFolder=%Desktop%
BorderColor=#00ff00,ttl,6
Template=RpcPortBindingsExt
Template=OpenBluetooth
Template=SkipHook
Template=FileCopy
Template=qWave
Template=BlockPorts
Template=LingerPrograms
Template=AutoRecoverIgnore
ConfigLevel=9
AutoRecover=y
NoSecurityIsolation=y
UsePrivacyMode=n
BoxNameTitle=n
BlockNetParam=n
CopyLimitKb=81920
RunCommand=steam|C:\Program Files (x86)\Steam\steam.exe

[ZeroModM]

This has something to do with the ESM of Fo76. In previous versions, there are three ways to read the ESM file: SteamLibrary\steamapps\common\Fallout 76\Data\SeventySix.esm Users\pc\AppData\Local\Fallout76\associated_media\Data\SeventySix.esm SteamLibrary\steamapps\common\Fallout 76\Mods\Data\SeventySix.esm However, in this version, reading \Mods\Data\SeventySix.esm has been deleted. The remaining two methods are locked and cannot be used.Maybe other isolation modes can run FO76, but it will require many system files to run very hard.
I have a question to ask DavidXanatos, what is the difference between right clicking the program to run in the sandboxie and dragging file to sandboxie to select mode? I hope to get a reply, which may be helpful to fo7 run multiple instances of a sandbox.

[DavidXanatos]

I have a question to ask DavidXanatos, what is the difference between right clicking the program to run in the sandboxie and dragging file to sandboxie to select mode? I hope to get a reply, which may be helpful to fo7 run multiple instances of a sandbox.

Aside of a different working directory there shouldn't be any differences.

[Yasha613]

Quick question (for anyone that might know), is there some documentation somewhere for the status codes a Tracelog displays? I'm just guessing when I'm looking. There's https://sandboxie-plus.github.io/sandboxie-docs/Content/TraceLog.html but nothing regarding exact meanings.

[Yasha613]

Is there anything further I can provide to help? I did upgrade to 1.6.7 a bit ago and try again with the same results.

[ZeroModM]

Access the SeventySix.bin file in the game. The second fo76 accesses the SeventySix.bin file in the same directory. If the file has been opened, it will initialize the game data thread to close the game. You should understand what is going on, but there is another way I found Under certain circumstances, the game will additionally access the Data/Data directory to find files, and the files can be read without causing exit. I don’t know under what circumstances it will be accessed.

[Yasha613]

Yeah I tried every combination I could think of from what it was listing trying to access for the usual problem files in: \Users\\AppData\Local\Fallout76* \SteamLibrary\steamapps\common\Fallout76\Data* \Users\\Documents\My Games\Fallout 76* for inside the virtual file system with the few variations it had with Data\Data and such, along with every flag I could figure might be applicable. Best I can seemly get is that instead of exiting the second instance locks until it eventually triggers a crash that triggers WER.

[Yasha613]

I got a second instance running. Just can't share any of the files it uses outside of the config file it loads within the documents folder. Within steam I moved the game to another drive, then copied it back for the unsandboxed steam. Working that way in the meantime.

[NameIsZed]

well its been 2 weeks ...

[ZeroModM]

I guess the issue has been solved, Bethesda turns off secondary access to files forces the process to close, again allowing the player to run multiple processes.

[NameIsZed]

so using sandboxie with fo76 works again ? same process as before ? was this changed with the update today?

[ZeroModM]

yes changes after today's update

[NameIsZed]

i still cant get it to work

[ZeroModM]

OpenPipePath=X:\Steam\steamapps\common\Fallout76\Data edit the configuration file to add the fo76 data file to your sandbox with the corresponding name

[NameIsZed]

so i have added OpenPipePath=X:\Steam\steamapps\common\Fallout76\Data ( with my game location) to my sandboxie ini. as far as i can tell it goes at the end of the ini. i've added the data folder with proper file structure, and mod/data folder with proper file structure. and the 3 fo76 files have been added to those folders congruently. still crashes on start up. if anyone knows a way to get fo76 multi accounts to work with sandboxie please help.

[ZeroModM]

you can send the sandbox setting ini. Maybe I can find the reason. It works normally for me.

[DavidXanatos]

I did not get any refund request via paypal, if you want a refund contact me by email and specify your order ID.

[NameIsZed]

has anyone gotten this to work ?

[Machabees]

Here's the solution that worked for me. I'm no expert so I don't fully understand this. But it seems like you need to open access to the Fallout 76.esm and fallout76.bin files in Sandboxie Plus. You do this in Sandboxies INI. So right click on the virtual Box you created in Sandboxie that contains Steam. Mine is called "Steam Fallout 76 Box" But yours is whatever you named it. Click, "Sandbox Options." Go to the bottom and Click, "Edit INI Section" Then you want to add these Lines to the INI file. I just put them right at the bottom and didn't change anything else about my INI.

OpenFilePath=Fallout76.exe,H:\Games\SteamLibrary\steamapps\common\Fallout76\Data\SeventySix.esm OpenFilePath=Fallout76.exe,H:\Games\SteamLibrary\steamapps\common\Fallout76\Data\SeventySix.bin

Obviously you need to change the file path to wherever you actually have Fallout 76 installed on your PC. NOT the Sandbox Path but the original path. That Worked for me! I'm now able to run Fallout 76 inside Sandboxie again.

[NameIsZed]

omg thank you.

[Boes0184]

my friend bought fallout 76 and when he started it up it starts up, on steam en then after 5 seconds u see, start fallout 76, so i think it crashes or something whe tryde almost everything switching drives reinstalling downloading stuff much more buth it didnt work can someone help us

duplicate of https://github.com/sandboxie-plus/Sandboxie/issues/3281#issue-1884260961

[Machabees]

Boes0184. This Github issue/workaround is specifically related to running Fallout 76 inside of Sandboxie. It doesn't sound like that's the issue you are having.