Bypass latest Windows 11 OOBE

README

This guide explains two ways to run the bypass_oobe.bat script during the Windows 11 OOBE (Out-of-Box Experience) screen:
	1.	Using Explorer (easiest)
	2.	Using CMD (Shift+F10)

No PowerShell required.

⸻

What the script does:
	•	Bypasses the Windows 11 OOBE network requirement
	•	Creates a local administrator account
	•	Removes or disables defaultuser0
	•	Marks OOBE as fully completed
	•	Disables OOBE scheduled tasks
	•	Deletes OOBE executables so OOBE cannot return
	•	Reboots automatically when done

Requirements:
	•	A USB drive
	•	The file bypass_oobe.bat copied onto the USB drive
	•	A Windows 11 installation stuck at an OOBE screen

⸻

METHOD 1: Using Explorer (recommended)
	1.	Copy bypass_oobe.bat onto a USB drive.
	2.	Boot Windows until you reach the OOBE screen (for example: “Let’s connect you to a network”).
	3.	Press Shift + F10 to open Command Prompt.
	4.	In the CMD window, type: explorer
	5.	Explorer will open.
	6.	In the left sidebar, click “This PC”.
	7.	Open the USB drive.
	8.	Double-click bypass_oobe.bat.
	9.	The script will run and reboot the system automatically.

After the reboot, Windows will skip OOBE and log directly into the new local administrator user.

⸻

METHOD 2: Using CMD (no Explorer)
	1.	Copy bypass_oobe.bat onto a USB drive.
	2.	Boot Windows until the OOBE screen appears.
	3.	Press Shift + F10 to open Command Prompt.
	4.	Type: diskpart
	5.	Type: list volume
	6.	Identify your USB drive letter (for example D: or E:).
	7.	Type: exit
	8.	Switch to the USB drive, for example: D:
	9.	Type: dir to verify the file is present.
	10.	Run the script: bypass_oobe.bat
	11.	Allow the script to finish. The system will reboot automatically.

⸻

After reboot:
	•	OOBE will be disabled
	•	defaultuser0 will be removed or deactivated
	•	The system will boot into the created local admin account
	•	No Microsoft account or network is required

Notes:
	•	Do not close CMD or Explorer while the script is running.
	•	CMD during OOBE runs elevated, so no extra permissions are needed.
	•	The script works on Windows 11 ARM, x86, and x64 builds, including strict OOBE versions.

bypass_oobe.bat

@echo off
echo =====================================================
echo   WINDOWS 11 ARM OOBE NUKER - FUCK MICROSOFT EDITION
echo =====================================================
echo.

:: ------------ CONFIG ------------
set NEWUSER=LocalUser
set NEWPASS=FuckMicrosoft
:: --------------------------------

echo Creating local admin user "%NEWUSER%"...
net user %NEWUSER% %NEWPASS% /add
net localgroup administrators %NEWUSER% /add
echo User created.
echo.

:: --- Disable OOBE flags ---
echo Disabling OOBE registry flags...
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v SkipMachineOOBE /t REG_DWORD /d 1 /f
reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v SkipUserOOBE /t REG_DWORD /d 1 /f

reg add HKLM\SYSTEM\Setup /v OOBEInProgress /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\Setup /v SetupPhase /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\Setup /v SetupType /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f
reg add HKLM\SYSTEM\Setup /v CmdLine /t REG_SZ /d "" /f

echo OOBE flags disabled.
echo.

:: --- Disable auto login ---
echo Removing auto admin login settings...
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultUserName /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword /f
reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v AutoAdminLogon /f

echo Autologin disabled.
echo.

:: --- Force normal shell ---
echo Fixing Winlogon shell...
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Shell /t REG_SZ /d explorer.exe /f
reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v Userinit /t REG_SZ /d "C:\Windows\System32\userinit.exe," /f

echo Shell fixed.
echo.

:: --- Disable setup tasks ---
echo Disabling setup tasks...
schtasks /Change /TN "\Microsoft\Windows\Setup\SetupCleanupTask" /Disable
schtasks /Change /TN "\Microsoft\Windows\OOBE\FirstLogonAnimation" /Disable
schtasks /Change /TN "\Microsoft\Windows\Setup\gwx" /Disable
schtasks /Change /TN "\Microsoft\Windows\OOBE\HardwareOOBE" /Disable
schtasks /Change /TN "\Microsoft\Windows\Setup\StateRepository-Setup" /Disable
schtasks /Change /TN "\Microsoft\Windows\Setup\SetupFinalize" /Disable
echo Tasks disabled.
echo.

:: --- Remove defaultuser0 if present ---
echo Removing defaultuser0 if it exists...
net user defaultuser0 /delete >nul 2>&1
echo defaultuser0 removed (or never existed).
echo.

:: --- Nuclear delete of OOBE executables ---
echo Nuking OOBE executables...
takeown /F C:\Windows\System32\oobe /R /D Y >nul
icacls C:\Windows\System32\oobe /grant administrators:F /T >nul
del C:\Windows\System32\oobe\*.exe /F /Q
del C:\Windows\System32\oobe\*.dll /F /Q
echo OOBE destroyed.
echo.

echo =====================================================
echo     OOBE Finalized:
echo     User: %NEWUSER%
echo     Password: %NEWPASS%
echo     System will reboot in 10 seconds
echo =====================================================
shutdown /r /f /t 10

hey i have used this method and it bypassed everything, it says localuser but asks for a password to log in. Sorry if this is dumb i have 0 literacy on it and stuff

Hello @hilou2000-cyber

The password for the localuser is: FuckMicrosoft

When you have logged in, you can create a new user and delete this temporary user.

Good luck. Let me know if you have any other questions.

Thank you very much !
I had to go around it by changing the accessibility menu to cmd and temporarily change the password but then it reboots into "let's setup your windows"

You're welcome

i'm back at you, when i put in the password, it goes back to setting up windows, asks for a new user. Which i fill up as i would normally do for a local user, the issue is that when i fill it up, kapoot, something went wrong and can't get off that menu unless i fully reset my computer...

Hi @hilou2000-cyber,

I haven’t used this script since I uploaded it about 8 months ago. At the time, I spent quite a few hours finding a way around Microsoft’s new online account enforcement during Windows setup and turned it into a simple, turnkey solution.

Since then, Microsoft may have updated Windows and changed the setup process again. They invest a lot of effort into pushing users toward Microsoft accounts, so it’s possible that my original method no longer works as intended.

I plan to test the script again when I have some free time (work has been keeping me busy lately). If anything has changed, I’ll update either the script or the description accordingly.

In the meantime, there are other ways to bypass the Windows 11 online account requirement. One of the easiest options is using Rufus. When I originally created this script, Rufus hadn’t yet caught up with Microsoft’s latest changes, but I believe it has since been updated and should work properly again.

You can check out this video guide, which is only about a month old and should still be relevant:

https://www.youtube.com/watch?v=vfj1dSLGM9o

For now, this is probably the fastest way to get started instead of waiting for me to verify and update the script.

Best of luck. Let me know if you still have problems, even with Rufus.