The CachePath parameter sets the deployment system path to a cache directory for font files and stub executable files.

Because of the frequent use of font and stub executable files, ThinApp must extract files in the cache quickly and place them on the physical disk.

If you delete the cache, ThinApp can reconstruct the cache.

You can use the THINSTALL_CACHE_DIR environment variable to override the CachePath parameter at runtime. If you do not set the THINSTALL_CACHE_DIR environment variable or the CachePath parameter, ThinApp sets an initial value for the CachePath parameter based on the SandboxPath parameter. The value is set according to the following rules:

  • If the SandboxPath parameter is present in the Package.ini file and uses a relative path, the CachePath parameter uses the sandbox path and stores the cache at the same directory level as the sandbox.
  • If the SandboxPath parameter is present in the Package.ini file and uses an absolute path, or if the SandboxPath parameter does not exist in the Package.ini file, the CachePath parameter uses the %Local AppData%\Thinstall\Cache location. This places the cache directory on the local machine, regardless of where the user travels with the sandbox. ThinApp creates a Stubs directory within the cache.

Setting an Absolute Path

You can modify the CachePath parameter to use an absolute path.


Setting a Relative Path

You can set a relative path that ThinApp detects as the path relative to the directory where the application executable file resides. If the package resides in C:\VirtApps and the CachePath parameter has a value of Cache, the cache directory is C:\VirtApps\Cache.


Setting the Cache and Sandbox at the Same Directory Level

When you use a USB device and move the sandbox to the USB device, you might move the cache to the USB device to avoid interfering with the local machine. In this situation, the cache and sandbox exist in the same directory level.