Rightek Rescue · Guides · We can't sign in / temporary profile

"We can't sign in to your account" or a temporary profile? Here's the fix

You signed in and your desktop, documents and settings are all gone — because Windows loaded a blank temporary profile instead of yours. Take a breath: your real profile and all its files are still on the disk. Windows just pointed you at a placeholder because it couldn't load the real one.

Updated 23 August 2026 · written and tested by Rightek IT Services

What you're seeing

• A pop-up: "We can't sign in to your account" or "You've been signed in with a temporary profile"
• Or "The User Profile Service service failed the sign-in. User profile cannot be loaded."
• Your normal desktop, Documents and browser data appear empty or reset
• Anything you save now disappears at the next sign-out

Why it happens

• Your profile's registry file (NTUSER.DAT) is corrupt, so Windows loads a temporary one instead
• Your account's profile entry got a leftover .bak tag, so Windows looks in the wrong place
• The Default user template that new accounts are cloned from is broken (so new or first-time users can't sign in, while existing ones can)
• A bad shutdown or disk error damaged the profile on the way to disk

Fix it yourself — the manual steps

1. Sign in, open regedit → HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
2. Find your account's key. If there are two keys with the same ID and one ends in .bak, the pointers need to be swapped back — a fiddly, easy-to-get-wrong edit.
3. If NTUSER.DAT in your profile folder is corrupt, it has to be replaced from a backup (Windows.old) — without overwriting your data.
4. Reboot and sign in.

The manual registry edit is exactly where people make it worse. Rescue does it safely and keeps your files.

Your files are still there — check, and then relax

The alarming part of this fault is that the desktop looks wiped. It is not. Windows could not load your profile, so it made an empty temporary one and signed you into that instead. Your real profile is untouched on disk.

Confirm it in ten seconds: open File Explorer and go to C:\Users. You should see a folder with your account name, containing your Documents, Desktop and Pictures exactly as you left them. That is your data. Nothing has been deleted.

Do not create a new account to work around this

It is the instinctive move and it makes things harder. A new account gets a new profile folder and, on a machine already struggling with the Default template, may fail in exactly the same way. Worse, people then start saving work into the new account and end up with data split across two profiles, which is a genuinely annoying thing to unpick later.

Similarly: do not delete the existing profile folder to "start clean". That folder is your data.

What the .bak entry actually means

Windows tracks profiles in the registry under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Each account has a key named after its security identifier — a long S-1-5-21-... string.

When Windows fails to load a profile, it renames that key by appending .bak and creates a fresh one under the original name pointing at the temporary profile. So you end up with two keys: the .bak one pointing at your real data, and a new one pointing at nothing. Repairing it means swapping them back and correcting two values inside (State and RefCount).

That is the fix, and it is also exactly where people make it worse — editing the wrong SID, or leaving the values inconsistent, produces an account that cannot sign in at all. If you do attempt it, export the ProfileList key first so there is a way back.

Recovering your data without touching the registry

If the registry edit is more than you want to attempt, there is a safe alternative that gets your files back even if the profile itself is never repaired: sign in as another administrator account (or from a rescue USB), and copy the contents of your old profile folder out to an external drive. Documents, Desktop, Pictures, and the browser profiles under AppData\Local.

That does not fix the profile, but it does mean the worst case is inconvenience rather than loss — which is a good position to be in before attempting anything riskier.

Why it happened

Almost always a bad shutdown while your profile's NTUSER.DAT was being written, or disk errors damaging it. If it keeps recurring after being repaired, that points at the drive rather than at Windows — check the disk's health.

FAQ