Symptoms

Consider the following scenario:

  • You use Microsoft Visual Studio 2008 Service Pack 1 (SP1) to open a Win32 application on a computer that is running a 64-bit version of Windows.

  • The Ole32.dll module is loaded multiple times.

  • You debug the Win32 application.

In this scenario, an access violation may occur. Additionally, the application crashes if the access violation occurs.

Resolution

Hotfix information

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:

http://support.microsoft.com/contactus/?ws=supportNote 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.

Prerequisites

To apply this hotfix, you must have Visual Studio 2008 SP1 installed.

Restart requirement

You have to restart the computer after you install this hotfix if an instance of Visual Studio is running.

File information

The global 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.

File name

File version

File size

Date

Time

Platform

Avvspkdh.dll

9.0.30729.5726

31,568

27-Aug-2011

15:55

x86

Avvspkdh.dll

9.0.30729.5726

37,200

27-Aug-2011

15:55

x64

Avvspkdh.dll

9.0.30729.5726

74,064

27-Aug-2011

15:55

IA-64

Mcee.dll

9.0.30729.5726

1,179,976

27-Aug-2011

15:55

IA-64

Mcee.dll

9.0.30729.5726

363,848

27-Aug-2011

15:55

x86

Mcee.dll

9.0.30729.5726

655,688

27-Aug-2011

15:55

x64

Mpishim.exe

9.0.30729.5726

22,864

27-Aug-2011

15:55

x86

Mpishim.exe

9.0.30729.5726

27,984

27-Aug-2011

15:55

x64

Mpishim.exe

9.0.30729.5726

53,584

27-Aug-2011

15:55

IA-64

Msvb7.dll

9.0.30729.5726

2,741,576

27-Aug-2011

15:55

x64

Msvb7.dll

9.0.30729.5726

4,086,600

27-Aug-2011

15:55

x86

Msvb7.dll

9.0.30729.5726

5,733,192

27-Aug-2011

15:55

IA-64

Msvsmon.exe

9.0.30729.5726

3,218,256

27-Aug-2011

15:55

x86

Msvsmon.exe

9.0.30729.5726

4,761,936

27-Aug-2011

15:55

x64

Msvsmon.exe

9.0.30729.5726

9,994,576

27-Aug-2011

15:55

IA-64

Natdbgde.dll

9.0.30729.5726

1,346,384

27-Aug-2011

15:55

x86

Natdbgee.dll

9.0.30729.5726

313,680

27-Aug-2011

15:55

x86

Status

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×