PowerShell: Set Up a New Windows Laptop Without a Microsoft Account
Setting up a new Windows 11 laptop should be simple.
Turn it on. Create a user. Get to the desktop.
Except Microsoft really, really wants you to use a Microsoft account.
For personal devices, using a Microsoft account can provide some useful features. But for IT administrators, testing machines, lab computers, temporary systems, or devices that simply don’t need a cloud-connected account, creating a Microsoft account just to get through Windows setup can be unnecessary.
Fortunately, depending on your version of Windows 11, you may still be able to create a local Windows account directly from the Out-of-Box Experience (OOBE).
Here’s one of the easiest methods.
Why Use a Local Account?
There are plenty of situations where an IT administrator may not want to associate a laptop with a personal or organizational Microsoft account during initial setup.
For example:
Preparing a computer before assigning it to someone.
Building a test or lab machine.
Troubleshooting a new computer.
Creating a temporary administrative account.
Preparing equipment that will later be joined to a domain or management platform.
Avoiding associating an IT administrator’s Microsoft account with an end user’s computer.
Setting up a computer that simply doesn’t need Microsoft’s consumer cloud services.
A local account gives you access to Windows without tying the initial Windows profile to an online Microsoft account.
Method 1: Open the Local Account Setup
Start the Windows 11 laptop and proceed through the normal setup process.
When Windows reaches the portion of OOBE asking you to sign in or create a Microsoft account, press:
Shift + F10
On some laptops you may need:
Shift + Fn + F10
This should open Command Prompt over the Windows setup screen.
Now enter:
start ms-cxh:localonly
Press Enter.
If supported by your Windows build, Windows should launch the local account creation interface.
You can then create your local Windows username and password without signing in with a Microsoft account.
That’s it.
No new Microsoft account. No personal IT account attached to the machine. Just a normal local Windows user.
Method 2: OOBE\BYPASSNRO
Another method that has traditionally worked with Windows 11 is bypassing the OOBE network requirement.
Before using this method, disconnect the computer from the Internet.
If you’re using Ethernet, unplug the network cable. If you’re using Wi-Fi, make sure the machine isn’t connected to a wireless network.
From Windows OOBE, press:
Shift + F10
Then run:
OOBE\BYPASSNRO
Press Enter.
The computer should restart and return to Windows setup.
On supported Windows builds, you should now have additional options allowing you to continue setup without an Internet connection and create a local user account.
A Quick Warning About This Method
Microsoft has been making changes to the Windows 11 Out-of-Box Experience and has removed or restricted some of the traditional local-account bypass methods in newer Windows builds.
That means:
OOBE\BYPASSNRO
may not work on every Windows 11 version you encounter.
The same warning applies to other OOBE shortcuts: Microsoft can change these behaviors through Windows releases and setup updates.
If one method doesn’t work, check which Windows 11 build you’re deploying before assuming you’ve done something wrong.
Sometimes Microsoft simply moved the cheese. Again.
Local Accounts Aren’t Necessarily Permanent
Creating a local account during setup doesn’t mean the computer has to stay that way forever.
Once you’re at the Windows desktop, you can still configure the machine however your environment requires.
You can later:
Connect a Microsoft account.
Join Microsoft Entra ID.
Enroll the computer into Microsoft Intune.
Join an Active Directory domain.
Create additional local or administrative accounts.
Install applications and updates.
Perform testing or troubleshooting.
Remove the temporary local account when you’re finished.
You’re simply getting through the initial Windows setup without unnecessarily tying the computer to a Microsoft account.
This Can Be Especially Handy for IT
One of my biggest reasons for using this method is preparing or troubleshooting computers before they’re assigned to their actual users.
I don’t want my personal Microsoft account attached to somebody else’s laptop.
I also don’t want to create a random Microsoft account just because Windows setup insists that I need one.
A local account gives IT a clean way to get to the desktop, perform whatever work is necessary, and prepare the computer for its actual deployment process.
It’s also handy when you just need a Windows machine for testing.
Create a local account, get to the desktop, do what you need to do, and move on with your day.
One Important Security Reminder
If you’re creating a temporary local administrator account on a company computer, don’t forget about it.
Use a strong, unique password and make sure temporary accounts are removed or disabled before the computer is placed into production.
For managed corporate environments, local administrator credentials should ideally be managed using a solution such as Windows LAPS rather than maintaining the same local administrator password across multiple computers.
A convenient setup shortcut shouldn’t turn into a forgotten administrator account six months later.
Final Thoughts
Microsoft continues to push Windows toward cloud-connected accounts, and there are legitimate benefits to using them.
But there are also legitimate reasons why an administrator may simply need a local Windows account.
For IT testing, troubleshooting, staging, lab environments, or certain deployment workflows, knowing how to get through Windows OOBE without creating another Microsoft account can save quite a bit of unnecessary work.
Just remember that Microsoft continues to modify the Windows 11 setup experience, so these shortcuts may change as new Windows builds are released.
For now, it’s another useful Windows trick worth keeping in the IT toolbox.
Hope you find this helpful!
