When you try to run a custom application or try to open a Web site by using Internet Explorer 6 with SP1, the application or Internet Explorer may stop responding

You try to run a custom application or try to open a Web site by using Microsoft Internet Explorer 6 with Service Pack 1 (SP1). If the application or the Web site uses the Mshtml.dll file and JScript, the application or Internet Explorer may stop responding.

This problem occurs when the Mshtml.dll library holds a loader lock when the application tries to exit. The loader lock may prevent other threads from exiting. This behavior causes a deadlock in the application or in Internet Explorer. Therefore, the application or Internet Explorer may stop responding.

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 Web site: 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

No prerequisites are required to install this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Registry information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To enable this hotfix, you must add the following registry keys: To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE \Software\Microsoft\Internet Explorer\Main\FeatureControl
3. On the Edit menu, point to New, and then click Key.
4. Type FEATURE_JSCRIPT_EXHAUSTIVE_COLLECT_AND_100MS_DOWNLOAD_THREAD_TIMEOUT_KB915355, and then press ENTER.
5. On the Edit menu, click New, and then click DWORD.
6. Type Iexplore.exe, or type the name of the custom application, and then click OK.
7. On the Edit menu, click Modify.
8. Type 1, and then click OK.
9. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE \Software\Microsoft\Internet Explorer\Main\FeatureControl
10. On the Edit menu, point to New, and then click Key.
11. Type FEATURE_ENABLE_DXTRANS_SHUTDOWN_TIMEOUT_KB905297, and then press ENTER.
12. On the Edit menu, click New, and then click DWORD.
13. Type Iexplore.exe, or type the name of the custom application, and then click OK.
14. On the Edit menu, click Modify.
15. Type 1, and then click OK.
16. Exit Registry Editor.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: