User`s guide

ThinApp blocks any attempt by a captured application to inject itself into a native application. The captured
application can still inject itself into virtual applications running in the same sandbox. ThinApp does not
display the default parameter in the Package.ini file.
When ThinApp blocks a captured application from injecting itself into a native application, Log Monitor
generates trace logs that refer to the AllowExternalProcessModifications parameter.
Example: Supporting Write Operations From Virtual Processes to Native
Processes
You can add the AllowExternalProcessModifications parameter to the Package.ini file to support write
operations from virtual processes to native processes. For example, a speech recognition application must inject
itself into native applications to voice the text.
[BuildOptions]
AllowExternalProcessModifications=1
AllowUnsupportedExternalChildProcesses
The AllowUnsupportedExternalChildProcesses parameter specifies whether to run 64-bit child processes in
the physical environment.
ThinApp runs 64-bit applications in the physical environment because ThinApp does not support 64-bit
processes and cannot virtualize a 64-bit application.
ThinApp sets an initial value for the AllowUnsupportedExternalChildProcesses parameter that runs 64-bit
applications in the physical environment. You can run 64-bit child process tasks on applications that run on
64-bit systems. Running a print spooler is an example of a 64-bit child process task.
Example: Blocking ThinApp from Generating 64-bit Child Processes Outside the
Virtual Environment
To protect the physical file system from any changes, you can modify the
AllowUnsupportedExternalChildProcesses parameter and block ThinApp from generating 64-bit child
processes outside the virtual environment. ThinApp cannot run any 64-bit processes because ThinApp does
not support the processes in the virtual environment.
[BuildOptions]
AllowUnsupportedExternalChildProcesses=0
AutoShutdownServices Parameter
The AutoShutdownServices parameter controls whether to shut down virtual services when the last non-service
process exits.
ThinApp sets an initial value to stop virtual services when the last non-service process exits. The parameter
does not affect services outside the virtual context.
Example: Keeping a Virtual Service Running After the Application Exits
You can modify the AutoShutdownServices parameter when you run Apache Web Server and want to keep the
virtual service running after the application that starts the service exits.
[BuildOptions]
AutoShutdownServices=0
ThinApp Package.ini Parameters Reference Guide
44 VMware, Inc.