check-circle-line exclamation-circle-line close-line

VMware ThinApp 5.2.4 Release Notes

ThinApp 5.2.4 | 18 SEP 2018 | Build 9964600

Check for additions and updates to these release notes.

What's in the Release Notes

ThinApp 5.2.4 is a maintenance release. This release notes covers the following topics:

What's New

The ThinApp 5.2.4 release introduces the following new features:

  • Support for Windows 10 1709 (Fall Creators Update)
  • Support for Windows 10 1803 (April 2018 Update)
  • Additional modules have been added in this release. You must copy them to the deployment machine in specific cases, as desribed below. The modules are not required during application capture:
    • For 32-bit virtual applications which crash at launch on Windows 10, copy the file dummyTLS.dll to the folder C:\Windows\SysWOW64 on a 64-bit deployment machine or to the folder C:\Windows\System32 on a 32-bit deployment machine.
    • For 64-bit virtual applications which crash at launch on Windows 10, copy the file dummyTLS64.dll to the folder C:\Windows\System32 on a 64-bit deployment machine.
    • For 32-bit virtual applications which fail to start when launched from a 64-bit ThinApped application on Windows 10, copy the file dummyNt.exe to the folder C:\Windows\SysWOW64 on a 64-bit deployment machine
  • One new parameter is available for inclusion in package.ini:
    • ReleaseShutdownLocksEarly Setting this parameter to 1 fixes an issue that could cause a process to hang during shutdown.

System Requirements and Installation

For information about system requirements and installation instructions, see System Requirements for Installing ThinApp.

Important note about installing VMware ThinApp 5.2.4
You cannot install ThinApp 5.2.4 on Windows XP, Windows 2000, or Windows Server 2003. Consider using ThinApp 5.2.3 or earlier to capture applications on these operating systems. Use ThinApp 5.2.3 or earlier to create a ThinApp project and then use ThinApp 5.2.4 (on a supported OS) to build the virtual application from the project.

Resolved Issues

The ThinApp 5.2.4 release resolves the following issues:

  • SASBEG application does not work if Sophos SafeGuard 8 is installed
    SASBEG application crashes/loses functionality if Sophos SafeGuard 8 is installed on a 32-bit version of Windows 7.

    This issue is resolved in ThinApp 5.2.4.

  • MobaXterm application fails to start on Windows 10 1703
    Copy dummyTLS.dll to C:\Windows\SysWOW64 and dummyTLS64.dll to C:\Windows\System32 folder on a 64-bit version of Windows 10 1703.

    This issue is resolved in ThinApp 5.2.4.

Top of Page

Known Issues

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

  • Virtual IE11 crashes during shutdown after IE11 security patch KB 4056568 applied.
    Workaround: Add the following parameter under general purpose parameters in Package.ini and rebuild the package:
    [BuildOptions]
    ForceTerminateThread=1

  • LibreOffice does not shut down properly on 64-bit version of Windows 8.1.
    Workaround: Add the following parameter under general purpose parameters in Package.ini and rebuild the package:
    [BuildOptions]
    ReleaseShutdownLocksEarly=1

  • Unable to insert Office objects in certain Microsoft Office applications like Excel charts in Excel, Word document in Word, PowerPoint, and so on.
    Workaround: None.

  • Internet Explorer 11 fails to start on Windows 8 and Windows 8.1.
    Workaround: None.

  • Messaging Application Programming Interface (MAPI) is not supported on Windows XP operating systems.
    Workaround: None.

  • Internet Explorer 6.0 fails to open some specific URLs.
    Workaround: Add the following parameters to Package.ini and rebuild the package:
    [BuildOptions]
    NotificationDLLs=T2embed.dll

  • If Protected View is enabled in Microsoft Excel 2013, it will fail to open files from a network share.
    Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations.

  • Microsoft Office 2010 and 2013 fail to launch when deployed to a system with Microsoft Office natively installed.
    Workaround: For more information, see KB article 2107369.

  • Unable to launch Google Chrome from a network share.
    Workaround: Add SetVirtualModuleFileNameInPeb=1 to Package.ini and rebuild the package.

  • Microsoft Visio 2010 help files are not displayed on 64-bit versions of Windows.
    Workaround: Apply the workaround in KB article 2091911.

  • 32-bit Internet Explorer 10 does not work on 32-bit and 64-bit versions of Windows 8.1.
    Workaround: None.

  • ThinApp does not support any 16-bit applications on Windows 8 machines.

  • If you attempt to start two instances of Microsoft Word 2013 or Microsoft Power Point 2013, these applications will become unresponsive.
    Workaround: None.

  • ThinApp fails to build packages on the 32-bit versions of Windows 7 if you change the Outdir parameter in the Package.ini and replace it with any of the following language characters:
    • Simplified Chinese
    • Traditional Chinese
    • Japanese
    • Korean
    Workaround: None.

  • ThinApp cannot change registry key names on 32-bit versions of Windows.
    Workaround: None.

  • When you start AutoCAD on 64-bit versions of Windows 7, the following error message is displayed:
    PresentationFontCache.exe - Application Error
    Workaround: None.

  • Visual Studio 2010 displays the following error message:
    Invalid license data. Reinstall is required on launch.
    For more information, see KB article 2091953.
    Workaround: None.

  • Unable to open Web pages using Internet Explorer 8 or later versions on Windows 10.
    Workaround: Apply the workaround provided in KB article 2137873.

  • When you mark a Web site as favorite in Internet Explorer, you cannot immediately view it in the Favorites Bar.
    Workaround: If needed, create ##Attributes.ini file in the %Common Favorites% folder with the following content and rebuild the package:
    [Isolation]
    DirectoryIsolationMode=WriteCopy

  • A Fatal Application Exit error occurs when you launch 64-bit versions of Microsoft PowerPoint 2010 or Microsoft Word 2010 on Windows 10.
    Workaround: Add the ChildProcessEnvironmentException=msiexec.exe in Package.ini and build the project.

  • A COMDLG32.dll error appears when applications are run from a network share.
    Workaround: Add ProcessExternalNameBehavior=Original and SetVirtualModuleFileNameInPeb=1 to the General Parameters section of the Package.ini and rebuild the package.

  • Microsoft Visio 2010 fails to launch when deployed to Windows 10 1803.
    Workaround: None.

Top of Page