Windows Says "User Profile Cannot Be Loaded" — or Signs You Into a Temporary Profile? Here's the Fix

You go to sign in to Windows and instead of your desktop you get one of two frightening messages. The first is a hard stop right at the login screen: "The User Profile Service service failed the sign-in. User profile cannot be loaded." You type your password, it accepts it, and then it bounces you straight back out. The second is sneakier — you do get to a desktop, but it's not yours: default wallpaper, no icons, none of your files, and a little pop-up that says "We can't sign in to your account," or "You've been signed in with a temporary profile," and warns that anything you do now will be lost when you sign out. Either way it feels like your whole account, and everything in it, just vanished.

Here's the reassurance to lead with, because it's true almost every time: your files are not gone. Your documents, photos, desktop and downloads are still sitting in the folder C:\Users\YourName exactly where they always were. What's broken is the profile — the small bundle of settings and the registry entry that tells Windows how to load that folder as your account. When Windows can't read that bundle, it either refuses the sign-in or quietly gives you a blank stand-in "temporary" profile so you can at least use the machine. This is a loading problem, not a wiped hard drive, and in most cases you can get your real profile back with free, built-in tools. You do not need a "profile repair" or "PC fixer" download — those are the last thing to hand a computer that's only having a profile hiccup.

One quick scope check so you're in the right guide. This is specifically about Windows accepting your sign-in but failing to load your profile. If Windows won't take your password or PIN at all because you've forgotten it, that's a different problem — see our guide on being locked out of a PC. If your PIN in particular throws "Your PIN isn't available," or fingerprint/face sign-in has stopped, we have dedicated guides for those. And if you can sign in fine but the Start menu and taskbar are dead once you're on the desktop, that's the shell, covered separately. This article is the "it says my profile can't be loaded, or it stuck me on a temporary account" case. We sort these out for homes and small businesses across Southern California and the Coachella Valley every week.

First, the one thing not to do: don't work inside the temporary profile

If Windows has dropped you onto a temporary profile — blank desktop, none of your stuff, that "changes will be lost" warning — treat that session as read-only and throwaway. Anything you create or save there, and any file you drag into its Documents or Desktop, is deleted the moment you sign out. So don't start working, don't save that email attachment "just for now," and above all don't copy files from your real profile into the temporary one thinking you're rescuing them — you'd be moving them somewhere that gets wiped. Your real data is safe where it is, in C:\Users\YourName; the goal is to get you back into that account, not to rebuild inside the temporary one.

It helps to know why this happens, because it points straight at the fix. Windows stores each person's account as a profile folder plus a small registry hive (a file called NTUSER.dat) that gets loaded at sign-in, and it keeps a list of everyone's profiles under a registry key called ProfileList. If that hive can't be read or the ProfileList entry is wrong or duplicated, the profile won't load. The usual triggers are ordinary: a Windows update that went badly, the PC being force-powered-off or losing power mid-session, antivirus locking the NTUSER.dat file exactly as Windows tries to open it during login, or a drive that's full or beginning to fail. None of those erase your files — they just knock over the thing that loads them.

The two-minute first move: restart a few times, then try Safe Mode

Before touching anything advanced, try the cheap fixes, because a surprising share of these clear on their own. If a locked or busy NTUSER.dat was the cause, simply restarting can let it load cleanly the next time. Restart the PC and let it reach a desktop, then restart again — do this three or four times in a row. Many temporary-profile cases fix themselves after a couple of full reboots. If you're on a temporary profile rather than fully locked out, signing out and back in (or restarting) is also the first thing Microsoft's own guidance suggests, for the same reason.

If a plain restart doesn't restore your real profile, try signing in through Safe Mode, which loads a stripped-down Windows and can sometimes reattach the correct profile. To get there: hold Shift while you click Restart (from the sign-in screen's power button or the Start menu), then choose Troubleshoot > Advanced options > Startup Settings > Restart, and when the list appears press 4 (or F4) for Safe Mode. Sign in, let it settle, then restart normally and sign in again — occasionally that's all it takes. If the PC won't even reach the sign-in screen, you can force the recovery menu by pressing the power button to interrupt startup three times in a row; the fourth boot brings up the same Troubleshoot options.

The main fix: repair the profile entry in the registry

When restarts don't do it, the real fix is usually to correct the profile's entry in the ProfileList registry key. This needs an administrator account — if your own account is the broken one, sign in with another admin account or use Safe Mode as above. Important caution first: the registry runs Windows, and changing the wrong value here can make things worse, so before you edit anything, create a System Restore point (or export the ProfileList key with File > Export). If you're not comfortable in the registry, this is a very reasonable point to have a person do it with you rather than guess.

