1. Hosts packaged software even if it does not have the right to do so violating the EULA fo the products.
2. Sandboxed apps leave traces on the system.
Mostly people package the software in the wrong way. When I make a virtual package I usually edit it right after the capture making it store its changes under the executable folder and delete registry traces save the registry changes in a file. (See Screenshots attached)
Guess what? it still leaves traces! it creates a registry key: HKCU\Software\VOS\
Now, I know it saves its registry settings there before deleting theme. Eg: HKCU\Software\VOS\PStart
The software should check whenever the VOS key is empty and delete it if the assumption is true. Now I've achieved that by using PortableApps.com Launcher to make portable one of those programs.
I've programmed a Launcher in AutoIT that runs a open file dialog to run an application and waits for it to finish before it exits. Here's the source.
Code: Select all
#include <FileConstants.au3>
#include <MsgBoxConstants.au3>
Local $Run = FileOpenDialog("Execute Program", @ProgramFilesDir, "Application (*.exe)|All (*.*)" , $FD_FILEMUSTEXIST + $FD_PATHMUSTEXIST )
RunWait($Run)
then I created a Launcher with PortableApps.com Launcher
I'll attach the program here.
