You open a webpage in Windows Internet Explorer 6.
The webpage hosts an ActiveX control that is developed by using version 18.104.22.168 of the Msvbvm60.dll file.
The webpage contains buttons that call methods of the object for a parent window.
You click a button, and then a modal dialog box is displayed by the ActiveX control.
In this scenario, the parent window is still disabled even if you close the dialog box.
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
After you obtain this hotfix, you must replace version 22.214.171.124 of the Msvbvm60.dll file with version 126.96.36.199 of the Msvbvm60.dll file. This file is located in the system32 folder.
Note You can back up the original file before you replace it.
There are no prerequisites for installing this hotfix.
You do not have to restart the computer after you apply the hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.