📎 AI Summary:
The thread discusses a corrupted user profile issue on a Windows Vista laptop, with the original poster seeking alternatives to the Microsoft-recommended method of creating a new profile and transferring files. A respondent explains that problems with the security identifier or corrupted NTUSER files can complicate recovery, suggesting running system tools like chkdsk and sfc /scannow, and warns that manually deleting profile files may lead to additional issues. The original poster plans to perform these steps and inquires about managing the sfc /scannow log file, seeking guidance on how to save, reset, and rerun the system file checker. Overall, the conversation is technical and helpful, focusing on troubleshooting user profile corruption with an emphasis on caution and proper procedures.
mikemyers

mikemyers

Well-Known Member
Joined
Jul 27, 2013
Messages
2
Thread Author #1
On one of my laptops, the main "user profile" apparently got corrupted. When I click on a folder, instead of using Windows explorer to show the folder, it opens up a program. I know it's the user profile, and not the computer itself, as I created a second user profile for testing, and that one works correctly. This particular laptop is still running Vista Professional, but I think that Vista, 7, and 8 all use the same "user profile" setup.

When I did a search, I found the Microsoft way to fix this - create a new account (actually, to do this I need three accounts on the computer), and then while logged into the third account, copy over all the files except two, from the "damaged profile" to the "new profile". Here's the link:
http://windows.microsoft.com/en-us/windows-vista/fix-a-corrupted-user-profile

Does anyone know a way to "fix" the problem, rather than do it Microsoft's way? If the two files they are concerned with are corrupted, can I re-create them?
 

Solution
Mike
There is a reason they specifically recommend creating a new account. When a Windows server migration takes place, a problem can happen with the security identifier on the account. Each account has a SID and this is problematic when a server is switched out or migrated incorrectly. If NTUSER.dat is corrupt, there is very little you will be able to do to restore the account to operation. You can try deleting that file, along with NTUSER.ini, and NTUSER.dat.log. You can find these files in c:\users\your_username in other words from the command line:

%userprofile% when in the account

To see these files you'll need to uncheck "Hide protected operating system files" in Explorer under Folder Options - View.

You will want to delete these...
Sort by date Sort by votes
Mike

Mike

Windows Forum Admin
Staff member
Premium Supporter
Joined
Jul 22, 2005
Messages
9,267
#2
There is a reason they specifically recommend creating a new account. When a Windows server migration takes place, a problem can happen with the security identifier on the account. Each account has a SID and this is problematic when a server is switched out or migrated incorrectly. If NTUSER.dat is corrupt, there is very little you will be able to do to restore the account to operation. You can try deleting that file, along with NTUSER.ini, and NTUSER.dat.log. You can find these files in c:\users\your_username in other words from the command line:

%userprofile% when in the account

To see these files you'll need to uncheck "Hide protected operating system files" in Explorer under Folder Options - View.

You will want to delete these files from a secondary account, which may require elevated administrator privileges. Windows may try to recreate the files, but you'll lose all your customizations and settings on the account. It is safe to say this is not the recommended way of doing it, as it may or may not work, and you could be opening yourself up to future problems.

Also, this may be a sign of additional corruption. You should run chkdsk /f on the drive as well as sfc /scannow under an elevated Command Prompt.
 

Upvote 1 Downvote
Solution
mikemyers

mikemyers

Well-Known Member
Joined
Jul 27, 2013
Messages
2
Thread Author #3
Thanks for the reply. I will do the chkdsk /f (have learned how to do that), and also the sfc /scannow (I know how to do this, but not how to do the follow-up fixing). When that's done, I will create the new account as per the MS instructions. Thanks to your reply, I now know the "why" of doing it this way.

Regarding sfc /scannow, I've tried to follow the instructions twice, and never quite understood how to use that tool. I will check here for a thread on how to do so. One quick question - is it possible to copy the log file to a saved location, zero out the file, and start over again?
 

Upvote 0 Downvote
You must log in or register to reply here.