How to Install Windows 11 Without a Microsoft Account (Local Account Setup)

Setting up a new PC used to mean typing a username, picking a password, and reaching the desktop within minutes. Windows 11 changed that expectation. On Home and Pro editions, the Out of Box Experience, commonly shortened to OOBE, now nudges almost everyone toward signing in with a Microsoft account before it will let you past the initial screens. For plenty of users that is a fine trade-off. For plenty of others, it feels like being forced to hand over an email address and cloud identity just to use a computer they already own.

The good news is that a local account has never actually been removed from Windows 11. It is still a fully supported account type, and Windows still runs perfectly well on one. What changed is discoverability: Microsoft buried the option deep enough in the setup flow that most people never see it. This guide walks through every current, verified way to reach that option, from the simplest click-through trick to the more technical routes IT professionals rely on for bulk deployment, and it explains exactly what changes on your PC once you choose a windows 11 local account over a cloud-connected one.

Why Windows 11 Pushes You Toward a Microsoft Account

The mechanism behind this behavior is simpler than most people assume. During setup, OOBE checks whether the PC has an active network connection. If it detects one, on Home and most Pro installations, it routes you directly into the Microsoft account sign-in flow and does not display a local account option on that screen at all. This check is often referred to in enthusiast and IT circles as the network requirement, or NRO for short, and it is the exact thing that later bypass methods are named after.

Microsoft’s stated reasoning is that a connected account unlocks features many users genuinely want: OneDrive backup for the Desktop, Documents, and Pictures folders, settings sync across devices, Find My Device, automatic BitLocker recovery key escrow, and a single sign-in that carries across the Microsoft Store, Xbox, and Microsoft 365. Those are real benefits for someone who lives inside the Microsoft ecosystem across a phone, a tablet, and a laptop.

The friction shows up for a different group of users entirely: people building a kiosk or shared family PC, IT administrators imaging machines that will be joined to a different identity system later, privacy-conscious users who do not want a cloud identity tied to their hardware, gamers who just want a clean local login, and anyone reinstalling Windows on a machine with no working network driver yet. For all of these situations, a windows 11 offline account remains the more practical choice, and Microsoft has, so far, left the underlying local account architecture completely intact even while making it harder to reach during setup.

It is also worth understanding what happens automatically if you do sign in with a Microsoft account on a TPM-equipped PC, since it is not always obvious from the setup screens. Device encryption is frequently switched on in the background, and the recovery key is uploaded and stored against that Microsoft account. On top of that, the Desktop, Documents, and Pictures folders are commonly redirected into OneDrive without a clearly worded opt-in, which is why some users later discover their local files have quietly become cloud placeholders. None of this happens on a genuine local account, which is one of the strongest practical reasons people search for a windows 11 setup without microsoft account in the first place.

There is also a licensing nuance worth understanding, since it explains why Home and Pro behave differently from Enterprise and Education. Business-oriented editions of Windows 11 are designed around domain controllers, Microsoft Entra ID, and centralized device management, so a local account was never pushed aside there in the same way, because IT departments already have their own identity systems and have no interest in every workstation phoning home to a personal Microsoft account. Home and Pro, aimed squarely at individual consumers, are where Microsoft has invested the most effort in nudging people toward a connected account, which is precisely why the workarounds in this guide matter most for exactly those two editions.

Local Account vs Microsoft Account: What Actually Changes

Before walking through the setup methods, it helps to know exactly what you gain and give up by choosing a local account. Neither option is universally correct; the right choice depends entirely on how you use the machine day to day.

Notice that the local account is not missing security. It still supports Windows Hello, a PIN, biometric sign-in where hardware allows it, and full BitLocker encryption if you choose to enable it manually. What it lacks is cloud convenience, and for a shared computer, an offline workstation, or a privacy-first setup, that trade-off is usually the entire point.

Method 1: Set Up Windows 11 Without Internet

The most straightforward approach for a windows 11 no internet setup is simply to make sure the PC has no active network connection when it reaches the “Let’s connect you to a network” screen. Unplug the Ethernet cable before powering on, or if you are on Wi-Fi, do not connect to any network when prompted. On some builds, this alone is enough for a “Sign in with Radius server” style message to be replaced with an “I don’t have internet” link, which then leads to a “Continue with limited setup” option and, finally, the familiar “Who’s going to use this device?” screen where you create a local username and password.

