Error message when you log on to a Windows Vista-based or Windows Server 2008-based computer that uses roaming user profiles: "Unable to log you on because your profile could not be loaded, please contact your administrator"

In a network environment, you configure some client computers to use roaming user profiles. In this case, users may become unable to log on from a client computer that is running Windows Vista or Windows Server 2008. The users receive an error message that resembles the following: Then, the user is logged off immediately.

Additionally, the following two application events (event 1508 and event 1502) are logged on the client computer:

Event 1508

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: Date
Event ID: 1508
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: Computer
Description: Windows was unable to load the registry. This problem is often caused by insufficient memory or insufficient security rights. DETAIL - Access denied for C:\Users\TEMP\ntuser.dat

Event 1502

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: <Date>
Event ID: 1502
Task Category: None
Level: Error
Keywords: Classic
User: User_SID
Computer: Machine Description: Windows cannot load the locally stored profile. Possible causes of this error include insufficient security rights or a corrupt local profile. DETAIL - File is used by another process

This problem occurs because of a race condition in which the Ntuser.dat file of the user cannot be mounted correctly.

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 this specific problem. 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Server 2008 or Windows Vista SP1 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 Server 2008 and Windows Vista note

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 Windows Vista

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

To log on to the system by using the user account again, you have to delete the following registry key: To work around this problem, you have to disable roaming user profiles on the client computer.

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008

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

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