Open the Registry Editor (press Windows+R, type regedit, press Enter) and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Under it you'll see several keys with long names beginning "S-1-5-21-…" — these are the accounts on the PC. Click each one and look at the ProfileImagePath value on the right until you find the one that reads C:\Users\YourName (your actual account folder). What you do next depends on what you see:

Case one — there are two keys for your account, and one ends in ".bak". This is the classic cause. The one ending in .bak is your real profile; the one without .bak is the temporary stand-in. Right-click the key without .bak and rename it to add a suffix (for example, add ".bak2" to the end); then right-click the key that ends in .bak and rename it to remove the ".bak" so it becomes the plain S-1-5-21 name. Now select that key, and in the right-hand pane double-click the value named State and set it to 0, and double-click RefCount and set it to 0 (if either value is missing, right-click > New > DWORD (32-bit) Value, name it exactly State or RefCount, and set it to 0).

Case two — there's only one key for your account, with no .bak twin. Then you don't rename anything; just select that key and set State to 0 and RefCount to 0 as above, and confirm its ProfileImagePath still points to C:\Users\YourName and not to some C:\Users\TEMP path. Either way, close the Registry Editor and restart the PC, then sign in — in most cases you'll land back in your own profile with your files, wallpaper and settings intact.

If the registry fix won't hold: build a fresh account and move your files

Sometimes a profile is corrupted too badly to revive, and it keeps reverting to temporary no matter what you set. The honest, reliable cure then is to create a brand-new account and move your files into it — you lose the profile's app settings, but you keep all your actual data, and it's usually faster than fighting a broken hive. From a working admin account, go to Settings > Accounts > Other users > Add account, choose "I don't have this person's sign-in information," then "Add a user without a Microsoft account," and create a local account (you can link it to your Microsoft account later). Give it administrator rights, then sign into the new account.

Now copy your data across. Open File Explorer to C:\Users\YourOldName and copy the contents of Documents, Pictures, Desktop, Downloads and any other personal folders into the matching folders of the new account. Copy your actual files only — do not try to copy the whole old profile or its hidden AppData folder over the new one, because that just carries the corruption across. Browser bookmarks and passwords come back by signing back into Chrome, Edge or Firefox with your account. Once the new profile is working and your files are in it, you can leave the old account in place (its folder is your backup) until you're certain nothing was missed. Our guide on moving everything to a new Windows PC walks through the same file-by-file copy if you want more detail — and if this scare taught you anything, it's why a regular backup is worth setting up so a profile fault is never a data loss.

Stop it coming back — and when it's time to reset

A profile that broke once can break again if the underlying cause is still there, so it's worth ruling a few things out. If your antivirus is aggressive, it can lock NTUSER.dat during sign-in and trip this repeatedly; adding your user folder as an exclusion (or the profile corrupting only after a scan) is a strong hint that's the culprit. If the trouble started right after a Windows update, roll that update back — our guide on a stuck or bad Windows update covers doing that safely. And check the boring hardware causes: a drive with almost no free space can't write the profile properly, and a drive that's starting to fail corrupts the hive — if your C: drive is nearly full, clear some room; if the PC has also been freezing, throwing read errors, or making odd noises, treat a failing disk as a real possibility and back up now. Repairing Windows' own system files with sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth (run from an admin Terminal) can also fix underlying damage that keeps knocking the profile over — a good step to run with a person if you're unsure.

Finally, the honest endpoint. If even a brand-new account immediately loads as temporary, or the error survives the restarts, the registry repair, a fresh account and the system-file repairs, then the damage is system-wide rather than in one profile, and you're into "Reset this PC" territory (Settings > System > Recovery > Reset this PC > Keep my files). Because a reset is a bigger job, back up your files off the machine first — copy C:\Users\YourName to an external drive — and it's worth talking through with someone before you commit, so you don't reset a PC whose real problem was a failing drive that a reset won't fix.

How we can help

To recap the order that fixes almost all of these: restart three or four times and try signing in through Safe Mode; if that doesn't restore your real profile, repair the account's entry in the ProfileList registry key (handle the .bak twin, set State and RefCount to 0, confirm the path points at your real C:\Users folder) after making a restore point; if the profile is too far gone, create a fresh admin account and copy your files across (never into the throwaway temporary profile); and rule out the antivirus, a bad update, or a full or failing drive so it doesn't come back — with a full backup and, if needed, a Reset that keeps your files as the last resort. Every one of those is a free, built-in step.

This is one of those problems where the fix is straightforward but the stakes feel high, because it looks exactly like you've lost everything — and the registry work in the middle is genuinely easy to get wrong. If you'd rather not gamble with it, that's a sensible call. We recover locked and corrupted Windows profiles, sort out temporary-profile loops, and migrate your files cleanly to a fresh account for homes and small businesses across Southern California and the Coachella Valley, in person or by remote support — and because we don't sell you a new PC to make the problem go away, we'll always start with getting your real account, and your files, back exactly as they were.