Solved An easier way to install Win 11 22H2 with local user account, network can remain on. Need someone with a DC to test.

EDIT2: Apologies for the confusion. For this method to work, you do need an active Internet connection.

Please note that this method requires Win 11 PRO, not Home.


I've posted this method before and had no feedback saying that it doesn't work, but I would like to understand WHY it works. I need someone with Domain Controller to test this and tell me what happens.

Follow along with the steps below and I'll explain what I am looking for below.

For those with no DC, simply consider this a quick tutorial on how to install with a local account with special requirements such as disabling the network.

Ok, enough of that. Here is the procedure:

Boot from your Windows installation media and continue as usual until you get to this screen:



Normally, you would choose "Set up for personal use". Select "Setup for work or school" instead and then click on "Next".

Select "Sign-in options".



Select "Domain join instead". Don't worry, we are NOT joining a domain. NOTE: This is where I need someone who has a DC to test and tell me what happens. As you will see, if there is no DC present, you end up simply creating a local account here. I want to know what happens if Windows finds a DC on the network.



Enter a user name (the local user name):



Continue with setup as normal.

TIP: On the screen following the one above, you will asked to enter a password. My personal preference is to leave the password blank and create one later. The reason for this is that if you supply a password now, the next screen will ask you to supply 3 security questions and answers. I find that annoying. But do as you wish.

When you are done, you should have a local account, no special steps needed.

This isn't a local DC, but it's Azure Active Directory (AAD) join for enterprises or schools which are cloud-managed.
If you have a normal Windows image with no MDM preparation, the join fails and it falls back to Local user much like the "bad email" hack.

Home doesn't support AAD, which is why the bypass doesn't work. Only Pro & Enterprise.

Okay, so that answers my question. If no DC is available, it falls back to allowing a local user account.

Thanks for the response.

I have a local DC (running on a Synology NAS) which also is providing DNS to my new PC. Nonetheless, Windows setup evidently fails to find it; it doesn't recognize my domain admin login. ("This doesn't look like a work or school email address").

When OOBE asks for "Domain join", they're referring to AAD or cloud-based domains.

To join a local domain on a clean install, you normally have to insert a domain join account and password in the unattended file. There is no part of OOBE that natively handles local domains. You have to do that yourself outside of OOBE.

I had a preinstalled Windows on the new PC, not a customized unattended install iIt worked as I had done it on an earlier Windows 11 Pro installation about a year ago. I finished the setup with a Microsoft account and then joined the domain from that account via Settings.