If I install sandbox+ on computer #2 (not the main one), exactly the same version as on my main computer #1, then on computer #2, where there are no sandboxes with files yet, I copy the sandbox folder from computer #1 from the disk where the sandboxes themselves are located, will everything work, will sandboxes appear in the program?
Can I copy sandboxes to another computer?
- Thread starter zawedodik
- Start date
No, it won't work only by copying the files, you would have to copy the configuration for the sandboxes that are located in the Sandboxie.ini, which is usually located in C:\Windows.
Sandboxie-Plus has an export and import feature, where you can export to an archive (7z and starting with 1.14.8 zip can be used as well.) and import it on another machine. (1.14.8 has an issue, when you set a password, this will be fixed in the next release.)
Edit: To use the export feature, right click onto a sandbox, select Sandbox Tools > Export Box. And to import, click on the menu item "Sandbox" and select "Import Box"
Sandboxie-Plus has an export and import feature, where you can export to an archive (7z and starting with 1.14.8 zip can be used as well.) and import it on another machine. (1.14.8 has an issue, when you set a password, this will be fixed in the next release.)
Edit: To use the export feature, right click onto a sandbox, select Sandbox Tools > Export Box. And to import, click on the menu item "Sandbox" and select "Import Box"
Thanks for the help, but unfortunately it didn't work for me. I exported sandboxes from machine number 1, transferred these archives to machine number 2, on machine number 2 I installed the same program that I was going to run in the sandbox, the same version of the sandbox, I import the sandbox there, open it and nothing opens, the program process just stops and nothing appears.
what could be the problem? The only differences are that machine number 1 has Windows 10, and machine number 2 has Windows 11, and the user names are different, maybe something needs to be replaced in some config?
And also when importing it is suggested to select a user root folder, maybe this should be selected? If so, then should I just select the user folder or the full path to the program that should open in the sandbox?
I have never exported and imported boxes between machines, nor have I used this feature, beside using it to test the feature.
By default, Sandboxie, separates the user folders, when you create a new sandbox. This could be a problem when you have different users, as many programs store configuration user-depended and sometimes even the binaries are stored in the user folder.
It should not matter, where the box is stored, as long as the drive has enough space to contain the contents of the box and it will be readable for the user that is supposed to run it.
By default, Sandboxie, separates the user folders, when you create a new sandbox. This could be a problem when you have different users, as many programs store configuration user-depended and sometimes even the binaries are stored in the user folder.
It should not matter, where the box is stored, as long as the drive has enough space to contain the contents of the box and it will be readable for the user that is supposed to run it.
@DavidXanatos, can you detail how this is supposed to work in the context the user describes?
Containers with the Viber messenger client for PC, after importing to machine number 2, simply do not open, there are no errors, the process simply stops immediately after launch
That is, as I understand it, I need all the paths and user name on machine number 2 to match the same as on machine number 1 from which I exported containers?
This should not be the case, but I don't see why it fails.
I am not sure if that is a requirement, since I am not aware how the feature is intended to work for such cases, which is why I mentioned David, to let him give more insight.
I understand that it shouldn't be like this, for the sake of purity of the experiment I exported the container on the first machine, deleted it from Sandboxie, and then imported it back, so everything works.
So maybe the problem is that the second machine has Windows 11, although it looks like Windows 10, but maybe something is different