Select the product you need help with

The user profile may not be correctly unloaded when you log off from a Windows Server 2003-based computer, and event 1517 is logged

Article ID: 944984 - View products that this article applies to.

SYMPTOMS

The user profile may not be correctly unloaded when you log off from a Windows Server 2003-based computer. Additionally, an event that resembles the following is logged in the Application log:

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: Date
Time: Time
User: NT AUTHORITY\SYSTEM
Computer: ComputerName
Description:
Windows saved user User_Name registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.

When you log on to the computer later, a temporary profile may be loaded. In this situation, any changes that you make to the current desktop will be lost after you log off from the system.

When this problem occurs, you cannot resolve it even by using the User Profile Hive Cleanup Service (UPHClean). To recover from this problem, you have to restart the computer.

This problem occurs regardless of whether you log on to the computer directly, in a terminal server session, or in a remote console session.

Back to the top | Give Feedback

CAUSE

This problem occurs because of a race condition on the reference count in the registry optimization module.

Back to the top | Give Feedback

RESOLUTION

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:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

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, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

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.