This method has become less consistent than it used to be. Newer builds sometimes hide the “I don’t have internet” link even without a connection, or they display it only after a short delay, or they loop back to asking you to connect. If you reach the network screen and do not see any offline option at all, do not keep clicking around hoping it appears; move straight to the command-based bypass covered next, since it forces the offline path to reappear reliably rather than depending on how a particular build happens to behave that day.

If you are reinstalling Windows on a desktop PC and want to guarantee no network is detected, physically unplugging the Ethernet cable is more reliable than trying to cancel a Wi-Fi connection through the on-screen prompts, since some OOBE builds auto-connect to a previously saved network before you get the chance to back out. For laptops, a physical Wi-Fi switch or airplane mode, toggled before the setup process even begins, achieves the same result.

Method 2: The OOBE BypassNRO Command

This is currently the most reliable and widely documented method for a windows 11 bypass microsoft account workflow, and it works by triggering the exact registry value that governs the network requirement check described earlier. It is not an exploit or a hidden hack in the traditional sense; it is a built-in Microsoft script that ships inside every Windows 11 installation image, just not exposed through the normal interface.

1. Boot from your Windows 11 installation media and proceed through language and region selection as normal.
2. When you reach the “Let’s connect you to a network” screen, press Shift and F10 together to open a Command Prompt window. On some laptops this is Shift, Fn, and F10.
3. Type the command exactly as written: oobe\bypassnro and press Enter.
4. The PC will automatically restart and return to the beginning of OOBE.
5. When you reach the network screen again, look for an “I don’t have internet” link near the bottom of the screen and select it.
6. Click past the limited-setup warning, accept the license agreement, and you should now reach “Who’s going to use this device?” where you can create a local username and password without ever touching a Microsoft sign-in field.

Under the hood, this command runs a script located at C:\Windows\System32\OOBE\BypassNRO.cmd, and all it does is write a single registry value, setting HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE\BypassNRO to 1. That value tells the setup process it is allowed to offer the offline path even when a network connection is technically present, which is why staying disconnected from Wi-Fi after running the command is still worth doing for reliability, even though it is not always strictly required.

Reliability of this exact command has varied across builds throughout 2025 and 2026. Microsoft appeared to quietly break it in some preview and early 25H2 builds, then it returned to working on subsequent production releases. As of the most recent 25H2 cumulative updates, it continues to function on standard release media for most users, but because Microsoft has shown a pattern of adjusting this behavior between updates, it is sensible to have a backup method ready rather than assuming it will always work identically on every build you encounter.

Method 3: Manual Registry Edit as a Backup

If the bypassnro shortcut ever stops responding on a particular build, you can achieve the identical result by editing the registry value directly, which is useful to know since it is the same mechanism the shortcut command triggers behind the scenes.

1. At the network connection screen, press Shift and F10 to open Command Prompt.
2. Type the following command exactly, then press Enter: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1 /f
3. Type shutdown /r /t 0 and press Enter to restart the PC immediately.
4. After the restart, return to the network screen, choose “I don’t have internet,” then “Continue with limited setup,” and proceed to create your local account as usual.

This is effectively the same fix as Method 2, written out manually, and it is worth keeping as a note on hand because it works even in edge cases where the shortcut command has been removed or renamed in a specific Windows build. Typing the full registry command is only marginally slower and depends on nothing beyond Command Prompt and regedit access, both of which are always available during OOBE regardless of what Microsoft changes in the user-facing shortcuts.

Method 4: Build a Local-Account USB Installer With Rufus

For anyone who installs Windows more than once, or who wants a solution that does not depend on typing commands during setup, patching the installation media in advance is the cleanest long-term fix. Rufus is a free, open-source USB bootable drive creator that has added dedicated Windows 11 customization options specifically to address this exact restriction, and it remains the tool most consistently recommended across enthusiast and IT communities for this purpose.

1. Download the official Windows 11 ISO from Microsoft’s software download page.
2. Download the latest version of Rufus and insert a USB drive of at least 8GB.
3. Open Rufus, select your USB drive, and choose the Windows 11 ISO as the boot selection source.
4. When Rufus detects a Windows 11 image, it will present a “Windows User Experience” customization dialog. Check “Remove requirement for an online Microsoft account.”
5. Optionally, check “Create a local account with username” and type the account name you want pre-filled, which skips the account-creation screen entirely.
6. While in this dialog, you can also enable related quality-of-life options, including removing hardware requirement checks for unsupported PCs, disabling automatic BitLocker device encryption, and skipping the privacy questions screen.
7. Click Start to build the USB drive, then boot the target PC from it and complete Windows Setup normally. The Microsoft account sign-in screen will not appear.

Behind the scenes, Rufus achieves this by generating and injecting an autounattend.xml answer file into the installation media, which is the same official Microsoft provisioning mechanism used in enterprise deployment tools, just packaged into a simple checkbox interface. Because the modification lives on the USB drive rather than depending on you remembering a command during setup, this remains reliable across almost every Windows 11 build, and it is the option most often recommended for anyone who is not comfortable typing commands live during OOBE. One caveat worth knowing: after installation, staying disconnected from the internet during the very first boot screens still improves reliability, since some builds re-check network status before finishing account creation even with the patched media.

Method 5: The Domain Join Trick (Windows 11 Pro Only)

Windows 11 Pro, Enterprise, and Education editions include a legitimate, Microsoft-supported path to a local account that Home edition does not offer. On the network screen, instead of connecting to Wi-Fi, look for a small link that reads “Join a domain instead,” typically found near the bottom of the screen once you are connected to a network or have selected an offline path.

Selecting this option is designed for business environments joining Active Directory domains, but choosing it also unlocks the classic local account creation screen as a side effect, even if you have no domain to join. You can proceed through the domain-join prompt, and Windows will still let you set up a standard local account instead if you back out or simply create the account through the presented fields. This route has remained one of the most consistent workarounds precisely because Microsoft cannot remove it without breaking legitimate enterprise domain-joining scenarios that businesses depend on daily.

The limitation is edition-specific: this trick is not available on Windows 11 Home, since the domain-join feature itself is a Pro-tier capability tied to Active Directory support. If your PC shipped with Home edition and you want this particular route, you would need to upgrade to Pro first, which somewhat defeats the purpose for users simply trying to avoid extra account setup. For Home edition machines, the BypassNRO command or the Rufus method remain the more practical choices.

Method 6: Unattended Answer Files for IT Admins and Bulk Deployment

System administrators imaging multiple machines rarely want to type commands by hand at every single OOBE screen. For that scenario, the same underlying setting Rufus configures automatically can be added directly to an unattend.xml answer file, created through the Windows System Image Manager included in the Windows Assessment and Deployment Kit, or hand-written using Microsoft’s documented OOBE unattend settings.

An answer file placed at the root of the installation USB, or injected into a deployment share used by tools like MDT or SCCM, can pre-populate the local account username and password, skip the privacy settings screens, and set the BypassNRO registry value automatically before OOBE ever loads. This is the approach most consistent with Microsoft’s own supported provisioning tools rather than relying on a manually triggered command, and it is the method least likely to break unexpectedly after a future Windows update, since it uses the same official mechanism Microsoft documents for enterprise deployment scenarios.

One practical warning worth passing along: mismatched combinations of a newer Windows 11 image and an older or incorrectly formatted answer file can occasionally cause Setup to throw a “Windows could not parse or process the unattended answer file” error. Testing any custom answer file on a non-critical machine or a virtual machine before rolling it out across a fleet of devices avoids turning a time-saving deployment method into a troubleshooting exercise on production hardware.

Comparing All Six Methods Side by Side

With several valid paths available, choosing the right one usually comes down to how often you install Windows, which edition you are running, and how comfortable you are with Command Prompt.

Is a Local Account Less Secure Than a Microsoft Account?

This question comes up constantly, and the honest answer is that a local account is not inherently less secure; it simply shifts responsibility for a few things from Microsoft’s servers back onto you. Windows Hello, the biometric and PIN sign-in system, works identically on a local account as it does on a Microsoft account, since it is a device-level credential rather than something tied to cloud identity. Fingerprint and facial recognition sign-in, where the hardware supports it, function exactly the same way regardless of which account type sits behind them.

