Why Your Windows 11 Boot Loops Through OOBE and How to Escape

Quick fix: If Windows 11 keeps booting back to the “Hi, let’s set up your account” (OOBE) screen instead of your desktop, the user profile data is unreadable. At any OOBE step, press Shift + F10 to open Command Prompt. Run oobe\bypassnro — reboots without forcing MSA. Or net user administrator /active:yes to enable the built-in admin and sign in via that.

You boot. Windows shows the OOBE setup wizard instead of your sign-in screen. You complete it. Reboot. Same OOBE screen again. The cause is usually a damaged user profile or a stuck OOBE flag in the registry. Recovery requires booting outside of OOBE’s normal flow.

What causes this

OOBE (Out-of-Box Experience) is the first-boot setup. It runs when registry flag HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE\SetupPhase is non-zero. If OOBE crashes mid-flow, or completes but doesn’t clear the flag, Windows reruns OOBE on next boot.

Less commonly: a corrupted user profile causes Windows to skip your existing account and launch OOBE again.

Method 1: Escape OOBE via Shift+F10 and bypass

The standard escape.

1. At any OOBE screen (region selection, keyboard, network), press Shift + F10. Command Prompt opens.
2. To skip Microsoft Account requirement (forces local account):

   oobe\bypassnro

   PC reboots. OOBE restarts, but now “I don’t have internet” option appears, allowing local account creation.

3. Alternative: enable the built-in Administrator account directly:

   net user administrator /active:yes

   Reboot. Sign in as Administrator (no password by default).

4. Once signed in: complete account setup via Control Panel → User Accounts. Or transfer files from old user profile in C:\Users\<name>.
5. For very stuck OOBE: launch regedit from Shift+F10 command prompt. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OOBE. Set OOBEInProgress = 0 and SetupPhase = 0. Close. Reboot.

This is the most reliable escape.

Method 2: Boot Safe Mode and repair user profile

For damaged profile.

1. At OOBE screen: Shift+F10 → Command Prompt → type shutdown /r /o /f /t 00 to reboot to advanced startup options.
2. From recovery: Troubleshoot → Advanced options → Startup Settings → Restart → press 4 for Safe Mode.
3. Safe Mode may bypass OOBE if it’s due to network/driver issue. Sign in as built-in Administrator if standard sign-in fails.
4. In Safe Mode: open regedit. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Each subkey is a user account with SID.
5. Find the SID with ProfileImagePath matching your profile. If State is non-zero, profile is marked as broken. Set to 0.
6. For SIDs with .bak suffix: indicates corrupted profile. Rename without .bak (after backing up).
7. Reboot. Try normal sign-in.

This is the right path for profile-level corruption.

Method 3: Create a new user account via Command Prompt

For when you can’t escape OOBE any other way.

1. At OOBE, Shift+F10 → Command Prompt.
2. Enable built-in Administrator: net user administrator /active:yes.
3. Or create new admin: net user newadmin password /add then net localgroup administrators newadmin /add.
4. Set OOBE flag to complete:

   reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE" /v OOBEInProgress /t REG_DWORD /d 0 /f
   reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE" /v SetupPhase /t REG_DWORD /d 0 /f

5. Reboot. Should reach sign-in screen with newadmin (or Administrator) account.
6. Sign in. Investigate why original profile broke; migrate files to new account if needed.
7. Once stable: disable built-in Administrator: net user administrator /active:no. Don’t leave it enabled long-term.

This is the recovery path when other methods fail.

How to verify the fix worked

• Reboot. Sign-in screen appears (not OOBE wizard).
• Sign in successfully. Reach desktop.
• Run reg query "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE". SetupPhase = 0, OOBEInProgress = 0.

If none of these work

If OOBE keeps recurring despite registry edits: System file corruption: from Shift+F10 cmd, run sfc /scannow. May not work in OOBE phase. For PCs where Shift+F10 doesn’t open cmd: keyboard issue or disabled by setup. Try Ctrl+Shift+F10 or external keyboard. In-place upgrade as repair: from Shift+F10 cmd, try start D:\setup.exe if Windows install media is mounted. Run setup.exe directly, keeping files and apps. For irrecoverable OOBE: clean install. Save data via Linux Live USB first if possible. For PCs with multiple OOBE-triggering causes: TPM reset, account corruption, hardware change. Reset This PC → Cloud download fixes most.

Bottom line: Shift+F10 at any OOBE screen opens Command Prompt. Use oobe\bypassnro for local account, net user administrator /active:yes for built-in admin, or registry edits to clear OOBE state.