You need the best way to fix a login loop, not every way — the shortest reliable path from staring at the sign-in screen to being back at your desktop. After fixing dozens of these, the answer is clear: break in through Safe Mode, test with a fresh profile, and repair what’s actually broken instead of guessing. This order works because it tests the most likely cause first — profile corruption — with a definitive yes-or-no experiment rather than a pile of maybes. No registry diving, no blind driver updates, no reinstalling Windows on a hunch.

This is the action-first companion to our full login screen loop troubleshooting guide . If you want the fastest route, follow this page from top to bottom; if this page’s fixes don’t work, that guide has the deeper diagnostics for unusual cases.

Why this happens

  • A corrupted user profile that Windows can’t load past the sign-in screen.
  • A third-party credential provider (VPN, biometric software) crashing during logon.
  • A failed Windows update leaving authentication components mismatched.
  • Too many broken startup items stalling the logon sequence.
  • Disk errors damaging profile or system files.
  • Corrupted system files in the winlogon/LSASS chain.
  • A full system drive preventing the profile from loading its temporary files.

How to fix it

Work through these in order — fastest, most decisive steps first.

Fix 1: Get into Safe Mode via the login screen

Everything starts here — Safe Mode is your way past the loop.

  1. At the login screen, hold Shift and click the Power icon > Restart.
  2. Choose Troubleshoot > Advanced options > Startup Settings > Restart.
  3. Press 4 for Safe Mode.
  4. Log in — Safe Mode skips the third-party components that usually cause the loop.
  5. If even Safe Mode loops, skip to Fix 5 for offline repairs.

Fix 2: Create a new administrator account

This is the decisive test: if a fresh profile logs in, your old one is corrupt and you’re ten minutes from done.

  1. In Safe Mode, open an elevated Command Prompt (Start, type cmd, Run as administrator).
  2. Run net user fixuser Temp1234 /add.
  3. Run net localgroup administrators fixuser /add.
  4. Restart and log in as fixuser.
  5. Success here means: migrate your files, don’t waste time repairing the old profile.

Fix 3: Migrate your files to the new profile

Your data is safe in the old profile folder — move it over methodically.

  1. Open File Explorer and navigate to C:\Users\<your-old-username>.
  2. Copy Desktop, Documents, Downloads, Pictures, Music, and Videos to the new profile’s folders.
  3. Export browser bookmarks/passwords if you don’t use cloud sync.
  4. Verify everything opens correctly in the new profile.
  5. Only then remove the old account via Settings > Accounts > Other users.

Fix 4: Remove the software that caused it

Before settling into the new profile, eliminate the trigger so it doesn’t corrupt this one too.

  1. In Settings > Apps > Installed apps, uninstall recently added VPN clients, biometric tools, and system tweakers.
  2. Open Task Manager > Startup apps and disable anything suspicious.
  3. Restart normally and confirm clean logins over several days.
  4. Reinstall removed software one piece at a time if you need it.
  5. The one that re-triggers the loop is your culprit — find an updated version or replace it.

Fix 5: Repair offline when Safe Mode fails too

If no account can log in, repair Windows from the recovery environment.

  1. Shift + Restart from the login screen, then Troubleshoot > Advanced options > Command Prompt.
  2. Run sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows.
  3. Run DISM /Image:C:\ /Cleanup-Image /RestoreHealth.
  4. Try System Restore from Advanced options — pick a point before the loop began. Our System Restore guide walks through it in detail.
  5. Type exit, choose Continue, and test the login.

Fix 6: Uninstall the update that triggered it

Check the timeline: loop started after Patch Tuesday? Roll it back.

  1. From recovery, go to Troubleshoot > Advanced options > Uninstall Updates.
  2. Remove the latest quality update first, restart, and test.
  3. If still looping, remove the latest feature update.
  4. Once stable, pause updates for two weeks while the issue gets fixed upstream.
  5. Microsoft’s Windows support hub tracks known bad updates.

Fix 7: Reset while keeping files (last resort)

When nothing else breaks the loop, a reset gives you a clean authentication stack.

  1. From recovery, choose Troubleshoot > Reset this PC > Keep my files.
  2. Prefer Cloud download for the cleanest files.
  3. After the reset, create your user account fresh — don’t restore a possibly corrupt profile backup.
  4. Reinstall apps from official sources.
  5. Set a system restore point once everything works, so next time is a ten-minute rollback.

Fix 8: Repair the profile via the registry (advanced)

If you must salvage the original profile instead of migrating, the registry holds the key.

  1. In Safe Mode, press Win + R, type regedit, and press Enter.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList.
  3. Find your profile’s SID key — if it ends in .bak, the profile failed to load.
  4. Rename the key without .bak to .tmp, rename the .bak key to remove the suffix, then delete the .tmp key.
  5. Set RefCount to 0 and State to 0, restart, and try logging in — back up the registry first by exporting the ProfileList key.

Closing

The best way to fix a login loop is the fastest decisive path: Safe Mode in, new profile test, migrate files, remove the trigger. It resolves the overwhelming majority of loops in under half an hour because most loops are corrupt profiles or crashing credential providers — both of which a fresh account sidesteps completely. Save the deep repairs for the rare cases where every account loops, and keep that restore point current afterwards so the next incident is trivial instead of genuinely terrifying.

Frequently asked questions

What is the quickest fix for a Windows 11 login loop?
Booting into Safe Mode and creating a new administrator account is the fastest reliable path — it takes about ten minutes and works even when the cause is unclear. If the new account logs in fine, your old profile is corrupt; copy your files over and you’re done. This beats hours of blind troubleshooting.
Why does Safe Mode break the login loop?
Safe Mode skips third-party credential providers, startup programs, and non-essential drivers — the exact things that most often crash the logon process. If you can log in via Safe Mode but not normally, the cause is something loading at startup, which narrows the hunt dramatically.
Will creating a new profile delete my files?
No. Your files live in C:\Users<oldname> and stay put when you create a new account. After logging into the new profile, copy Documents, Desktop, Pictures, and other folders across. Only delete the old profile after confirming everything migrated — and empty the Recycle Bin afterwards to reclaim space.
What if the loop affects every account including new ones?
Then it’s system-level, not profile-level: corrupted authentication files, a bad update, or disk errors. Boot into the recovery environment and run SFC/DISM offline, try System Restore, or uninstall the latest update. Our full login loop troubleshooting guide covers the deep cases step by step.