Corrupted User Profiles Can Cause New Local Default to be Lost

When a corrupted profile on the central server is downloaded, an error 1009 is logged to the Windows NT event system log. A new local profile is created from the local default. After you restart, however, the system will not reference the new local profile and will begin the cycle of pulling down the corrupted profile from the server again.

The following error is displayed:

When Windows NT detects a certain type of profile corruption, a flag is set, causing the reference to the newly created user profile not to be saved in the registry. The user is given a new copy of the local default profile and can make changes to it which are saved to the hard disk. When the system is restarted, it looks for the local version to check the time stamp versus the server version. This check is made ONLY against profiles listed in the registry (not against the physical files in the profile directory) and, thus, the recently created local copy is ignored. The system then repeats the process of downloading the server copy (which is still corrupted) and the cycle repeats.

To work around this problem, after the user logs on and creates the file copies of the new local profile, manually copy these file copies to the profile server. They will be downloaded the next time the computer is restarted and should work fine from then on.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

• http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
  
  
• 152734  (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

Microsoft has confirmed that this is a problem in Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

For additional information, see the following article or articles in the Microsoft Knowledge Base: