Windows 11 Install Local Account Setup Bypass 2026 (Including TPM bypass)

Windows 11 now pushes you into a Microsoft account during setup, and refuses to install at all on hardware without TPM 2.0 and Secure Boot. Four working methods below get you a local account on a machine you own — pick the one that matches your situation.

Microsoft has made it increasingly difficult to install Windows 11 without a Microsoft account. For privacy-conscious users, or IT professionals setting up offline machines, that restriction is a serious hurdle.

Which method do you need?

• You just want a local account: use Method 1. It is the fastest way to skip the online sign-in on any standard PC.
• Your PC is "unsupported" (TPM or CPU errors): use Method 2 (Rufus). You need to patch the installer to ignore the hardware requirements and the account check.

Method 1: The quickest fix (command line)

Best for: standard PCs stuck at the "Let's connect you to a network" screen. Bypasses: the Microsoft account requirement only.

If you are already in Windows setup and cannot proceed without Wi-Fi, this is the instant solution.

1. Open a command prompt

   At the "Connect to a network" screen, press Shift + F10 on your keyboard.

2. Run the bypass

   Type cd oobe and press Enter, then type bypassnro and press Enter.

3. Let it restart

   Your computer will restart automatically.

4. Go offline first

   Crucial step: make sure the computer is disconnected from the internet — unplug the Ethernet cable or turn off your router temporarily.

5. Choose "I don't have internet"

   When you return to the network screen, the new option will be there.

6. Continue with limited setup

   Select it to create your local account.

Method 2: The total bypass (Rufus)

Best for: old hardware, "unsupported" PCs, or clean installs. Bypasses: Microsoft account + TPM 2.0 + Secure Boot + RAM checks.

If Method 1 doesn't work, or your computer is failing the Windows 11 system requirements on TPM or CPU, you need to rebuild the USB installer.

1. Download the Windows 11 ISO from the official Microsoft website.
2. Download Rufus, a free bootable USB tool.
3. Insert your USB drive — 16GB or larger recommended.
4. Open Rufus and select your downloaded Windows 11 ISO.
5. Click Start. A "Windows User Experience" dialog will appear.
6. Tick the boxes listed below, then let Rufus create the drive. When you boot from this USB it will skip all the checks automatically.

Your Rufus window should look similar to this:

Device:           [Your USB Drive (e.g., 16 GB)]
Boot selection:   [Your Windows 11 ISO file name]
Image option:     Standard Windows Installation
Partition scheme: GPT
Target system:    UEFI (non CSM)
...
[Ready]

Method 3: The manual registry hack (advanced)

Best for: troubleshooting hardware blocks without Rufus.

If the installer is blocking you on hardware requirements — TPM or Secure Boot — and you cannot use Rufus, you can edit the registry mid-installation.

1. At the "Install Now" or language selection screen, press Shift + F10 to open a command prompt.
2. Type regedit and press Enter.
3. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup
4. Right-click the Setup folder, select New > Key, and name it LabConfig.
5. Inside LabConfig, right-click and create the following DWORD (32-bit) values, each set to 1:
   • BypassTPMCheck
   • BypassSecureBootCheck
   • BypassRAMCheck
6. Close the Registry Editor and command prompt, then carry on with the installation.

Method 4: Advanced automation (FlyOOBE)

Best for: IT professionals and system integrators.

If you want to automate the OOBE (out-of-box experience) customisation without rebuilding the ISO, use a specialised script such as FlyOOBE. FlyOOBE is an open-source script by developer builtbybel that modifies the Windows setup environment on the fly.

1. Download the script and place it on a separate USB drive.
2. When you reach the Windows Setup screen, insert the USB drive.
3. Press Shift + F10 to open the command prompt.
4. Navigate to your USB drive — type D: then dir to find it.
5. Run the script to strip bloatware and bypass the account requirement in one pass.

The "why": privacy, surveillance and the kill chain

Forcing a Microsoft account tethers the operating system to a cloud identity.

The shift away from local accounts is not just about user experience — it is a fundamental change in how the OS operates. Tying the login to a cloud identity creates what privacy experts call a "kill chain".

The privacy risk

When your login is tied to a Microsoft account:

• BitLocker encryption: your drive encryption keys are automatically uploaded to Microsoft's servers, stored in OneDrive.
• Surveillance: the OS can more easily sync telemetry, tying your usage habits to your real identity rather than an anonymous hardware ID.
• Control: it enables remote management features that many people explicitly do not want on a personal device.

Expert analysis

Privacy advocate Rob Braxman (The Internet Privacy Guy) has highlighted this as a critical turning point in personal computing. The combination of TPM (Trusted Platform Module) and mandatory online accounts creates a surveillance infrastructure that is difficult to opt out of.

For users who refuse to accept those terms, two options remain:

1. Use the bypass methods above to maintain a severed, offline Windows experience.
2. Migrate to Linux. Distributions such as Linux Mint or Ubuntu offer a modern experience without the corporate tethering.

Archived and obsolete methods

• The "fake email" trick: typing test@test.com or no@thankyou.com to force an error. Currently patched in 24H2.
• Task Manager kill: using Task Manager to kill the "Network Connection Flow" process. Often results in an unstable install.
• OOBE\BYPASSNRO: a command-line trick where it was important not to let the PC connect by network cable or Wi-Fi. You pressed Shift + F10 to open a command prompt during setup at the point where you enter your network details, typed OOBE\BYPASSNRO, and the PC restarted — allowing you to click "I don't have internet" and create a local account. This is now blocked when used as a single line.
• start ms-cxh:localonly: another command-line trick that opened the "create a local account" screen directly. Typically you would install and go online first, then at the "Sign in" or "Let's add your Microsoft Account" screen press Shift + F10 (or Shift + Fn + F10 on some laptops) to get a command prompt, and type start ms-cxh:localonly to allow local account creation. This is also being blocked.

Further reading

Speculation from reputable sources suggests that signing in during installation creates a permanent device ID — a hardware identifier bond between your PC and Microsoft's user and device master database, along with the decryption keys, which can be very bad for privacy and security.

Rob Braxman has a good video explaining some of these concerns: https://www.youtube.com/watch?v=t1eX_vvAlUc. It discusses the TPM 2.0 chip, a requirement for Windows 11, as a surveillance tool rather than purely a security feature. He claims that through features such as BitLocker, Microsoft forces users to permanently link their computer's unique hardware ID (Endorsement Key) to their Microsoft account [03:37]. The video alleges this allows Microsoft to route all security operations through its cloud [05:31] and use "remote attestation" to verify your hardware and software, potentially blocking other operating systems such as Linux [10:04]. Braxman concludes that this system, combined with AI (Copilot) features like Windows Recall [11:44], creates a "kill chain" to monitor user behaviour and control their computers [13:52].