

Workaround: Add SetVirtualModuleFileNameInPeb=1 to Package.ini and rebuild the package. Unable to launch Google Chrome from a network share. Workaround: For more information, see KB article 2107369.

Microsoft Office 20 fail to launch when deployed to a system with Microsoft Office natively installed. Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations. If Protected View is enabled in Microsoft Excel 2013, it will fail to open files from a network share. Workaround: Add the following parameters to Package.ini and rebuild the package: Internet Explorer 6.0 fails to open some specific URLs. Messaging Application Programming Interface (MAPI) is not supported on Windows. Internet Explorer 11 fails to start on Windows 8 and Windows 8.1. Unable to insert Office objects in certain Microsoft Office applications like Excel charts in Excel, Word document in Word, PowerPoint, and so on. The following issues are known to occur in the ThinApp 5.2.1 release: When you capture a ThinApp package on Windows 7 or above with Internet Explorer 10 or 11 natively installed, Setup Capture treats all ThinApp captures as Internet Explorer captures. Setup Capture treats all ThinApp captures as Internet Explorer captures.

When you use the ThinApp SDK to read registry subkeys from a ThinApp package, the SDK returns an error if one of the subkeys is longer than 97 characters.
