Fixing the Windows 11 Login Screen Loop

The login loop is uniquely maddening: you type your password, Windows seems to accept it, the screen goes dark for a moment — and you’re back at the login screen. No error message, no explanation, just an infinite merry-go-round. The good news is that the loop has a short list of causes, and each has a clean fix.

The key diagnostic question is whether any account can sign in. If a different account works, your profile is the problem. If nothing works, Windows itself needs repair. This guide handles both paths in order.

Why this happens

• Corrupted user profile. Damaged profile registry data or profile files prevent the desktop from loading after authentication.
• Broken credential or PIN data. Corrupted Windows Hello or credential manager entries can interrupt the sign-in sequence.
• Misbehaving startup program. An application that crashes during login can abort the whole sign-in process.
• Damaged system files. Corruption in the components that build your desktop session causes silent sign-in failure.
• Disk errors. Bad sectors in profile or system areas produce intermittent login failures.
• Recent update damage. A bad update can break the credential providers or profile service.

How to fix it

Work through these in order — test signing in after each fix.

Fix 1: Try Safe Mode to break the cycle

Safe Mode bypasses the startup items and drivers that commonly cause the loop.

1. At the login screen, hold Shift and click the Power icon > Restart.
2. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode.
3. Try signing in. If Safe Mode lets you in, the cause is a startup program, driver, or service — continue to the next fix.
4. If Safe Mode also loops, skip to the profile and system-repair fixes below.

Fix 2: Disable startup programs and services

A crashing startup item can abort sign-in entirely.

1. In Safe Mode, press Win + R, type msconfig, and open System Configuration.
2. On the Services tab, tick Hide all Microsoft services and click Disable all.
3. Open Task Manager > Startup apps and disable everything.
4. Restart normally and try signing in. If it works, re-enable items in small groups until the culprit returns — then leave it disabled or reinstall it.

Fix 3: Clear corrupted credential data

Damaged PIN and Hello data can stall the sign-in sequence.

1. In Safe Mode, go to Settings > Accounts > Sign-in options.
2. Remove the PIN, facial recognition, and fingerprint entries.
3. Restart and sign in with your password.
4. Once you’re in normally, re-add the PIN and Hello methods fresh. Corrupted biometric data causes the same class of login failures covered in the Windows Hello fix guide .

Fix 4: Create a new user profile

If your profile is corrupted, a fresh one gets you working in minutes.

1. In Safe Mode, open an elevated Command Prompt and run net user NewUser * — set a password when prompted — then net localgroup administrators NewUser /add.
2. Restart and sign in as NewUser.
3. If the new account works, your old profile is the problem. Copy your files from C:\Users\OldName (Documents, Desktop, Pictures, Downloads) into the new profile.
4. Migrate browser data via sync or manual export, then delete the corrupted profile from Settings > Accounts > Other users once everything is moved.

Fix 5: Repair system files from recovery

When no account can sign in, Windows components need repair.

1. Boot to the recovery environment (Shift + Restart > Troubleshoot > Advanced options > Command Prompt).
2. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows.
3. Then run DISM /Image:C:\ /Cleanup-Image /RestoreHealth.
4. Restart and test sign-in. These repairs fix the profile service and credential components when they’re damaged.

Fix 6: Use System Restore

Roll back to before the loop started.

1. In recovery, go to Troubleshoot > Advanced options > System Restore.
2. Choose a restore point from before the login loop began.
3. Let it complete and restart. System Restore reverts system files and registry — including profile service configuration — without touching personal files.

Fix 7: Check the disk and reset as a last resort

Rule out storage damage, then rebuild if nothing else works.

1. From recovery Command Prompt, run chkdsk C: /f /r to find and repair disk errors affecting profile data.
2. Check drive health with your manufacturer’s diagnostics if available.
3. If the disk is healthy but nothing works, choose Troubleshoot > Reset this PC > Keep my files — this rebuilds Windows while preserving your data, the same reset covered in the reset-without-losing-files guide .

Fix 8: Repair the user profile service registry entries

When the profile itself is fine but Windows can’t load it, the profile list registry may be damaged.

1. Boot into Safe Mode and open Registry Editor (regedit).
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
3. Look for subkeys ending in .bak — these are backup copies of corrupted profiles. If your account’s SID appears both with and without .bak, the .bak one is usually the good copy.
4. Rename the corrupted key (add .old), remove .bak from the good one, and set its RefCount and State values to 0.
5. Restart and try signing in. If the registry is too damaged for manual repair, the reset-without-losing-files guide rebuilds it while keeping your data — and always back up the registry key (right-click > Export) before editing.

Closing

The login loop feels endless, but it’s a short diagnostic tree: Safe Mode tells you if it’s startup software, a new profile tells you if it’s profile corruption, and recovery tools fix system-wide damage. Work it in order and you’ll be at your desktop again — usually without losing a single file. Once you’re back in, set a restore point so the next problem is a five-minute rollback instead of another loop.

Frequently asked questions