Error message when you run an application that uses the per-user class registration feature on a computer that is running Windows Vista or Windows Server 2008: "Interface not found"

You have an application that uses the per-user class registration feature. However, the application does not run on a computer that is running Windows Vista or Windows Server 2008. Additionally, you may receive the following error message:

This problem occurs because, in Windows Vista and in Windows Server 2008, the Automation integrity checks do not enable HKEY_CURRENT_USER (HKCU) access if the TokenIntegrityLevel registry entry is greater than medium. This may cause failures in some cases in which applications rely on the per-user class registration feature. This includes applications that are running under non-administrative accounts or administrative accounts together with the User Access Control (UAC) disabled.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix to a computer that is running Windows Vista, you must have Windows Vista SP1 or Windows Vista SP2 installed.

No prerequisites are required for computers that are running Windows Server 2008.

Restart requirement

You must restart the computer after you apply this hotfix.

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.

Windows Vista and Windows Server 2008 file information notes

The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2008 and of Windows Vista

For all supported x64-based versions of Windows Server 2008 and of Windows Vista

For all supported IA-64-based versions of Windows Server 2008

To work around this problem, you can register the component under the HKEY_LOCAL_MACHINE hive.

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

In Windows Vista and in Windows Server 2008, any application that is running at a level that is greater than the medium Integrity level is considered elevated. Services that run as a built-in service account run at the system integrity level. Service logon accounts that are not built-in run at the high integrity level. Therefore, any service that is running at a level that is greater than the medium Integrity level is considered elevated. The Automation integrity checks do not enable access to the HKEY_CURRENT_USER hive for the applications that are considered elevated. This behavior caused some per-user registration scenarios not to work as expected.

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported x86-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported x64-based versions of Windows Server 2008 and of Windows Vista

Additional files for all supported IA-64-based versions of Windows Server 2008