This article was previously published under Q191834
This article has been archived. It is offered "as is" and will no longer be updated.
User profiles that are stored on the server (roaming user profiles) maybecome corrupted if contact with the remote server is terminated during thecopy process. This may happen in, but is not limited to, the followingscenarios:
The user prematurely turns the workstation off.
The network connection from the workstation to the server is severed, for example, the cable is disconnected from the network card.
This problem occurs when Ntuser.dat contains only part of the profileinformation.
It should be noted that this hotfix does not resolve the underlying causeof the profile corruption. It merely prevents the user's NTUSER.DAT on theserver from being overwritten by the uploaded version, until the uploadcompletes successfully. If the profile does fail to copy successfully, thenone of two things will occur, depending on the user.
If the User Does Not Roam from Computer to Computer
The user will be prompted at the next logon to select between the localprofile and the remote profile. Because the upload process failed at thelast logoff, the date/time stamp on the remote Ntuser.dat file is olderthan the date/time stamp on the local Ntuser.dat file. This causes WindowsNT to prompt the user to prevent a loss of data on the local workstation.If the user selects the remote profile then any changes made to the userprofile in the last session -- colors, wallpaper, or other settings -- willbe lost.
If the User Does Roam from Computer to Computer
Any changes made to the user profile in the last session -- colors,wallpaper, or other settings -- session will be lost.
This does not affect any files saved to the Desktop, Personal folder, orother profile folders.
A change has been made that causes profile information to be stored in atemporary file (Ntuser.dat.tmp) and then renamed to Ntuser.dat when loggingoff.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT 4.0 Service Pack 3, Microsoft Windows NT Server 4.0 Enterprise Edition