ERROR_BAD_USER_PROFILE (0x000004E5) Fix Guide

Cause #1: Corrupted User Profile Registry Key

This is the culprit in about 80% of cases. Windows stores the path to each user's profile in the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. When that key gets corrupted — often after a failed Windows update, disk error, or abrupt shutdown — you see error 0x000004E5 on login.

A real-world example: user's laptop loses power during a Windows Update. Next boot, they can't log in. The profile key is a mess.

Here's the fix:

1. Boot into Safe Mode. Hold Shift while clicking Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart. Press 4 or F4.
2. Open Regedit (type it in the Start menu).
3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
4. You'll see subkeys starting with S-1-5-21-. Look for two keys with the same long number. One ends in .bak — that's the backup. The other is the messed-up key.
5. Rename the non-.bak key by adding .old to it. Then rename the .bak key by removing .bak from it.
6. Reboot normally. Windows should now load your profile from the backup.

If you don't see a .bak key, you're probably dealing with Cause #2 or #3. Move on.

Cause #2: Corrupted NTUSER.DAT or User Profile Folder

Even if the registry is fine, the actual profile folder under C:\Users can get trashed. Common triggers: a virus scan quarantined NTUSER.DAT, a disk check ran mid-session, or you ran out of disk space and files got truncated.

This one's trickier because you need admin rights to mess with the folder. Boot into Safe Mode with Networking (Shift+Restart, then Troubleshoot > Advanced Options > Startup Settings > Restart, press 5).

1. Open File Explorer and go to C:\Users.
2. Right-click your user folder (the one you're trying to log into) and rename it to something like OldProfile.
3. Now back in regedit, go to the same ProfileList key. Find the subkey for your user (look at the ProfileImagePath value — it'll show the folder path).
4. Change ProfileImagePath to C:\Users\OldProfile.
5. Reboot and log in. Windows will create a fresh profile folder and copy some defaults. You'll lose your desktop, documents, and settings — but you can manually copy them from C:\Users\OldProfile after login.

Don't bother with chkdsk here. It rarely helps for profile corruption. Disk issues are a different error.

Cause #3: Third-Party Software Corrupting Profile on Load

Sometimes the profile itself is healthy, but something loads during login and borks it. I've seen this with old antivirus suites (Norton 360, McAfee), VPN clients (especially Cisco AnyConnect), and custom shell replacements. The error happens after you enter your password, right when Windows is applying your settings.

Fix: Boot into Safe Mode (no network this time — you want to exclude drivers and services). If the error doesn't appear in Safe Mode, you've confirmed it's a third-party thing.

1. Press Win+R, type msconfig, hit Enter.
2. Go to the Services tab, check 'Hide all Microsoft services', then click 'Disable all'.
3. Go to the Startup tab, open Task Manager, and disable everything.
4. Reboot normally. If you can log in, start re-enabling services and startups one batch at a time. The culprit is usually the first one you re-enable that triggers the error.
5. When you find it, uninstall or update that program.

If you can't even boot into Safe Mode because the profile is completely hosed, skip to the nuclear option: create a new local admin account via Command Prompt from the recovery environment (Shift+Restart > Troubleshoot > Advanced Options > Command Prompt). Run net user NewAdmin /add and net localgroup Administrators NewAdmin /add. Then log in with that account and delete the old profile using System Properties > Advanced > User Profiles.

Quick-Reference Summary Table

Bottom line: start with the registry backup fix. That one solves the majority of cases. If that fails, move to creating a fresh profile. Don't waste time with system restore or SFC — they almost never fix profile issues.