Symptoms
Consider the following scenario:
-
You install a COM Interop assembly by using the assembly registration tool (Regasm.exe).
-
You create a Windows Form project that targets to the Microsoft .NET Framework 4 Client Profile by using Microsoft Visual Studio 2010.
-
In the toolbox, you open the Choose Toolbox Items dialog box to select the registered COM class in the installed assembly.
-
You drag the COM class to the Windows Form project.
In this scenario, you receive an error message that resembles the following:
Failed to import the ActiveX control. Please ensure it is properly registered.
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 Web site:
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
You must have the release version of the .NET Framework 4 installed to apply this hotfix.
Restart requirement
You do not have to restart the computer after you apply the hotfix if the affected files are not being used.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
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.
For all supported x86-based versions of Windows Server 2003, of Windows XP, of Windows Vista, of Windows Server 2008, of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
SetupUi.dll |
10.0.30319.318 |
295,248 |
05-Jun-2010 |
03:53 |
x86 |
|
Setupengine.dll |
10.0.30319.318 |
809,304 |
05-Jun-2010 |
03:53 |
x86 |
|
Setup.exe |
10.0.30319.318 |
78,152 |
05-Jun-2010 |
03:53 |
x86 |
|
System.design.dll |
4.0.30319.318 |
5,078,360 |
05-Jun-2010 |
08:06 |
x86 |
For all supported x64-based versions of Windows Server 2003, of Windows XP, of Windows Vista, of Windows Server 2008, of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
SetupUi.dll |
10.0.30319.318 |
295,248 |
05-Jun-2010 |
03:53 |
x86 |
|
Setupengine.dll |
10.0.30319.318 |
809,304 |
05-Jun-2010 |
03:53 |
x86 |
|
Setup.exe |
10.0.30319.318 |
78,152 |
05-Jun-2010 |
03:53 |
x86 |
|
System.design.dll |
4.0.30319.318 |
5,078,360 |
05-Jun-2010 |
08:06 |
x86 |
For all supported IA-64-based versions of Windows Server 2003, of Windows XP, of Windows Vista, of Windows Server 2008, of Windows 7 and of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
SetupUi.dll |
10.0.30319.318 |
295,248 |
05-Jun-2010 |
03:53 |
x86 |
|
Setupengine.dll |
10.0.30319.318 |
809,304 |
05-Jun-2010 |
03:53 |
x86 |
|
Setup.exe |
10.0.30319.318 |
78,152 |
05-Jun-2010 |
03:53 |
x86 |
|
System.design.dll |
4.0.30319.318 |
5,078,360 |
05-Jun-2010 |
08:06 |
x86 |
To work around the problem, use the Gacutil.exe command to install the Interop assembly to Global Assembly Cache (GAC).
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
