A Windows 11 login loop — where you enter your credentials, the login appears to succeed, Windows starts loading, and then returns to the login screen again — is one of the more stressful Windows problems because it locks you out entirely. But it has a reliable set of causes and a systematic recovery path. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.
The critical first step: determine whether you can access Safe Mode or the Windows Recovery Environment. If you can, most causes are fixable. If you can’t access either, there’s still an option, but the path is longer.
To reach WinRE from the login screen: click the power icon (bottom right of the login screen) → hold Shift → click Restart. This boots into the recovery environment without completing the normal login. From here, Troubleshoot → Advanced options provides access to the repair tools that address most login loop causes.
Most Common Causes
Three causes cover the vast majority of login loops:
- ProfileList registry corruption — Windows is trying to load a user profile from a wrong registry path. The most common cause after a Windows update or unexpected shutdown. Fix 2.
- User profile folder renamed or moved — The C:Users[YourName] folder was renamed or moved and Windows can’t find it. Fix 3.
- Corrupted system files — System files required for the login sequence are damaged. Fix 5 (SFC from recovery environment).
Fix 1: Disable Automatic Restart on System Failure
Before working through fixes: prevent Windows from automatically restarting during the login loop, which makes it harder to apply fixes from the recovery environment.
From WinRE: Troubleshoot → Advanced options → Startup Settings → Restart → press 8 for Disable automatic restart on system failure. After restarting with this setting, Windows won’t automatically loop back through the failed login — it stays at whatever stage the failure occurs, giving more information about what’s failing.
Fix 2: Fix the ProfileList Registry Corruption
When a user profile load fails, Windows redirects the login to a temporary profile — but then the login screen reappears because Windows won’t let you continue in a temporary profile in some configurations. The ProfileList registry key may show the profile path as ending in “.bak” or may have duplicate entries causing the redirection to fail.
Access the registry from WinRE: Troubleshoot → Advanced options → Command Prompt.
regeditNavigate to: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionProfileList
Look for keys that end in “.bak” — these indicate a failed profile load. The key without “.bak” should have a ProfileImagePath pointing to your C:Users[Name] folder. If there are two keys with the same SID (one with .bak and one without), the .bak one needs attention:
- Right-click the .bak key → rename it to remove .bak (making it the primary)
- Or right-click the non-.bak key → delete it, then rename the .bak key without .bak
Restart and attempt login. This resolves the “looping back to login” pattern that appears after Windows created a temporary profile on a previous login attempt.
Fix 3: Check User Profile Folder Integrity
From WinRE Command Prompt, verify the user profile folder exists:
dir C:UsersYour username folder should appear. If it doesn’t exist, or if it exists but is named differently than Windows expects (C:UsersUsername.000 instead of C:UsersUsername), Windows can’t load the profile.
If the folder exists but is renamed: rename it back to the expected name. If the folder is missing entirely: the profile folder was deleted and recovery requires either restoring from backup or creating a new user account and migrating data.
Fix 4: Reset PIN or Password From Recovery
Login loops caused by authentication failures — incorrect PIN, expired password, or corrupted Windows Hello credential — require resetting the credentials rather than fixing file system or registry issues.
From WinRE → Troubleshoot → Advanced options → Command Prompt:
net user [username] [newpassword]Replace [username] with the Windows account name and [newpassword] with a temporary password. Restart → log in with the temporary password → immediately set a proper password through Settings. This bypasses the corrupted credential state that was preventing login.
For Microsoft accounts with a PIN that’s stopped working: after the forced password login, Settings → Accounts → Sign-in options → Windows Hello PIN → remove and re-add the PIN. The fresh PIN setup goes through a clean verification process that resolves whatever corrupted the previous PIN.
Fix 5: SFC and DISM From Recovery Environment
System file corruption that affects the login sequence requires SFC run offline from the recovery environment — running it from within a logged-in Windows session won’t fix corruption in files that Windows needs for the login process itself.
From WinRE Command Prompt, identify the Windows drive letter first (it may not be C: in the recovery environment):
dir D:Windows
dir E:WindowsTry different letters until you find the Windows folder. Then run:
sfc /scannow /offbootdir=C: /offwindir=C:Windows(Replace C: with the correct drive letter.) This runs SFC against the offline Windows installation, repairing files that are actively in use during normal operation and can’t be replaced while Windows is running.
Fix 6: Create a New User Account
When the specific user profile has irreparable corruption but the Windows installation itself is fine, creating a new user account provides a working login while data is migrated from the old account. From WinRE Command Prompt:
net user [newusername] [password] /add
net localgroup Administrators [newusername] /addRestart → log in with the new account → the desktop loads correctly. From the new account, navigate to C:Users[OldUsername] to access the old profile’s files and copy them to the new account’s profile. The Documents, Desktop, Pictures, and other personal folders can be transferred directly.
Windows Hello and Biometric Login Loops
Login loops specific to PIN or biometric (fingerprint, face) while the password still works indicate corrupted Windows Hello data rather than a general profile issue. Settings → Accounts → Sign-in options → Windows Hello PIN → I forgot my PIN → follow the reset process. After resetting, the PIN re-registers through a clean verification that clears the corrupted data causing the loop.
Our guide on Windows 11 not booting covers the startup failures that prevent reaching the login screen at all — a more severe failure with overlapping recovery environment steps. For the ProfileList registry approach, our black screen recovery guide covers accessing registry editing from the recovery environment with more detail on drive letter identification. Microsoft’s Windows 11 sign-in troubleshooting documentation covers Microsoft account login recovery, the account unlock process after too many failed attempts, and the DISM /RestoreHealth offline repair for corrupted Windows component stores.
Recent Update as a Login Loop Trigger
Windows updates that install and then restart the machine for completion sometimes interrupt the profile loading sequence mid-update. If the machine was shut down during a profile update or the update changed user profile handling, the login loop appears on the next startup. The ProfileList registry fix (Fix 2) handles most update-caused login loops.
If the update itself needs to be reversed: from WinRE → Troubleshoot → Advanced options → Uninstall Updates → remove the most recent Cumulative Update or Feature Update. After uninstalling and restarting, the machine returns to the pre-update state where login worked. Check whether Microsoft has released a fix for the login loop issue before reinstalling the update.
System Restore From Recovery Environment
If the login loop started after a specific change — a software installation, a Windows update, a driver change — and a System Restore point exists from before that change, restoring to the prior state is often the fastest resolution. WinRE → Troubleshoot → Advanced options → System Restore → follow the wizard to select a restore point from before the loop started.
System Restore doesn’t affect personal files (documents, photos, downloads) but does remove software installed after the restore point and reverses system configuration changes. After the restore completes, the machine reboots and login should work correctly. Verify the trigger for the original login loop — if it was a Windows Update, the update will attempt to reinstall at the next update check, potentially re-creating the loop.
Third-Party Software Blocking Login Completion
Security software, endpoint agents, and system utilities that run during the login sequence can cause loops when they encounter an error or infinite wait during initialisation. The login appears to complete (Windows logo shows, user profile loads briefly) and then returns to login because the startup sequence failed.
Test: boot into Safe Mode (WinRE → Startup Settings → press 4 for Safe Mode). Safe Mode loads only essential components — if login succeeds in Safe Mode, a non-essential startup application or service is causing the loop in normal mode. From Safe Mode, use msconfig → Startup tab or Task Manager → Startup apps to disable startup items in groups. Restart normally after each group is disabled — when login succeeds after disabling a specific group, narrow down to the specific application within that group.
Corrupted User Registry Hive
Each user account has its own registry hive (NTUSER.DAT file in the user profile folder). When this file becomes corrupted, Windows can’t load the user’s settings during login, which causes the login to fail and loop. The issue is specific to the affected user account — other user accounts on the same machine log in normally.
From WinRE Command Prompt, check the NTUSER.DAT file:
dir C:Users[username]NTUSER.DATThe file should exist and have a reasonable file size (typically several MB for an established account). If it shows as 0 bytes or is missing, the registry hive is damaged. Windows keeps a backup at NTUSER.DAT.LOG — this can sometimes be used to restore the hive. A corrupted NTUSER.DAT typically means creating a new user account (Fix 6) and migrating data, as repairing a corrupted registry hive requires specialised registry recovery tools.
Group Policy or Logon Script Failures
On domain-joined Windows 11 machines, logon scripts and Group Policy processing run during the login sequence. If a logon script encounters an error that prevents it from completing, or if a Group Policy setting conflicts with the current system state, the login sequence stalls and eventually loops back. This is specific to domain environments rather than personal machines.
The indicator: login loops on domain-joined machines while local account or administrator login works fine. Event Viewer from a working login (even temporary access through the recovery environment Command Prompt) shows Group Policy or script errors timestamped during the failed login attempts. Reporting these specific events to IT provides the information needed to diagnose whether the issue is a logon script error, a policy configuration problem, or a domain authentication issue that needs server-side investigation.
Microsoft Account vs Local Account Login
Windows 11 login loops sometimes occur specifically with Microsoft account login while a local account login for the same machine works. This indicates the Microsoft account authentication component has a problem rather than the local user profile.
Create a local administrator account from the recovery environment (Fix 6) → log in with the local account → Settings → Accounts → Other users → Add account → Add a Microsoft account → re-add the Microsoft account fresh. After re-adding, the Microsoft account login re-establishes a clean authentication token and profile association. The login loop caused by the corrupted Microsoft account session is resolved because the account is re-associated with the profile from a clean starting point.
When Nothing Works: In-Place Upgrade
If login loops persist through all recovery attempts — registry fix, SFC, Safe Mode testing, new account creation — an in-place Windows 11 upgrade reinstalls Windows while keeping files, applications, and most settings. This is the most thorough local fix short of a full wipe and reinstall.
From WinRE, access Command Prompt and mount the Windows 11 installation media (USB drive or ISO) → run setup.exe → choose “Upgrade this PC” → select “Keep personal files and apps.” The in-place upgrade replaces all Windows system files with known-good versions and re-establishes the login infrastructure from scratch. After the upgrade, login works reliably because the corrupted components that caused the loop have been replaced entirely.
A practical note on data protection during login loop recovery: before applying any fix that modifies system files, registry, or user accounts, consider whether your important data is backed up or accessible. Most login loop fixes don’t touch personal files — documents, photos, and downloads in the user profile remain accessible even when the login mechanism is broken, accessible through the WinRE Command Prompt by navigating to C:Users[username]Documents. If there’s any uncertainty about a fix’s impact, copying critical files from the recovery environment to an external drive before proceeding provides a safety net regardless of the outcome.
Login loops after a failed Windows Hello update or after enrolling in a new MFA method sometimes respond to a specific quick fix without going into the recovery environment: at the login screen, instead of using PIN or biometric, click “Sign-in options” and select the password option. If password login succeeds while PIN login loops, the PIN data specifically is corrupted rather than the full profile. After logging in with password, Settings → Accounts → Sign-in options → Windows Hello PIN → I forgot my PIN → reset it. This targeted fix applies in a narrow but common scenario that doesn’t require the full recovery environment approach. See also Windows 11 Stuck on Identifying Network for a related case.
