Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

The use of monikers is no longer supported in Internet Explorer after installing the security updates provided by cumulative security update 896727 (MS05-038)


View products that this article applies to.

Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.

↑ Back to the top


Symptoms

When you view a Web page in the products that are listed in the "Applies to" section and the Web page contains a moniker, the Web page may not work as expected. For example, an object that contains a Java moniker may not load.

This problem occurs after you install the cumulative security update that is referenced in the following Microsoft Knowledge Base article:
896727� MS05-038: Cumulative security update for Internet Explorer

↑ Back to the top


Resolution

Because of security changes that were implemented in cumulative security update 896727, the use of custom monikers is no longer enabled. A custom moniker is used to reference and create an instance of an ActiveX control or to run code. For example, these monikers include the following.
JAVA:
NEW:
SESSION:
If the application uses the Microsoft Java Virtual Machine Java moniker, use one of the following methods to enable the use of custom monikers.

Method 1: Application written in Microsoft Visual J++

To resolve this problem if the application was written in Microsoft Visual J++, convert the application to a Microsoft Visual J# application.

For more information about how to convert the Visual J++ application to a Visual J# application, visit the following Microsoft Developer Network (MSDN) Web sites:

Method 2: Application written to the Microsoft SDK for Java

To resolve this problem if the application was written to the Microsoft SDK for Java, convert the application to a Visual J# application.

For more information about how to convert the Visual J++ application to a Visual J# application, visit the following MSDN Web site:Note Other applications that use a custom moniker must be rewritten to remove the dependency on the custom moniker.

↑ Back to the top


More information

Warning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756� How to back up and restore the registry in Windows


Note These steps disable a change that was implemented in cumulative security update 896727 that prevents the use of monikers. After you follow these steps, a Web page that contains a moniker will work as expected. However, we do not recommend that you make this change because it disables part of the security update. You should only make this change temporarily until you implement one of the methods in the "Resolution" section.

To work around this problem and to enable the use of monikers, you must install the cumulative security update for Internet Explorer that is described in security bulletin MS05-052. You must also create or modify registry subkeys. To do this, follow these steps:
  1. Download and then install the cumulative security update for Internet Explorer that is described in security bulletin MS05-052. For more information about how to obtain and install this cumulative security update for Internet Explorer, visit the following Microsoft Web site:
  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then click one of the following registry subkeys:
    • To enable the use of monikers per user, click the following registry subkey:
      HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\
    • To enable the use of monikers per computer, click the following registry subkey:
      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\
  4. On the Edit menu, point to New, and then click Key.
  5. Type FEATURE_LIMIT_MONIKERS, and then press ENTER.
  6. Click FEATURE_LIMIT_MONIKERS.
  7. On the Edit menu, point to New, and then click DWORD Value.
  8. Type iexplore.exe, and then press ENTER.
  9. On the Edit menu, click Modify, type 0, and then click OK.

    Note A value of 0 enables monikers to work in an Internet Explorer process. A value of 1 disables the use of monikers.
  10. Quit Registry Editor.

↑ Back to the top


Keywords: kbqfe, kbfix, kbbug, kbhotfixserver, KB906294

↑ Back to the top

Article Info
Article ID : 906294
Revision : 3
Created on : 9/22/2011
Published on : 9/22/2011
Exists online : False
Views : 358