After you install Cumulate Update 957924 for Visual Basic 6.0 Service Pack 6, certain ActiveX controls do not load in Internet Explorer

On a computer that is running Microsoft Windows, consider the following scenario:

• You deploy an ActiveX control.
• You license the computer to use the ActiveX control by using the method that is described in the following Knowledge Base article:
  159923 How to use licensed ActiveX controls in Internet Explorer
• You install the Microsoft Visual Basic 6.0 Service Pack 6 Cumulative Update (KB957924).
• You use Windows Internet Explorer to view a webpage that contains the ActiveX control.

In this scenario, the ActiveX control does not load in Internet Explorer. You see a red X instead of the control on the page.

Note This problem occurs in the following ActiveX controls:

• {1E216240-1B7D-11CF-9D53-00AA003C9CB6} - Microsoft Animation Control, version 5.0 (SP2)
• {3A2B370C-BA0A-11d1-B137-0000F8753F5D} - Microsoft Chart Control 6.0 (SP6) (OLE DB)
• {B09DE715-87C1-11d1-8BE3-0000F8754DA1} - Microsoft Animation Control 6.0 (SP6)
• {cde57a43-8b86-11d0-b3c6-00a0c90aea82 } - Microsoft DataGrid Control 6.0 (SP6) (OLE DB)
• {6262d3a0-531b-11cf-91f6-c2863c385e30} - Microsoft FlexGrid Control, version 6.0 (SP6)
• {0ECD9B64-23AA-11d0-B351-00A0C9055D8E} - Microsoft Hierarchical FlexGrid Control 6.0 (SP6) (OLE DB)
• {C932BA85-4374-101B-A56C-00AA003668DC} - Microsoft Masked Edit Control, version 6.0 (SP6)
• {248dd896-bb45-11cf-9abc-0080c7e7b78d} - Microsoft WinSock Control, version 6.0 (SP6)

The Visual Basic 6.0 Service Pack 6 Cumulative Update (KB957924) updates all the legacy Microsoft Visual Basic ActiveX controls to "phoenix bit." When controls are updated to phoenix bit, the controls use new CLSIDs (phoenix bit and kill bit). This problem occurs for the following reasons:�

• The original license package (.lpk) files that are redistributed by users are using the old CLSIDs of the controls.
• The license manager of Internet Explorer (Licmgr10.dll) does not follow the phoenix chain for looking up alternative CLSIDs that can be used.�

This issue should not be specific to the Visual Basic ActiveX controls. In theory, this issue occurs with any licensed and phoenix-bitted controls that have already previously been deployed.

Note In a reference to the mythological creature, the AlternateCLSID setting is also known as the "phoenix bit" because it enables controls that were "killed" (blocked) to "live again" (load).

Security update information

To resolve this problem, install the most recent cumulative security update for Windows Internet Explorer. To do this, visit the following Microsoft website: For more technical information about the most recent cumulative security update for Windows Internet Explorer, visit the following Microsoft website: Note� This update was first included in security update 2360131 (MS10-071).� For more information, click the following article number to view the article in the Microsoft Knowledge Base:

For more information about how managing ActiveX Control loading, visit the following Microsoft website: For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: