An application virtualized and published with Microsoft Application Virtualization (App-V) may launch and be available for user interaction for approximately 10 minutes but the SFTTray notification in the system tray remains on "Launching <Application Name> (100%)" and the application closes with the following error: The Application Virtualization Client could not launch <Application Name> 220.127.116.11
The application took too long to be ready to interact with the user, possibly
because the system was too busy. Try again in a few minutes. If the problem
persists, report the following error code to your System Administrator.
Error code: 4505C6-0B01E304-0000041E
Please note that the first 15 charactors (4505C6-0B01E304) in the error code may vary but the last 8 (0000041E) will be consistant.
When an App-V enabled application is started, the client tries to detect when the application is ready to interact with the user. In some applications (for example certain java based applications) this detection fails. After 10 minutes a timeout is triggered and the client assumes that something went wrong during the launch and terminates the application.
This detection feature can be disabled by changing the SUBSYSTEM tag from windows to console in the package OSD files. To resolve this issue, change the <SUBSYSTEM VALUE="windows"/>
XML tag in the .OSD file from windows
. This change will need to be implemented on every OSD file in the package.
This change will need to be made to every OSD file in the App-V package. If deploying packages using a Virtual Application Server a DC refresh will need to be initiated on the App-V clients to update the OSD cache.
keywords: jfb app-v Softgrid SUBSYSTEM tag Error Code 460281F-0b01f5040-000041E 40-000041E 000041E appv Open Office OpenOffice Libre Office LibreOffice ten 10 minutes Java applications graphics sub-systems: console, windows, posix, and os2 windows message pump The application took too long to be ready
for other considerations.