Omnissa ThinApp Release Notes

Omnissa ThinApp | 12 Sep 2019 | Build 14449759

Check for additions and updates to these release notes.

What is in the Release Notes

Omnissa ThinApp 5.2.6 is a maintenance release and includes a few enhancements, resolved issues, and known issues:

What's New

Support for Windows 10 1903
Support for Mozilla FireFox ESR 68.
Security updates
Support for new parameters: CopyManifestData and DllNamesMap in the package.ini file.

Omnissa ThinApp Product Documentation

For more information about Omnissa ThinApp, see Omnissa Product Documentation.

Resolved Issues

Virtual applications fail if Omnissa Dynamic Environment Manager, Citrix XenApp, or Horizon View Agent are installed on the deployment machine.

Certain applications like Omnissa Dynamic Environment Manager, Citrix XenApp, or Horizon View Agent install hook DLLs in the system that might cause virtual applications to fail. The presence of any of the following hook DLLs such as vmwsci.dll, MfApHook.dll, MfApHook64.dll, FlexHook32.dll, or FlexHook64.dll might interfere with the child process creation in ThinApp causing the virtual applications to fail.

Resolution:
1. In the package.ini file, set the parameter EnableExternalHookInterception to 1.
2. Copy the following DLLs to the deployment machine:
These DLLs are not required during an application capture.
1. For 32-bit virtual applications, copy the file dummyTLS.dll from the ThinApp install location 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.
2. For 64-bit virtual applications, copy the file dummyTLS64.dll from the ThinApp install location to the folder C:\Windows\System32 on a 64-bit deployment machine.
Virtual GFRQuery application is not working with ThinApp 5.2.5

The "Detail Summary Window" of the Virtual GFRQuery application is not displayed.

Resolution:

Rebuild the package with ThinApp 5.2.6.
Applications virtualized with ThinApp when compiled with "Control Flow Guard Flag" fail to start.

Resolution:

Rebuild the ThinApp package with version 5.2.6.
Paint.NET 4.x, when virtualized by using ThinApp, fails when started on a Windows 8, Windows 8.1, or Windows 10 Virtual Machine

When an application virtualized by using ThinApp fails to start on either Windows 8, Windows 8.1, or Windows 10 machine, the following error message is displayed:
*application_name* requires Windows 7 SP1, Windows 8.1 or Windows 10.

Resolution:
1. In the General Purpose Parameters section of the package.ini file, add CopyManifestData=1.
2. Rebuild the ThinApp package.
CopyManifestData is a new parameter.
Virtual ixDrill application fails with a runtime error.

Virtual ixDrill application fails due to a runtime error.

Resolution:

In the package.ini file, add DllNamesMap=dartwe~1.dll:dartwebserver.dll.

Known Issues

Virtual IE11 fails during shutdown after IE11 security patch KB 4056568 has been applied.

Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package:
```
  `[BuildOptions]  
  ForceTerminateThread=1`
```
LibreOffice does not shut down correctly on the 64-bit version of Windows 8.1.

Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package:
```
  `[BuildOptions]  
  ReleaseShutdownLocksEarly=1`
```
Unable to insert Office objects in certain Microsoft Office applications such as Excel charts in Excel, Word document in Word, PowerPoint, and so on. ****

Workaround: None
Internet Explorer 11 does not start on Windows 8 and Windows 8.1.

Workaround: None.
Internet Explorer 6.0 does not 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, Excel fails 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 Microsoft Office 2013 fail to start when deployed to a system with Microsoft Office natively installed.
Not able to start 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.
32-bit Internet Explorer 10 does not work on Windows 8.1; both 32-bit and 64-bit versions.

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

Workaround: None.
If you replace the Outdir parameter in Package.ini with any of the following language characters, ThinApp fails to build packages on the 32-bit versions of Windows 7:
- Simplified Chinese
- Traditional Chinese
- Japanese
- Korean
Workaround: None.
ThinApp does not support any 16-bit applications on Windows 8, Windows 8.1, and Windows 10 machines.

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.

Workaround: None
Unable to open web pages by using Internet Explorer 8 or later on Windows 10.

Workaround: For information about the workaround, see the knowledge base article 2137873.
When a website is marked as favorite in Internet Explorer, the website is not seen immediately in the Favorites Bar.

Workaround: Create ##Attributes.ini file in the %Common Favorites% folder with the following content and rebuild the package:
```
  `[Isolation]  
  DirectoryIsolationMode=WriteCopy`
```
When 64-bit version of Microsoft PowerPoint 2010 or Microsoft Word 2010 on Windows 10 is started, a "Fatal Application Exit" error occurs.

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 start when deployed to Windows 10 1803

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

Workaround: None

Was this page helpful?