This could be mitigated by making the launchers check for it and install it, so that you only have to run one of them once with elevated privileges, and from that point on all other launchers would work normally.

The only problematic thing would be the Sandboxie driver, which has to be installed in order for sandboxie to work and which is very hard and impractical to make portable since admin rights are required. Data (the directory where all the generated data is stored, in this case the actual sandbox) DefaultData (data to be copied to Data on first run) Appinfo (Directory containing metadata and the launcher config)

The sandbox would be the Data directory, where all the generated data woud be stored, according to the PortableappsFormat (which I think is an ideal format for portable applications): There just needs to be a way to pack sandboxie with your portable application distribution. The way this would work would be fairly easy to implement, since all the functionality is already there in Sandboxie. It would be a much more stable and straightforward solution compared to alternatives like VMWare Thinapp or Cameyo Describe the solution you'd like Since that is the case anyway, I think it would be a great idea to just make the apps portable using Sandboxie. I have made a lot of portable applications and I always use Sandboxie to determine what sort of paths i need to put down in the config file. This solution is not so great because the packer has to be aware of all the files that an application could use, which can be a lot and easily missed. The locations of the files have to be manually specified in the launcher's config file. It works by using a launcher that moves all the files that the aplication uses arond on the system and cleans up after the app is closed. It is an utility for making applications self-contained. I'm sure most of you are familiar with the framework. Is your feature request related to a problem or use case?

Cameyo portable