Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172647

From BetaArchive Wiki

Server Copy of User Profile May Be Overwritten By Local Copy


The information in this article applies to:

  • Microsoft Windows 95
  • Microsoft Windows 95 OEM Service Release, versions 1, 2, 2.1


If you are using user profiles and roaming profiles, a user's local copy of the profile may overwrite the server copy. The local copy may be out of date or incorrect. The user is not prompted when this occurs.


This behavior can occur in the following situation:

  • A user logs on at a workstation that does not contain a local copy of his or her profile, or that contains an outdated local copy of the profile.
  • The server copy of the profile is not successfully downloaded when the user logs on (for example, because of network problems).
  • The user logs off and then logs back on at the same workstation, but this time the server copy of the profile can be accessed.

When this situation occurs, the outdated or incorrect local copy of the profile overwrites the server copy. The server copy can also be over- written when the user logs off if the server becomes available at that time.

Windows compares the date and time stamps of the local and server copies of the profile when a user logs on. The newer copy of the profile overwrites the older copy. In the situation described above, the local copy has changed more recently than the server copy. When the profiles are reconciled, the newer local copy, although incorrect, overwrites the older server copy.


This issue is resolved by the following updated file for Windows 95 and OSR2, and later versions of this file:

   MPRSERV.DLL  version 4.00.956  dated 7/31/97  127,488 bytes 


Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression tested and should be applied only to computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

This issue is resolved in Microsoft Windows 98.


This update checks for the sequence of events described above, and prompts the user before overwriting the server copy of the profile with the local copy.

This behavior can also occur when you are using mandatory profiles. You may be able to work around this behavior by setting the security permissions on the file in the user's home folder to read access only.

This behavior can also be resolved using the update described in this article. However, the user is not prompted if the local profile is not synchronize with the mandatory server profile. The server profile is always used.

For additional information about using mandatory profiles in Windows 95, Please see the following article in the Microsoft Knowledge Base:

Q161809 How to Create Mandatory Profiles for Windows 95/98 Users

For additional information about issues resolved by updates to this component, please see the following articles in the Microsoft Knowledge Base:

Q184838 OLE Problems Using MSNDS Are Not Resolved By NWNP32 Update

Q181869 Desktop Folders Are Not Deleted Under Roving Profiles

Q181868 Config.pol File Attributes Change After Supervisor Logs On

Q174979 Screen Saver Password Is Not Changed with Domain Password

Q165402 Windows 95 Update to Encrypt Passwords in Memory

For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:

Q161020 Implementing Windows 95 Updates

Additional query words:

Keywords : kbnetwork osr1 osr2 win95
Issue type :
Technology : kbWin95search kbOPKSearch kbWin95 kbWin95OPKOSR2 kbWin95OPKOSR1 kbWin95OPKOSR210

Last Reviewed: March 30, 2001
© 2001 Microsoft Corporation. All rights reserved. Terms of Use.