VMware

VMware ThinApp 5.0 Release Notes

ThinApp 5.0 | 31 October 2013 | Build 1391583

Last Document Update: 31 October 2013

These release notes cover the following topics:

What's New

SDK
The ThinApp 5.0 introduces support for 64-bit SDK. ThinApp now provides a 64-bit SDK, ThinAppSDK64.dll for 64-bit in process COM, this eliminates the need for ThinAppSDKSrvr.exe on 64 bit Operating System. On 64 bit Operating System the user can register 64 bit SDK dll (regsvr32 ThinAppSDK64.dll) and use their scripts or applications to access ThinApp packaged data.
Registry key path change - If you use registry APIs from ThinApp SDK. for the old package the users need not change anything. However, for packages built with the ThinApp 5.0 tools, the user needs to pay attention for these registry paths. Users can query the registry key that is captured for 64-bit application as usual.

    Native - HKLM\Software\7-Zip
    ThinApp - HKLM\Software\7-Zip
    Native - HKCR\CLSID\{23170F69-40C1-278A-1000-000100020000
    ThinApp - HKCR\CLSID\{23170F69-40C1-278A-1000-000100020000
However, for the registry key captured for 32-bit application, the changes are explained in following examples.
The top line is the native 32-bit key path and the bottom line is the path that is passed to the SDK as argument.
    Redirected keys - (32-bit registry keys are redirected)
    Native - HKLM\Software\7-Zip
    ThinApp - HKLM\Software\Wow6432Node\7-Zip
    32-bit keys are redirected to Software\Wow6432Node

    Shared keys - (Shared by both 32-bit and 64-bit view)
    Native - HKLM\SOFTWARE\Clients
    ThinApp - HKLM\SOFTWARE\Clients

Inclusion of .alt file in Bin folder
The ThinApp 5.0 release adds support for an alternate architecture PDC with .alt extension. If the ThinApp capture feature contains both 32 bit and 64 bit executable, then a file with an extension *.alt * would be generated in the bin directory after build process. The pdc would generally be x86 and not suitable to launch a 64 bit process. The .alt files provide an alternate architecture PDC image to use as an entry point.

Example
Capture a 32-bit version of Office 2010 on a 64-bit version of Windows, it will install 32-bit components (winword.exe, excel.exe and so on), but it will also install a 64-bit version of the Office License Protection service (OSPPSVC.exe). Now, if you execute an Office 2010 shortcut executable (word.exe), ThinApp must also start the OSPPSVC service. With ThinApp 473 there was no shortcut executable for osppsvc.exe, ThinApp would use the PDC file as the entrypoint, as ThinApp 4.7.3 did not support 64-bit executables this was not a problem. However, in ThinApp 5.0, the PDC will be x86 and this not suitable for launching the x64 OSPPSVC.exe process, this is where .alt PDC is very useful.

New Package.ini parameters
A new package.ini option MSIIs64Bit is added to the MSI-related options. Snapshot.exe sets this option if the first app executable is 64-bit, and if MSI is enabled, tlink generates a 64-bit MSI package. This change builds a 64-bit MSI package if the captured application is 64-bit.

Another new parameter LargeAddressAware is included in ThinApp 5.0, this option is used to capture applications which install on both 32-bit and 64-bit operating systems. Set LargeAddressAware =1 to allow 32-bit applications to launch 64-bit application without any error.

Virtual CMD
By Default the ThinApp Setup capture feature captures a 32-bit virtual command prompt. However, to launch the x64 Virtual command prompt perform the following changes to the settings:

[cmd.exe] Source=%SystemSystem%\cmd.exe
 To
[cmd.exe] Source=%SystemSystem(x64)%\cmd.exe

Application Synchronization

The following changes have been made to the ThinApp AppSync process:
  • The .alt file is required for Application Synchronization of ThinApp 5.0 packages. In case of forced AppSync, if the .alt file is missing, the user will receive a message box and the downloaded file will be named as .1 update
  • If the Appsync feature uses IIS server the user needs to add .alt file to the mime types.
  • All the shortcuts, entry points and PDC's of both (old and new) applications should have the same name for a successful AppSync. Example Microsoft office word 2003.exe and Microsoft office word 2007.exe should be named as Microsoft office word.exe.

Other Enhancements in ThinApp 5.0

The following enhancements have been made in ThinApp 5.0 :
  • Conditional support for virtualizing App Sense.
  • Existing version of Horizon will work with ThinApp 5.0, 32 bit applications, but support for 64 bit applications might be available in future releases.
  • Conditional support for virtualizing 64 bit applications.
  • Previous versions of View will work with ThinApp 5.0, 32 bit applications, but support for 64 bit applications might be available in View 5.3.
  • Conditional support for virtualizing Microsoft Office 2013 and Internet Explorer 10.

For additional information about ThinApp 5.0, visit the following Web sites:

Top of Page

Prior Releases of VMware ThinApp 4

Features from prior releases of VMware ThinApp 4 are described in the release notes for each release. To view release notes for prior releases, click one of the following links:

Top of Page

Resolved Issues

The ThinApp 5.0 release resolves the following issues:

  • When you attempt to launch virtualized Microsoft Expression Studio 4, on Windows XP Service Pack 3, the application fails with the following error
    MS Expression Web 4 has encountered a problem and need to close. We are sorry for the inconvenience.... .
  • Stratis software virtualized with ThinApp 4.6 version fails to launch.
  • ClaroRead Plus V5.6 virtualized with ThinApp 4.6.1, fails to start on 32-bit Windows 7 operating system.
  • Volvo car application virtualized along with Internet Explorer 6 fails randomly. This issue occurs when the user switches from an active window of one application to another application.
  • The virtual version of Novell Groupwise client connected to Novell Groupwise Server requires constant re-authentication.
  • Virtualized QuickBooks Premier application, fails at runtime with the following error
    QuickBooks Centers is unable to locate a critical file. Please reinstall or update your QuickBooks installation.
  • When you use virtual applications with thin clients, the applications fail with Out of memory error.
  • In the virtual version of Open Office 3.11, the spell check feature for the German language does not work.
  • The virtual version of Adaptive Server Anywhere freezes on launch.
  • In a virtualized Maneuver Control System, if you attempt to start Map Manager from the Maps and Overlays option, the Map Manager function fails.
  • On a 32-bit Windows XP operating system, when you attempt to open a PDF using virtual version of Foxit reader with Firefox, the application fails with an error message.
  • When the user attempts to capture the Pacsbridge application in Windows XP Service Pack 3, with Windows 3.1 installer, the virtual version of the application fails with a .NET exception.
  • During ThinApp startup, if you attempt to use the callback feature to run some scripts, then ThinApp fails. This issue is observed on Windows Server 2008, 32-bit and 64-bit operating system.
  • Virtualized version of ThinApp does not support Side-by-Side COM object activation.
  • When you launch Clip Organizer from the virtual version of Microsoft Office 2007, the application fails with the following error
    The operating system is not presently configured to run this application.
  • On 64- bit Windows XP Service Pack 3, when you start virtual version of Internet Explorer 7 with Java6 Update7, MSI installers pop up.
  • When a user attempts to create a new trace using virtual version of SQL Profiler, the application fails with the following error
    Cannot connect to Additional information class not registered (pfutil90).
  • The ThinReg feature of ThinApp might not work, if you register ThinReg using the UNC path.
  • After you virtualize Firefox with Web developer 1.1.8 add-on using ThinApp 4.0.4. The Web developer add-on becomes incompatible with Firefox. This issue is observed on Windows XP Service Pack 2 operating system.
  • On Windows 7 operating system, the virtual version of vSCT-jrel1.6.0_16 application fails with the following authentication error
    Unable to login. Unexpected error.
  • Using the Applink feature when you set the application link to a non-primary data container, ThinApp displays a failure dialog indicating incorrect success message.
  • The ThinApp Setup capture feature displays prescan and postscan warning messages, while accessing the Perflib Sub key on Windows 7 registry.
  • MSI Package of 64-bit Application installs the virtual application in ProgramFile(x86) Directory instead of the Program Files directory.
  • Force appsync option fails if the previous application is in open state.
  • Virtual version of Adobe CS6 fails to start on View linked clone desktop.
  • On a Virtual application the appsync feature might not synchronize the .alt files. In this case you have to rename the *.alt file to n.alt where n is the number you choose for the .bat or .exe file.
  • ThinApp ThinDirect ADM Group Policy template might nor support newer Group Policy formats introduced by Microsoft.
  • When you build a 64-bit Internet Explorer application on a system with 32-bit operating system, the Internet Explorer displays an error message similar to the following:
    Explorer++.exe is not a valid windows Image. Please check against your installation diskette.
  • ThinApp installation might not accept new Horizon Suite license keys.
  • Virtual version of Internet Explorer 9.0 silently exits when you start it on Windows 8, 64-bit system.
    Workaround:
    1. Disable the DetourDialogs in Internet Explorer package.
    2. Add the following entry in HKEY_CURRENT_USER.txt in the package and rebuild

    3. isolation_writecopy HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\New Windows
      Value=DetourDialogs
      REG_SZ~no#2300

  • Setup Capture generates a HKLM file whose size is greater than 100 MB on Windows 7, 32-bit and Windows 7, 64-bit operating system.
    Workaround: Add HKEY_LOCAL_MACHINE\COMPONENT, HKEY_LOCAL_MACHINE\Schema under RegistryIgnoreList in Snapshot.ini

Known Issues

The following known issues are known to occur in the ThinApp 5.0 release:

  • When you attempt to insert non-office OLE components to virtual version of Microsoft Office 2013 applications, the application fails. This issue is observed on Windows 8 and later operating systems.
    Workaround: Add the following entry in Package.ini under [BuildOptions] section:
    ForcedVirtualLoadPaths=%SystemSystem%\mfc42u.dll
  • When you start virtual version of Microsoft Office 2013 application (64-bit and 32-bit), the applications exit displaying the installer dialog box. This issue is observed on Windows 8 and Windows 8.1 operating systems.
  • The virtual version of Internet Explorer 6.0 fails to open some specific URLs.
    Workaround: Add the following parameter in Package.ini build options
    [BuildOptions]
    NotificationDLLs=T2embed.dll
  • The virtual version of Microsoft Outlook 2010, 32 bit captured on Windows 7, 64 bit fails to start on Windows 7, Windows 8 and Windows Server 2012, 64-bit operating systems. For more information see knowledge base article 2063264
  • Toad for Oracle application fails to start when you launch it using Windows 7 64 - bit operating system or Windows 8.1 64 - bit operating system.
  • If the protected view is enabled in Microsoft Excel 2013, then the virtual version of Microsoft Excel 2013 fails to open a file from the network path.
    Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Clear Enable protected view for files located in potentially unsafe locations and Clear Enable Protected View for files located in potentially unsafe locations.
  • Microsoft Visio 2010 help files are not displayed on all 64 - bit operating system.
  • When you start virtual version of Microsoft Office 2013 (32-bit or 64-bit) on Windows 8, or Windows 8.1 operating system, the application exits with an error message.
  • When you attempt to connect the virtual version of the VMware Horizon View Client 5.3 with the desktop pool, the View client becomes unresponsive and displays the following message
    The connection server is preparing the desktop.
  • When you start virtual version of Microsoft Office PowerPoint 2013, on Windows 8.1 operating system, the application dislpays a warning message similar to the following:
    Fatal Application Exit.
  • If you set Microsoft PowerPoint as the default application for opening presentation files and then attempt to open a ppt filewith the virtualized Microsoft Powerpoint2013, the application fails.
  • In a virtualized Microsoft Office 2013 package, if you attempt to lauch the help file with the F1 key , the application displays an Installer 1719 error message. This issue is observed on Windows 7, 64-bit operating system.
  • The virtual version of Internet Explorer 9.0 becomes unresponsive when you set the homepage to in.msn.com. This issue is observed for 32-bit and 64-bit versions of Internet Explorer 9.0.
    Workaround: Add the following parameter in Package.ini build options
    [BuildOptions]
    ChildProcessEnvironmentExceptions=svchost.exe
  • Virtualized Internet Explorer 10 (32-bit) might not work on Windows 8.1 operating systems (32-bit and 64-bit).
  • The ThinDirect feature of ThinApp might not work, if you capture Internet Explorer 10 through the setup capture using the Include an entry point for the system installed IE option.
  • If the user has provided an Applink path to all the files using Regular expressions, for example RequiredApplinks=c:\Flash\bin\*; the AppLink feature will fail.
    Workaround:AppLink will display an error when any file other than an application PDC is linked to the application. For a successful AppLink, remove the .alt file from the directory. Example:When Flash is built, an .alt file is created in the bin directory. Delete the .alt file from the bin directory.
  • The ThinApp registry filenames are case sensitive, if you change the filename using the virtual command line (vCmd) ThinApp will not work.
  • When you capture Internet Explorer 9 on Windows 7 x64 through setup capture(Internt Explorer options) process, it only captures 32 bit entry point.
    1. On a clean machine run set up capture and do a prescan
    2. Install Internet Explorer 9 x64 and perform a postscan
    3. Now capture both 32 bit and 64 bit entry points
    4. After the package is ready, create a file ThinDirect.txt in the package
    5. Add the 64bit entry point (from Package.ini) Example [iexplore - 64bit.exe]
    6. Rebuild the package. Internet Explorer 9 X64 is now ready for redirection
  • The ThinApp Setup capture process might display prescan and postscan warning messages, when you attempt to save a ThinApp project. These message are benign in nature and you can ignore them.
  • The ThinApp 5.0 Beta build does not build packages containing VBscript.
  • Horizon connector (v1.5) will not recognize ThinApp 5.0 packages. This will be fixed in future Horizon release.
  • In ThinApp 5.0, the Package.ini Parameter AllowUnsupportedExternalChildProcesses might not work as expected.
  • In ThinApp 5.0, the Package.ini Parameter HidePrinters might not work as expected.
  • If you attempt to start two instances of virtual Microsoft Word 2013 or Microsoft PowerPoint 2013, the application becomes unresponsive.
  • Horizon Workspace 1.5 does not have the support necessary for reading metadata from 64 bit ThinApp binaries and is thus incompatible with ThinApp 5.0 packages. The Horizon Workspace vNext would support ThinApp 5.0 packages.
  • ThinApp fails to rebuild the project on a Windows 7, x86 English operating system, if you change the Outdir parameter in package.ini and replace it with any of the following language characters
    • Simplified Chinese
    • Traditional Chinese
    • Japanese
    • Korean
  • When you capture Internet Explorer 9 on Windows7 x64 through setup capture(Internt Explorer options) process, it only captures 32 bit entry point. For more information see knowledgebase article 2053674.
  • Issues with ThinApp 4.x and Microsoft Office 2010, see knowledgebase article 2062694.
  • Issues with ThinApp 5.x and Microsoft Office 2013, see knowledgebase article 2062691.

For more information about known issues with ThinApp packages, see the VMware Knowledge Base.

Top of Page