This article was previously published under Q316911
This article has been archived. It is offered "as is" and will no longer be updated.
After you install a Windows Installer-based setup package that uses the Oleaut32.msm file on Windows 2000 or Windows XP, a Windows Installer dialog box that shows a progress indicator may unexpectedly appear when programs are running.
The Oleaut32.msm file that is included with Visual Studio 6.0 writes registry keys on Windows 2000 and Windows XP that should not be written because the Oleaut32.dll file is under NTFS? system file protection. Only a Windows service pack should update these registry keys.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Visual Studio 6.0 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix has the file attributes (or later) 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 tool in Control Panel.
Date Size File name --------------------------------- 8-FEB-2002 498,688 Oleaut32.msm
Microsoft has confirmed that this is a problem in Visual Studio 6.0.