This indicates there is a permission error however in this case sandboxie does not report anything. This scenario works without sandboxie error however steam goes into a game permanent update scenerio (Where the files are on the network drive) which does not happen on the local drive. There was another test installing steam in a sandbox on the c drive and storing the games on the network drive (via symbolic link) with direct access. Note running the above installers in a sandbox not on a symbolic link to a network drive work without issue. Adding Full and direct access to these folders does not make a difference. Installing an MSI file results in SBIE1212 Cannot create directory '\Device\Mup\192.168.168.2\SandboxieCache\test_sandbox' Steam however gets stuck permanently 'cleaning up'. I am able to install steam without issue. I create a 'test_sandbox' whos filerootpath C:\Sandbox\SandboxCache\%SANDBOX% I create a symbolic link at "C:\Sandbox\SandboxCache" which points to "\\192.168.168.99\SandboxieCache" No antivirus running outside of windows defender. Sandboxie was not designed to bypass software restrictions. If Valve is blocking connections, you should check online for the latest updates made to the game/ VAC system and see what changed. This doesnt seem to be a Sandboxie issue. MSI installers, my testing installers in this case is the default MinecraftInstaller.msi or 'PDF Xchange EditorV7.圆4.msi Last edited by mloveless1227 on Wed 11:47 am, edited 1 time in total. Why would sandboxie try to be writing to '\Device\Mup\192.168.168.99\Sandboxie Cache\testbox' instead of "C:\Sandbox\SandboxCache\testbox"? We have listed some of the best Sandboxie alternative for 2023: Buffer Zone. 12 Best Android Dialer Apps You Can Try in 2022. The computer has write permissions and sandboxie does indeed write there so i dont know what else to try. 5 of the Best Sandbox Applications for Windows 10. I have tried opening pipes to this directory etc but to no avail. Sandboxie does open and shows a Start.exe running, but nothing from the application. If I run it under a Standard User I get the following errors and the applications to be sandboxed never run. If I run it under an admin user, it works without issue. Note that the 'testbox' folder, reg hive and drive folder were created on the network drive.ĭeleting the contents from sandboxie is also successful. I am using the latest version 5.33.1 (64-bit) on Windows 10 Pro (64-bit) v1903. SBIE1212 Cannot create directory '\Device\Mup\192.168.168.99\Sandboxie Cache\testbox' I have created a symbolic link on my c drive "C:\Sandbox\SandboxCache" which points to "\\192.168.168.99\Sandboxie Cache" This also gives me the ability to transparently move files on the back end as the need requires. Instead of creating a new drive image (in case it corrupts etc) to store my sandboxed items i would rather store them directly on the share. On my back end i have a parity protected array and specific SSD drives that i am using as a network share. With my use case i am running sandboxie on my daily pc which is a virtual machine. Is it possible to run a sandbox on a network share? From what i can tell it should be possible but i am having no luck.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |