Eventually, for one reason or another, you’re likely to encounter a corrupted user profile. \u00a0While it’s possible to simply perform a System Restore to correct this in many cases, other times, that isn’t possible.<\/p>\n
Fortunately, there are ways around this problem. \u00a0For starters, it’s important to know that Windows stores all user profile information in the following location:<\/p>\n
HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion\\ProfileList<\/p><\/blockquote>\n
Here, you’ll find several subkeys named S-1-5-xx-…, each of which corresponds with a specific user on the machine. \u00a0How do you know which user is which? \u00a0By noting the value of ProfileImagePath<\/strong>, which contains the path to the user’s home directory (and the value of the %USERPROFILE% Environment Variable). \u00a0If this value happens to be corrupt, this value may be incorrect, instead pointing to, for instance, the Windows temp directory. \u00a0You can change this value to the proper one if you’re careful about what you’re doing and it may correct the issue.<\/p>\n
But before <\/strong>you change anything, first be sure you have a safety net just in case. \u00a0If you can log in with another user profile, do so, then create a System Restore point. \u00a0Or, at the very least, boot to Safe Mode (or to Startup Repair\/WinRE in Vista\/7) and create a backup of the registry hives (either by exporting them from within Regedit or by copying them directly from the system32\/config <\/strong>and %USERPROFILE% <\/strong>directories of the affected users. \u00a0Remember, the names of the registry hives are SOFTWARE, SYSTEM, SAM, SECURITY, and \u00a0DEFAULT in the config <\/strong>folder and NTUSER.dat in the %USERPROFILE% <\/strong>folder).<\/p>\n
Other things to check include:<\/p>\n
\n
- Look for SIDs (S-1-5-…) that end in “.bak”<\/li>\n
\n
- If you see one, rename the other corresponding SID (which matches) to something else for backup purposes (such as .old<\/strong>)<\/li>\n
- Then, remove the “.bak” from the end of the other matching SID and check the RefCount value before rebooting:<\/li>\n<\/ul>\n
- Look for RefCount<\/strong>\u00a0values above 1 (You can change this to 0)<\/li>\n<\/ol>\n
If things are really screwy, you can export the entire ProfileList key and then manually delete any SIDs that you don’t want. \u00a0(This is what I had to do to force my client’s PC to boot properly after some seriously registry cleaner\/tweak utility damage yesterday.) \u00a0Just be sure that you actually have backups of the data before you do so!<\/p>\n
Play around with this key and you’ll eventually find your way back in Windows without (hopefully) too much trouble. \u00a0In the absolute worst-case scenario, you may need to enable Administrator account access<\/a> and then create another replacement user account (SID) for yourself, after which you’ll need to copy all of the files over manually. \u00a0But don’t fret; remember, there’s always a solution!<\/p>\n","protected":false},"excerpt":{"rendered":"
Eventually, for one reason or another, you’re likely to encounter a corrupted user profile. \u00a0While it’s possible to simply perform a System Restore to correct this in many cases, other times, that isn’t possible. Fortunately, there are ways around this … Continue reading