Home > Blogs > VMware ThinApp Blog


What’s keeping my Sandbox locked?

Best practices packaging with ThinApp includes verifying nothing is being left running, locking the Sandbox, when the end-user shuts down the application. A simple method to verify nothing is running in the background is to try to delete the package’s Sandbox. If it is locked and you cannot delete it, something is still running.

To find out what it is I always use Sysinternals Process Explorer. This video will show you how to use Process Monitor to find out what is keeping the Sandbox opened.

How to solve the issue depends on what process we’re talking about. It can for example be an auto update process that needs to be disabled or as in this example the all to common ctfmon.exe. To solve ctfmon.exe (advanced text services) simply disable it within the virtual environment by adding below to the HKEY_CURRENT_USER.txt file.

isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\CTF
  Value=Disable Thread Input Manager
  REG_DWORD=#01#00#00#00

 

Problem viewing the Video? Try this link: http://vimeo.com/channels/thinapp#22228464

This entry was posted in FAQs, Office, Tips, Troubleshooting and tagged , , , on by .
Peter Bjork

About Peter Bjork

Peter Bjork is the VMware Identity Manager, Unified Access Gateway and ThinApp Specialist covering the EMEA region. Peter came to VMware with the acquisition of Thinstall. He has many years of experience in ThinApp and is the author of the book “VMware ThinApp 4.7 Essentials” and “VMware Horizon Workspace Essentials”. Peter lives in Sweden with his wife and two kids.
You can follow Peter on Twitter: @thepeb