Where the difference actually shows up is in recovery. A Microsoft account can reset a forgotten password through an online recovery flow at account.microsoft.com, using a secondary email or phone number. A local account has no equivalent cloud fallback, so if you forget the password and never set up the three security questions Windows offers during account creation, you are looking at a much harder recovery process, potentially involving a password reset tool run from installation media or, in the worst case, a clean reinstall. Anyone choosing a local account should treat those security questions as mandatory rather than optional, and consider keeping a written note of the answers somewhere safe.

BitLocker works the same way in reverse. A Microsoft account automatically escrows the recovery key to the cloud, which is genuinely convenient if a drive ever gets locked after a hardware change. A local account requires you to manually save that recovery key, either as a printed copy, a file on a separate USB drive, or an entry in a password manager, since there is no account to silently back it up for you. This is not a weakness in the encryption itself, only a difference in where the safety net lives, and it is entirely manageable as long as you treat the recovery key with the same care you would give a house key.

From a pure malware and network-attack standpoint, a local account and a Microsoft account face identical exposure, since Windows Defender, the firewall, Secure Boot, and every other operating-system-level protection apply equally regardless of sign-in type. If anything, some privacy-focused users consider a local account marginally safer in one specific sense: there is no cloud-linked identity that a compromised Microsoft account elsewhere could use to gain a foothold on the local device, since the two are never connected in the first place.

Creating a Local Account After Windows Is Already Installed

Not everyone needs to bypass anything at setup time. If a PC was already set up with a Microsoft account and you want to switch afterward, Windows 11 still supports this through the normal interface, no command tricks required. Open Settings, go to Accounts, select Your info, and choose “Sign in with a local account instead.” You will be asked to re-authenticate with the current Microsoft account, then walked through creating a new local username, password, and security questions.

It is worth being aware that this conversion detaches the cloud identity from the sign-in process, but it does not necessarily strip every trace of the Microsoft account from the device; some connected services and the original user profile folder structure may remain associated with it in the background unless you separately remove the account under Settings, Accounts, Other users. For a completely clean separation, many users prefer creating a brand-new local account rather than converting an existing Microsoft-linked profile.

To create an additional windows 11 create local account entry without touching the primary sign-in at all, go to Settings, Accounts, Other users, and select “Add account.” Choose “I don’t have this person’s sign-in information,” then “Add a user without a Microsoft account” on the following screen. This path works entirely offline and does not require disconnecting from the internet, since it is not gated by the same OOBE network check that governs the very first account on a fresh installation.

For advanced users, the same result is achievable through Command Prompt using net user commands, or through Computer Management under Local Users and Groups on Pro, Enterprise, and Education editions, which also allows setting account expiration, group membership, and password policy options not exposed in the standard Settings app.

What to Check Immediately After a Local Account Install

Reaching the desktop on a windows 11 local account setup is not quite the finish line. A handful of settings deserve a quick check to make sure the installation is behaving the way you expect, since some defaults do not fully reset just because you skipped the Microsoft sign-in.

Open Settings, System, About, and confirm the account listed is your local username rather than an email address. Then check BitLocker status by searching for “Manage BitLocker” in the Start menu; a genuine local account install should leave the system drive unencrypted by default, but Copilot+ PCs with a Pluton security processor occasionally enable device encryption automatically regardless of account type. If you see the drive listed as encrypted and you did not choose that, suspend or fully disable it, since a recovery key generated without a Microsoft account to store it against can leave you locked out of your own data permanently if the key is lost.

Next, review Settings, Accounts, Windows Backup, and confirm OneDrive folder syncing is off unless you intentionally want it. Local accounts generally do not trigger automatic folder redirection, but it is worth a direct check rather than an assumption, particularly after a feature update that may reset certain defaults. Finally, revisit Settings, Privacy & security, and walk through diagnostic data, advertising ID, and app permission settings, since a local account does not automatically apply more conservative privacy defaults than a Microsoft account does; those settings still need to be configured deliberately either way.

Troubleshooting When the Bypass Doesn’t Work

