Just wanted to see if this is a bug, or do other people have this problem.
Captured on Win7 x86 clean with Cameyo 2.6.1220 personal edition. Virtualization: Ram mode Isolation mode: Data.
So I capture the program, a simple copy and paste of the folder to the Program Files dir, all self contained etc, make shortcut - boom! Done. It works fine, loads etc.
But when the setting is set to "Remove all virtual data upon exit" and the check box "ask for confirmation before removal" is checked - it doesn't remove settings or prompt for the removal dialog? *im not expecting the app to be removed, just the settings - so like it was never there or run before.
I could have the wrong end of the stick here but my expected outcome was for the VOS\name of app dir to be cleaned out, so like the app was never run before. ie. VOS\name of app\CHANGES\...
%AppData%
%Common AppData%
%Local AppData%
Among other stuff to be cleaned out...like if it was never there.
Is my expected outcome correct for the setting, or have i got it totally wrong?
Your understanding of -Remove is correct. Please launch your package, exit it, and then run package with -ProcessList parameter. Are any processes listed, or do you get No active virtual apps message?
I open the app and closed it normally, in the command line I ran it with the -processlist parameter and it stated there was no running process.
Just to double check. When I exit the app (not remove it from the system) it should ask to "remove all virtual data upon exit"? So like it was never there?
The URL is correct, your looking for the 2.9 Desktop version.
Hmm, I see what you mean. I had tried it on Win 7 x64 and it removed itself after a time, but it's not removing (automatically) at all on Win7 x86. I'll have to look into it more.
The package will not ask if you want to remove the application and all of its settings & files unless you check the box in Package Editor next to Ask for confirmation before removal.
Please try this just to make sure we're experiencing the same thing; I'm not offering this as a workaround: run package on Win7 x64, exit package, and run -ProcessList parameter some seconds later. You might see a blank popup. If you do, click OK and run -ProcessList parameter again. I get a Process with a question mark. Checking the PID reveals that splwow64.exe is the running process. Click OK and see if sandbox removes itself in 3-5min.
I tried adding splwow64.exe to Exclude child processes from virtualization, but although it prevents the process from running virtualized, the sandbox still doesn't get removed.