Sandboxie Support

... E:\Sandbox\%SANDBOX% so programs wont see it. And cant move everything to C because its an 120gb SSD and will fill up. Also read about a Windows symlink trick, but prefer to wait for an update. If you want me to try something, just tell... Thanks

... the zzzz Box or the yyyy Box You will get SBIE1241 How to fix SBIE1241 1. Open cmd and change directory to C:\Sandbox\Administrator\ 2. create a symlink for zzzz: type "mklink /D zzzz D:\zzzz" and delete "FileRootPath=D:\zzzz" for Box "zzzz" do not delete "FileRootPath=D:\yyyy" 3. start any program ...

Hello Hardlinks,

Here are some related posts:

search.php?keywords=symlink
search.php?keywords=hardlink

What is the issue that you are experiencing, exactly? And what posts are you referring to?

Regards,
Barb.-

... for them (this is probably why you cannot finish installing your apps), which kind of defeats the purpose of running things in a Sandbox). The symlink behavior was the same as with the root folder change. However, the performance will degrade a lot when using this setup, just to keep in mind. ...

Support for 'using' junctions and symbolic links was added in later 4.x versions, I believe, and I've used it myself in the past on my real system. In fact I currently have a couple persistent boxes where I created junctions for certain folders due to an oddity in how sandboxie handles appdata paths...

Hi, I'm using scoop package manager inside a sandbox, and it relies on mklink /j or mklink /d logic - neither seem to function properly under Sandboxie. Is there any chance that symlinks / junctions are going to be supported? Sandboxie 5.20 Windows 10 Pro v1703 x64 Registered Sandboxie user. Thanks,...

... drive There are several NTFS volumes mounted into paths like C:\HDD1\1 (disk administration "use empty ntfs folder" to mount the drive) There is a symlink (not junction) C:\worktmp pointing to C:\HDD1\1\worktmp Saving to such locations (that are located on mounted volumes) has stopped working in ...

... e) Every drive formatted in NTFS. I gave direct access to folder with HB or to sandboxed folder; tried to start HB from sandbox folder; created symlinks between sandbox and working folder; sandbox was moved to C:\ drive or D:\ or flash drive. Every time seen System.Exception: Could not setup ...

solved through other way (launch skype with parameters)

/datapath:"Data" /removable /secondary

Server 2012 isn't officially supported for SBIE. http://www.sandboxie.com/index.php?Freq ... quirements

However, I know MS made some changes to Skype in the most recent Fast Ring build in Win10 that made it part of Metro Apps, if that applies to Server 2012, then Skype may not work.

... this folder (with profiles and other data): C:\Sandbox\Administrator\Permanent\user\current\AppData\Roaming\Skype\ to another location through symlink this idea works for all sandboxed programs (firefox, thunderbird, etc) but not for skype. i see skype process in sandbox and see no interface. ...

... profile on C. Do not execute the MKLINK cmd inside the Sandbox nor from a working directory within its paths. Yes, this is what I tried - the symlink works perfectly fine outside the sandbox, but sandboxie seem to not like them. then select to allow Firefox items out of that sandbox [...] ...

Every instance of Firefox "knows" where its profile folder is located. If it didn't "know", then when it ran it would create a new profile folder and files in the default location. Therefore, if you tell firefox.exe on a shortcut's command line (using the Target box) which profile you want it to use...

... from the get go that you want to share the Sandbox profile: (So, like, why create yet another profile?) But we don't know why you'd want to symlink a new folder on C: with your profile on F: when you could just create a program shortcut (if that's what you want to do, use the thing) there ...

And how does that help me?

Then I have a profile on c:\... and as soon as I start this FF sandboxed with this profile and save something like a bookmark it will be written to f:\sandbox\\sandboxname\drive\c\...
So it is on f:\ again.