VMware Horizon Community
hypermp
Contributor
Contributor

ThinApp 4.5: RemoveSandboxOnExit=1 does not work.

Hi everyone,

I've been testing the new ThinApp 4.5 and encountered a problem.

When I set in the Package.ini:

[[BuildOptions|http://communities.vmware.com/community-document-picker.jspa?communityID=&subject=BuildOptions]]

RemoveSandboxOnExit=1

I find that it does not remove the Sandbox from the user profile.

In version 4.0 it worked perfectly and removed all the files from the sandbox.

Please advise if this is a bug that will be fixed, or if I need to do something different with version 4.5.

Regards,

Richard

web:

blog:

Hyper MP - Monetize and Market your content via P2P and BitTorrent today.

Reply
0 Kudos
5 Replies
muriwai
Enthusiast
Enthusiast

Can you check if the application is still running in the background? It could be the reason of the sandbox not being removed.

Reply
0 Kudos
hypermp
Contributor
Contributor

Hi,

And thank you for your response.

I've double checked and can see that the .exe is completely closed, and there is no process within the .exe running on the system.

I did notice one thing strange though... when I run the .exe it infact shows 2 instances of the .exe running in my task manager.

I've never seen this behaviour before with ThinApp 4.0.

Please advise if there is some settings I need to change.

Regards,

Richard

Reply
0 Kudos
NickOn
Enthusiast
Enthusiast

Those two processes are needed to work well on Win7.

But I don't know what is with this sandbox option.

Reply
0 Kudos
hypermp
Contributor
Contributor

Hi,

So even if I run it on Win XP, it will still do the multiple instances run of the .exe?

Maybe the timing of the closing of the 2 .exe running processes is interfering with the RemoveSandboxOnExit=1 ?

Regards,

Richard

Reply
0 Kudos
muriwai
Enthusiast
Enthusiast

>> shows 2 instances of the .exe

That's how new ThinApp 4.5 works. Depending on certain conditions, it needs to relaunch the executable.

>>I've double checked and can see that the .exe is completely closed

I am afraid that you need to log a support request. I apologize for the inconvenince.

Reply
0 Kudos