Internet Explorer 11 WebOC application freezes because of memory leak in Windows

This article describes an issue in which Internet Explorer 11 Web Object Control (WebOC) application freezes in Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2012, Windows 7 Service Pack 1 (SP1), or Windows Server 2008 R2 SP1. A hotfix is available to resolve this issue. Before you install this hotfix, check out the Prerequisites section.
Symptoms
When a page is loading in a WebOC control, a memory leak may occur. Eventually, the WebOC application freezes.
Resolution

Method 1: Windows Update

This update for Windows 10 is available through Windows Update and will be downloaded and installed automatically.

Method 2: Microsoft Update Catalog

To get the stand-alone package for this update, go to the Microsoft Update Catalog website.

Method 3: Hotfix

Hotfix information

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Windows 7 Service Pack 1 or Windows Server 2008 R2 Service Pack 1

To apply this hotfix, you must have Service Pack 1 installed on Windows 7 or Windows Server 2008 R2.

Additionally, you must first install the following update, and then restart the computer: Windows 8.1 or Windows Server 2012 R2

To apply this hotfix, you must first install the following updates, and then restart the computer:

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Jscript9.dll11.0.9600.180064,520,44806-Aug-201516:28x86
Jscript9diag.dll11.0.9600.17840620,03223-May-201503:04x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Jscript9.dll11.0.9600.180065,923,32806-Aug-201517:34x64
Jscript9diag.dll11.0.9600.17840814,08022-May-201518:47x64
Jscript9.dll11.0.9600.180064,520,44806-Aug-201516:28x86
Jscript9diag.dll11.0.9600.17840620,03223-May-201503:04x86

Windows 7 and Windows Server 2008 R2 file information and notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Jscript9.dll11.0.9600.179954,520,44824-Jul-201516:49x86
Jscript9diag.dll11.0.9600.17995620,03224-Jul-201517:06x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Jscript9.dll11.0.9600.179955,923,32824-Jul-201518:23x64
Jscript9diag.dll11.0.9600.17995814,08024-Jul-201518:29x64
Jscript9.dll11.0.9600.179954,520,44824-Jul-201516:49x86
Jscript9diag.dll11.0.9600.17995620,03224-Jul-201517:06x86

Additional file information

Additional file information for Windows 8.1 and Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_449b241c9b6f7486f0ddca84a543d2c3_31bf3856ad364e35_11.0.9600.18006_none_37533aab41c51257.manifest
File versionNot applicable
File size708
Date (UTC)07-Aug-2015
Time (UTC)21:21
PlatformNot applicable
File nameX86_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.0.9600.18006_none_ebe896e8e837a872.manifest
File versionNot applicable
File size72,710
Date (UTC)07-Aug-2015
Time (UTC)21:24
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File propertyValue
File nameAmd64_3520f7b245a8d7838b8792291f61118d_31bf3856ad364e35_11.0.9600.18006_none_f7816d121e51a84f.manifest
File versionNot applicable
File size712
Date (UTC)07-Aug-2015
Time (UTC)21:21
PlatformNot applicable
File nameAmd64_d259f45b7214def26d902bdd8e3b416f_31bf3856ad364e35_11.0.9600.18006_none_f78cab174f359971.manifest
File versionNot applicable
File size1,065
Date (UTC)07-Aug-2015
Time (UTC)21:21
PlatformNot applicable
File nameAmd64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.0.9600.18006_none_4807326ca09519a8.manifest
File versionNot applicable
File size72,714
Date (UTC)07-Aug-2015
Time (UTC)21:28
PlatformNot applicable
File nameWow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.0.9600.18006_none_525bdcbed4f5dba3.manifest
File versionNot applicable
File size72,712
Date (UTC)07-Aug-2015
Time (UTC)21:28
PlatformNot applicable
Additional file information for Windows 7 and Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
File propertyValue
File nameX86_485a713d2fd20c01846c1a65ddd0cb64_31bf3856ad364e35_11.2.9600.17994_none_b0be6b5162ebbbe0.manifest
File versionNot applicable
File size708
Date (UTC)31-Jul-2015
Time (UTC)17:48
PlatformNot applicable
File nameX86_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.2.9600.17994_none_ca3353aa1a840adf.manifest
File versionNot applicable
File size72,911
Date (UTC)31-Jul-2015
Time (UTC)17:07
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File propertyValue
File nameAmd64_9ad68e4d7e14609298981bbff978cd97_31bf3856ad364e35_11.2.9600.17994_none_8719c384c56d5ce1.manifest
File versionNot applicable
File size1,065
Date (UTC)31-Jul-2015
Time (UTC)17:48
PlatformNot applicable
File nameAmd64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.2.9600.17994_none_2651ef2dd2e17c15.manifest
File versionNot applicable
File size72,915
Date (UTC)30-Jul-2015
Time (UTC)18:38
PlatformNot applicable
File nameWow64_microsoft-windows-scripting-jscript9_31bf3856ad364e35_11.2.9600.17994_none_30a6998007423e10.manifest
File versionNot applicable
File size72,913
Date (UTC)30-Jul-2015
Time (UTC)17:48
PlatformNot applicable

Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
See the terminology that Microsoft uses to describe software updates.
Properties

Article ID: 3082849 - Last Review: 09/08/2015 17:15:00 - Revision: 2.0

Windows 10, Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Standard, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows 8.1 Enterprise, Windows 8.1 Pro, Windows 8.1, Windows Server 2008 R2 Service Pack 1, Windows 7 Service Pack 1

  • kbqfe kbsurveynew kbfix kbhotfixserver kbautohotfix kbexpertiseadvanced KB3082849
Feedback