If you attempt to start two instances of Microsoft Word 2013 or Microsoft Power Point 2013, these applications become unresponsive. Workaround: Apply the workaround in KB article 2091911.ģ2-bit Internet Explorer 10 does not work on Windows 8.1 both 32-bit and 64-bit versions. Microsoft Visio 2010 help files are not displayed on 64-bit versions of Windows. Workaround: Add SetVirtualModuleFileNameInPeb=1 to Package.ini and rebuild the package. Not able to start Google Chrome from a network share. Workaround: For more information, see KB article 2107369. Microsoft Office 2010 and Microsoft Office 2013 fail to start 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, Excel fails to open files from a network share. Workaround: Add the following parameters to Package.ini and rebuild the package: Internet Explorer 6.0 does not open some specific URLs. Internet Explorer 11 does not start on Windows 8 and Windows 8.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: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package:
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: Virtual IE11 fails during shutdown after IE11 security patch KB 4056568 has been applied. ThinApp applications fail to launch on Wind64-bit systems, which have Microsoft Security Patch KB4592438 installed.
As a result, the Firefox application fails. When the Firefox user profile setting is set to level 1, the Firefox package is unresponsive. The applications might report an access violation exception in the event log, but fail to display the corresponding UI dialog box.įollowing is the sample of an access violation exception in the event log: Faulting application name: SampleExeName, version: x.x.x.x, time stamp: 0xxxxxxxxxįaulting module name: COMCT元2.dll, version: 5.xx.xxxxx.xxxx, time stamp: 0xxxxxxxxx In Windows 8.1 and later, virtualized applications fail to display certain GUI components.
0 kommentar(er)
