W P Staff asked 6 years ago
W P Staff answered 6 years ago
1) Before do anything, restart the computer 2 or 3 times to see whether it’s going back to your old correct profile. Go to next step if this doesn’t work.
2) Rename the temp profile registry and revert back the old registry settings for the correct profile. This method works most of the time for me in Workgroup and domain environment.
a) Log in with temp profile.
b) Start registry editor by typing regedit in find box of Windows 7.
c) Navigate the following location.
d) You will see similar keys under profile list, but one with .bak, as shown below.
e) The key with .bak is for the correct old profile. Currently your Windows 7 computer logged in with fresh (temporary) profile with same key. So, rename the new profile key ( which is not having.bak) and remove .bak from correct profile key. See below.
f) That’s it. Log off and log in (or restart) with your user name and password. You must get your correct profile with icons and profile settings back in Windows 7, if you are lucky enough.
Still if Windows 7 computer loads with temporary profile and creates a registry key with .bak, that means user profile is really corrupted and Operating System
is not reading it properly.
3) Few times this method worked for me, repair the corrupted files. Usually the corrupted ‘Ntuser’ files cause this issue. So, run the check disk for partition which is having user profile.
After restarting for check disk, if you see corrupted entries and repairing process inside your user profile folder, then you can hope for good news here. If it finds and repairs any files especially Ntuser files, you may get your old Windows 7 profile back.
If above steps do not help you out, then we need to create a new profile with new user name.
Basically we need to create a new user account, login with it and transfer the data from old user profile to new user profile. It is easy in workgroup environment as you can create new user name locally, but it is tricky in domain environment. Because, the existing user account is already there on domain server and nothing wrong with it. Also, creating a new different domain user account will cause issues on corporate emails, domain groups membership and shared permissions.