amset.info
from Sembee Ltd.
UK MS Exchange Consultants

Exchange - Net Admin - Outlook
Windows Mobile - Windows

Contact - Director's Blog

AddThis Social Bookmark Button


Windows Home


Microsoft Windows
Amazon Store


Recovery Console

Internet Explorer

Terminal Services /
Remote Desktop Shortcut Keys

Clear Type

Network Diagnostics

Shortcut Keys

Numlock

Local Policy

Other Quick Tips

Command Prompt Basics

Net Send

Automatic Updates

Login Scripts

Run As

Limiting the Number of Logins a User Can Make

Custom Text on the
"Workstation Locked" Screen

Corrupt User Profiles

Microsoft Windows
Page Last Reviewed: 09/11/2006

Working with Corrupt Windows Profiles

A common problem with Windows machines is a corrupt user profile. This can manifest itself in various ways including applications not operating correctly. You can usually prove it by logging in to the same machine as another user and discovering that the applications or settings are correct.

If you find this is the case, then you need to create a new profile for the user.

DO NOT use "Files and Settings Transfer Wizard" as this will transfer corruption to the new profile.

  1. Reboot the machine.
  2. Login in as a user with local administrator rights. Do not use the username that has the corruption, even if they have local admin rights.
  3. In C:\Documents and Settings. You should see a directory that matches the user name of the corrupt user. Rename that directory to something like <username>.old.
  4. Log back in as the user with the problem and verify that the problem has been resolved.
  5. If the problem has been fixed, logout again, and login back in with local administrator rights.
  6. Copy the contents of My Documents, Favourites and any other folders that contains the user data to the new profile.
    You may want to look through the Application Data and Local Settings folders as these will contain the files that could have user settings in it.

If the replacement of the profile doesn't resolve the problem, then check whether the problem follows the user by asking them to login at another machine. The problem may be local to the machine.

Last Page Update:
09/11/2006
More Content from Sembee Ltd.
 
Resources on amset.info Other Sites Sembee Ltd.
Microsoft Exchange Command Prompt Getting Started Guide Microsoft Exchange Consultancy
Microsoft Outlook Login Scripts Director's Blog
Network Administration MS Exchange Resources  
Internet Explorer Knowledge Base search  
Microsoft Windows Recovery of MS Office content from Temp Files  
Microsoft Windows Mobile Troubleshoot the Automatic Updates Client  
Amazon Store    

© Sembee Ltd. 1998 - 2010.

Reproduction of any content on this web site is prohibited without express written consent. Use of this web site is subject to our terms and conditions. All trademarks and registered trademarks are property of their respective owners. This site is not endorsed or recommended by any company or organisation mentioned on this site. This site is to provide guidance only and as such we cannot be held responsible for any consequences of following the advice given.