HKEY_CLASSES_ROOT

HKCR

Description

The HKEY_CLASSES_ROOT subtree contains two types of data:

• Data that associates file types with programs. The file type subkeys in HKEY_CLASSES_ROOT have the same name as the file name extension for the file type, such as .exe. File type associations are stored in the registry, but you should use Windows Explorer to change them. In Windows Explorer, from the Tools menu, click Folder Options, and then click the File Types tab.
• Configuration data for COM objects.

The content of HKEY_CLASSES_ROOT comes from two sources, HKEY_LOCAL_MACHINE\SOFTWARE\Classes and HKEY_CURRENT_USER\SOFTWARE\Classes. If a subkey or entry appears in either location, it also appears HKEY_CLASSES_ROOT. If the values of entries in the two Classes subkeys conflict, only the value in HKEY_CURRENT_USER\SOFTWARE\Classes appears in HKEY_CLASSES_ROOT.

In Windows NT 4.0 and earlier, HKEY_CLASSES_ROOT displayed the data in HKEY_LOCAL_MACHINE\SOFTWARE\Classes only. The current merged configuration lets the system register program classes independently for each user. This feature is known as per-user class registration.

Per-user registration has several benefits:

• Multiple users can customize a single computer. For example, User A can install an application which uses a particular file type, and User B can install a different application which uses the same file type without affecting User A.
• Roaming class registration. Because class registrations are stored in the user profile, the class registrations are loaded on each computer through the application management extension after the profile is loaded. When the user logs in to a different computer, the registration will travel with the user through the directory and be written to a local portion of the user profile during logon.

• Note: Roaming class registration is only available when using Intellimirror Software Management. For more information about Intellimirror, see Windows 2000 Help.

• Increased registry security. Previously, users could change or delete registry keys under HKLM\SOFTWARE\Classes, thus breaking an application or changing its behavior. However, with class information now written to the user profile, a system administrator can limit access to HKLM\SOFTWARE\Classes.

Note

This is a change in functionality from Windows NT 4.0, where HKEY_CLASSES_ROOT was an alias of HKEY_LOCAL_MACHINE\SOFTWARE\Classes. For more information about HKEY_CLASSES_ROOT, see the COM Programmer's Reference and the Automation Programmer's Reference in the Platform Software Development Kit at http://msdn.microsoft.com.

If an entry exists in both HKEY_LOCAL_MACHINE\SOFTWARE\Classes and HKEY_CURRENT_USER\SOFTWARE\Classes, the value of the entry in HKEY_CURRENT_USER\SOFTWARE\Classes will take precedence.

If you create a new key or subkey in HKEY_CLASSES_ROOT, it will also be created in HKEY_LOCAL_MACHINE\SOFTWARE\Classes. If you create a new entry in this same key or subkey, that entry will also appear in that key or subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Classes.

If you create a new entry in an existing subkey, where that entry will appear depends on whether the subkey already exists in HKEY_LOCAL_MACHINE\SOFTWARE\Classes or HKEY_CURRENT_USER\SOFTWARE\Classes:

• If the subkey exists in both HKEY_CURRENT_USER\SOFTWARE\Classes and HKEY_LOCAL_MACHINE\SOFTWARE\Classes, the entry will appear in that subkey in HKEY_CURRENT_USER\SOFTWARE\Classes only.
• If the subkey already exists in HKEY_CURRENT_USER\SOFTWARE\Classes only, then the entry will appear in that subkey in HKEY_CURRENT_USER\SOFTWARE\Classes.
• If the subkey already exists in HKEY_LOCAL_MACHINE\SOFTWARE\Classes only, then the entry will appear in that subkey in HKEY_LOCAL_MACHINE\SOFTWARE\Classes.