1. Purpose of This Document
This document explains how to complete Windows setup using a local (offline) account instead of a Microsoft account. It also outlines the advantages and disadvantages of relying solely on a local account for ongoing device use.
This guidance is useful for:
-
Shared or temporary devices
-
Systems intended for hand‑off
-
Privacy‑sensitive environments
-
Lab, kiosk, or utility machines
-
Users who prefer not to tie a device to a personal cloud identity
2. Background
Modern versions of Windows strongly encourage (and sometimes appear to require) signing in with a Microsoft account during setup. However, Windows still supports local accounts. The option is simply hidden behind network‑dependent screens.
To create a local account, the device must be offline during the account‑creation stage of setup.
3. Procedure: Creating a Local Account During Windows Setup
3.1 When Windows Prompts for Wi‑Fi
If the device is online, Windows will not show the offline account option.
Action: Do not connect to Wi‑Fi. If networks appear, disconnect or turn off the router temporarily.
Look for one of the following links:
-
I don’t have internet
-
Skip for now
-
Continue with limited setup
If none appear, proceed to the next section.
3.2 If Windows Forces You to Sign In With a Microsoft Account
Some builds show only a Microsoft sign‑in form with no back button.
To bypass this requirement:
-
Press Shift + F10 to open Command Prompt.
-
Run the following command:
Code
oobe\bypassnro -
The system will reboot and restart the Out‑of‑Box Experience (OOBE).
-
When you reach the network screen again, the “I don’t have internet” option will now be visible.
-
Select it and continue with limited setup.
3.3 Creating the Local Account
Once offline mode is enabled, Windows will prompt for:
-
Username
-
Password (optional)
-
Security questions (if a password is set)
This completes setup without linking the device to a Microsoft account.
4. Pros and Cons of Using Only a Local Account
4.1 Advantages
BenefitDescriptionPrivacyNo personal Microsoft account or cloud identity is tied to the device.Ideal for shared or transferred devicesEasy to hand off without unlinking accounts or synced data.Reduced cloud dependencyNo automatic syncing of personal files, settings, or credentials.Simplified troubleshootingFewer cloud‑based services involved; easier to isolate local issues.Offline‑friendlyDevice remains fully usable without internet access.
4.2 Disadvantages
LimitationDescriptionNo settings or data syncThemes, passwords, browser favorites, and app settings won’t follow you across devices.Limited Microsoft Store functionalitySome apps require a Microsoft account to download or update.No OneDrive integrationCloud backup and file sync are unavailable unless manually configured later.Some features disabledServices like Find My Device, cross‑device clipboard, and cloud restore won’t work.Manual updates for certain appsWithout a Microsoft account, some apps may not auto‑update.
5. When a Local Account Is Recommended
A local account is a strong choice for:
-
Loaner or temporary machines
-
Devices used by multiple people
-
Systems in training rooms, labs, or kiosks
-
Privacy‑focused users
-
Devices that will be resold or reassigned
-
Environments with limited or no internet access
6. When a Microsoft Account May Be Preferable
Use a Microsoft account if you need:
-
Seamless syncing across devices
-
OneDrive cloud backup
-
Microsoft Store purchases or app syncing
-
Cross‑device features (e.g., phone linking, cloud clipboard)
-
Device recovery and tracking features
7. Summary
Windows increasingly encourages cloud‑based identity, but local accounts remain fully supported. By temporarily disconnecting from the internet or using the oobe\bypassnro command, users can complete setup without linking a Microsoft account. This approach is ideal for shared, temporary, or privacy‑sensitive devices, though it comes with trade‑offs in cloud‑based convenience.
