Another method for avoiding using a Microsoft account during setup

[timeshifter]

Windows 11 install without Microsoft account (2025) - Pureinfotech

To install Windows 11 (Home or Pro) without a Microsoft account, use a fake email for the account, or in Pro, use "Domain join instead."

pureinfotech.com

Summary, when it asked for my Microsoft account I disabled the WiFi on the laptop by pressing F12 which put in in Airplane mode. Then I hit back. Was able to set up a regular old Local Account.

There was another method that involved getting to Task Manager during OOBE and killing a network process that I'd used before, but I think I saw that that method doesn't work anymore.

This method just worked for me.

 

[callthatgirl]

I wish I could get to my clients with this before they setup. Almost all just log right on in with their business email and then starts their hellish nightmares.

 

[Diggs]

A problem I am seeing is almost without exception when they use their email account for Win11 they are almost always using their email password for that account. Residential users don't seem to understand they should use a different password.

 

[cypress]

I wish I could get to my clients with this before they setup. Almost all just log right on in with their business email and then starts their hellish nightmares.

Yup, seen this as well. Very frustrating.

 

[fincoder]

There was another method that involved getting to Task Manager during OOBE and killing a network process that I'd used before, but I think I saw that that method doesn't work anymore.

No that method still works, no way it could be blocked considering I'm still using the same installer ISO and factory images would also be built with original installer. Maybe after the first feature update comes through things could change.

The hotkey for Airplane Mode would only work for factory image OOBEs, but not for generic installs with downloaded ISO.

 

[timeshifter]

The original method still works too according to my friend.

Whether it’s the airplane mode switch or whatever, you need to give it Internet then break it. Use Ethernet then unplug it, unplug your router or access point or whatever.

 

[HCHTech]

Residential users don't seem to understand they should use a different password.

So many folks don't even understand that it is a different ACCOUNT.

 

[SlickMinnow]

And all this crap from Microsoft benefits the typical home or soho user how exactly?...

 

[Sky-Knight]

And all this crap from Microsoft benefits the typical home or soho user how exactly?...

The same way Android and Apple accounts do, easy access to the ecosystem to get at stuff.

Automatic software updates for 3rd party apps is not a luxury anymore, it's of critical importance.

 

[YeOldeStonecat]

I don't work with residential users thus not with Windows "Home" edition much at all.
But...what's the issue, if end users sign in with a Microsoft account?

My laptop is joined to our AzureAD, I sign in with my Microsoft 365 account.
I've been converting clients to this also, as I have them shed their old on prem servers....we're unbuckling Windows Pro computers for them and signing end users in with their Microsoft accounts.

I've yet to see an undesirable result from doing that.
I still put a local Admin account on the machine.

 

[Sky-Knight]

@YeOldeStonecat It arms the device encryption bomb, and people forget their accounts. So when the device has an issue and you need that recovery key, it's nowhere to be found!

On the business side we just look it up.

Also, you cannot really "setup" a machine without it, so if you're trying to get a rig going for someone else, how do you do that?

 

[britechguy]

There are many advantages to the use of a Microsoft account. But the biggest one for home users is the ability to reset their Windows password via the "Forgot Password?" process . That alone has saved many a client's bacon.

 

[YeOldeStonecat]

@YeOldeStonecat It arms the device encryption bomb, and people forget their accounts. So when the device has an issue and you need that recovery key, it's nowhere to be found!

On the business side we just look it up.

Also, you cannot really "setup" a machine without it, so if you're trying to get a rig going for someone else, how do you do that?

OK, I see...for "one-off, non managed" home users...sure, I can see how they "don't know" the password to their MS account, thus...yeah, the recovery key be MIA for good.

Not sure what you mean "can't setup a machine without it". We setup computers for clients all the time, in our office, or onsite. Of course I still create a local admin account for us, document that HUDU, our documentation system, and from there, I join the clients AzureAD, and..just like if you join a workstation to a local active directory, anyone who is a member of that directory can then log onto the computer. So I set that up for the end user. If they have MFA on their account and are not standing nearby, can have them ready to approve via a phone call, or....if not avail, can temp disable MFA on their acccount (just gotta re-enable when done), or...they might be one of the tenants that we've added our WAN IP to their conditional access "trusted zones". (we're doing that more and more).

 

[timeshifter]

The biggest problem as an IT service provider is the headache of setting up and / or getting the account information. Most users won't know about the account, a lot will already have one and not know it, and you'll be spending a ton of time getting credentials. If they happen to be right there with you during setup and they're somewhat tech proficient not a big deal. But if you're setting one up in your shop and the client is hard to reach, fughetaboutit.

 

[Sky-Knight]

OK, I see...for "one-off, non managed" home users...sure, I can see how they "don't know" the password to their MS account, thus...yeah, the recovery key be MIA for good.

Not sure what you mean "can't setup a machine without it". We setup computers for clients all the time, in our office, or onsite. Of course I still create a local admin account for us, document that HUDU, our documentation system, and from there, I join the clients AzureAD, and..just like if you join a workstation to a local active directory, anyone who is a member of that directory can then log onto the computer. So I set that up for the end user. If they have MFA on their account and are not standing nearby, can have them ready to approve via a phone call, or....if not avail, can temp disable MFA on their acccount (just gotta re-enable when done), or...they might be one of the tenants that we've added our WAN IP to their conditional access "trusted zones". (we're doing that more and more).

You can do that for Pro, but Home unless severed from the Internet will force you to use a Microsoft account for that first user.

The Windows 11 Home machine I had on my bench even so severed forced the issue, sat there screaming for Internet access until I put it online and bound it to an account.

But yeah, for those servicing the residential market, this is a HUGE time sink and process disruption. For those servicing businesses that don't have Premium or greater... it's still an issue. Though I'm working around that by maintaining a "personal" account for each client, bound to the local admin I make to keep tabs on those recovery keys.

 

[nlinecomputers]

But...what's the issue, if end users sign in with a Microsoft account?

Because it will also make you set up a PIN and then they forget about the M$ account altogether. With Bitlocker that can be a major pain should the system crash and you get the dreaded Bitlocker Recovery key prompt.

 

[britechguy]

Because it will also make you set up a PIN and then they forget about the M$ account altogether.

Which you can switch back to password. And I do, and for precisely the "you must remember you are using a Microsoft linked Windows account and its password" reasons. Or at least for those clients I know will forget about the Microsoft account. There are some I know who will not, and if they prefer to use a PIN instead, they do.

 

[GTP]

Tried all the methods listed above. There is no other option than to join a network to continue.
There is no way to disable wifi (unless I physically open the laptop and remove the wifi chip?).
There is no "back" button or anyway to get out of the "Lets connect you to a network" page.
So, the only way to do an install of Windows 11 is to install Windows 10 and do an in place upgrade.

F*%k Microsoft

 

[timeshifter]

There is no "back" button or anyway to get out of the "Lets connect you to a network" page.

When I did it, I joined my local WiFi. Then when it tried to make me create or use an account I disabled the WiFi on the laptop. THEN, I hit back.

 

[britechguy]

Microsoft allows the use of non-numeric characters in the account's PIN, so if you're setting up an account for the first time there's nothing stopping you from setting its PIN and password to the same string. It doesn't stop the user from being confused but it makes a lot of problems go away.

True, but I dislike that idea because it muddies the actual concepts of what a PIN is supposed to be as opposed to what a password is supposed to be.

PIN = Personal Identification Number. When they started allowing what amount to passwords as PINs all I could do is scream then scratch my head.

Not that I wouldn't resort to your suggestion if push came to shove, but I'd rather avoid doing that if at all possible.