Because Microsoft periodically adjusts OOBE behavior between builds, it is common for a method that worked perfectly on one installation to behave differently on the next, particularly right after a new feature update rolls out. If the bypassnro command appears to run without any error but the offline link still does not reappear, restart the command and, this time, make absolutely certain no network cable is plugged in and no Wi-Fi network is selected before rebooting; some builds only honor the registry value when the network truly is unreachable rather than merely uncommitted to a specific connection.

If Command Prompt itself will not open when you press Shift and F10, some OEM installation images disable this shortcut deliberately as part of a customized deployment. In that situation, the Rufus method becomes the more dependable choice, since it modifies the installation media itself rather than relying on an interactive command during setup, sidestepping the disabled shortcut entirely.

If you are stuck in a loop where the setup keeps demanding a working network connection with no offline link visible under any circumstance, confirm you are using genuine, unmodified Microsoft installation media rather than an OEM recovery partition, since some manufacturer-customized recovery images enforce network sign-in more aggressively than the standard public ISO does. Downloading a fresh ISO directly from Microsoft’s official Windows 11 software download page and creating new installation media from it resolves this in the majority of reported cases.

Common Mistakes That Break the Bypass

A surprising number of failed attempts trace back to a handful of avoidable mistakes rather than an actual Microsoft patch. Typing the command with a forward slash instead of a backslash, for instance, oobe/bypassnro instead of oobe\bypassnro, will simply return an error, since Command Prompt treats that as an invalid path rather than the intended script call. Copy-pasting the command from a source that silently substitutes a curly or stylized apostrophe can also cause it to fail in ways that look identical to the feature being broken, when the real issue is just a mismatched character.

Another common error is reconnecting to Wi-Fi too early, out of habit, right after the restart triggered by the bypass command. Muscle memory leads many users to click the first available network the moment the list appears, which immediately routes setup back into the Microsoft account flow before the offline link has a chance to load. Waiting for the “I don’t have internet” link to actually appear, and clicking that first, avoids this entirely.

Finally, some users assume a windows 11 without sign in setup means Windows will never ask for any credentials again, which is not quite accurate. A local account still requires a password to sign in each session, the same as a Microsoft account would, and Windows will still occasionally prompt you to add a recovery email or phone number for account recovery purposes. Declining those prompts is entirely optional and does not affect functionality, but expect to see them appear periodically as gentle reminders rather than mandatory steps.

Quick Reference Checklist

Frequently Asked Questions

Is it still possible to install windows 11 without microsoft account in 2026?

Yes. Local accounts remain a fully supported account type in Windows 11, and the bypassnro command, Rufus-based installation media, and the Pro-edition domain trick all continue to work on current builds. Microsoft has made the option harder to find rather than removing it, so a short detour through Command Prompt or a pre-configured USB drive still gets you a working windows 11 local account setup.

Does windows 11 bypassnro still work on the latest 25H2 builds?

It works on most current 25H2 release media, though reliability has fluctuated across specific builds throughout 2025 and 2026. If the command does not trigger the offline link on a particular installation, disconnecting fully from any network before restarting, or switching to a Rufus-prepared USB drive, resolves the vast majority of cases without needing any further troubleshooting.

Will a windows 11 offline account limit which apps I can use?

No, a local account runs every desktop application exactly the same as a Microsoft account would. The only difference appears with apps or services that specifically require cloud sign-in for their own functionality, such as OneDrive syncing, Xbox cloud saves, or Microsoft 365 subscription activation, and even those simply prompt for a Microsoft sign-in within the app itself when needed, without affecting the rest of the operating system.

Can I switch from a Microsoft account back to a windows 11 local account later without reinstalling?

Yes. Go to Settings, Accounts, Your info, and select “Sign in with a local account instead,” then confirm your current Microsoft account credentials and set up a new local username and password. This does not require reinstalling Windows or using any bypass command, since it is a fully supported, built-in switch available through the standard interface at any time.

Is the windows 11 oobe bypass safe to use, or does it void any warranty or support?

It is safe and does not affect hardware warranty in any way, since it only changes a setup-time registry value that Microsoft itself ships inside the installation image. It has no impact on Windows Update eligibility, driver support, or your ability to receive ongoing windows 11 security updates once installed.