Another method for avoiding using a Microsoft account during setup

I really hope that Microsoft makes it as impossible to use Windows without a Microsoft Account as Apple and Google have made it to use their ecosystems effectively without these respective accounts.

But Apple and Google actually allow the OS to be initialised without those online accounts. Sure users might need an account to use the devices they way they want, but a tech can initialise the OS without online account if the end user isn't present or doesn't know their password.

Nobody here is complaining about the use of MS accounts generally, but about the inability to initialise the OS for a customer without requiring their online account info.
 
So...
I tried to install Windows 11 on an old Lenovo laptop model no. 310-i5isk
Cloned the the old drive to a new Crucial BX500 SSD.
I wanted to avoid the MS account bs so I thought I'd try updating from the .iso within Windows 10.

I got the "This processor is not supported" message so thought I'd try the other methods anyway.

Of course trying to disable the wifi by hitting the airplane mode key on the keyboard did nothing (do they disable key inputs during install?)
So I went to the BIOS and disabled wifi there.
There is no option to disable the network stack but thought I'd try the install again.
No go. It wants to connect to a network and the ethernet was the only one listed.
So I reenabled wifi in the BIOS and thought I'd try again to see what happens.

I proceeded to connect to wifi and continued just to see what I got. So far no prompt for a MS account.
When I did get asked for an email and password I just entered a gibberish bogus gmail address and PW which it accepted without issue.

The install completed! I thought the processor was not supported??

Anyway, I then went to accounts and signed in with a local account. So far its running perfectly. I ran Blackbird and a couple of other tools to remove the preloaded MS BS.

Installed the clients preferred software and she's as happy as a pig in sh*t.
 
Of course trying to disable the wifi by hitting the airplane mode key on the keyboard did nothing (do they disable key inputs during install?)
Most or all laptops need hotkey software installed for that to work, so this technique would only work in the OOBE for a factory image with drivers etc preinstalled.
No go. It wants to connect to a network and the ethernet was the only one listed.
The method that works every time (and it's pretty easy) is to hit SF10 when it asks for a network connection, at command prompt run taskmgr, and end the task Network Connection Flow. Mentioned earlier in this thread.
entered a gibberish bogus gmail address
Wow, didn't expect that to work!
I thought the processor was not supported??
Clean install only requires TPM 1.2 and a CPU of 1GHz. This is from a Microsoft help article:
You should verify that your device meets minimum system requirements before you choose to boot from media, because it will allow you to install Windows 11 if you have at least TPM 1.2 (instead of the minimum system requirement of TPM 2.0), and it will not verify that your processor is on the approved CPU list based on family and model of processor.

I suspect this was the original minimum spec before they decided to make it more strict. The fact that they haven't added the extra checks for clean installs suggests to me that the strict requirements are designed for ordinary end users (who are only capable of in-place upgrades). Making more ordinary home computers obsolete increases Windows license fees and pleases their hardware partners, while Corporate IT departments, techs and enthusiasts won't be too upset because they can clean-install. They're trying to have it both ways.

Closer to Windows 10 end-of-life I might consider doing these installs for customers. I'll see how it pans out in the meantime.
 
I used "somerandomperson@gmail.com" with random numbers/letters for a password (I didnt record them).
Worked without issue.

Except that there is now likely a phantom MS account, unreachable, associated with the computer.

As has been documented here, there are "clean" ways to set up with a local account if you feel you absolutely, positively must do so.
 
Except that there is now likely a phantom MS account, unreachable, associated with the computer.

As has been documented here, there are "clean" ways to set up with a local account if you feel you absolutely, positively must do so.
This. If M$ is going to force you to make an account, then make the damn account, print up a form with the account information and tell them to keep it safe. Creating a fake M$ account just BitLocker’d the machine to a lost account.
 
If M$ is going to force you to make an account, then make the damn account, print up a form with the account information and tell them to keep it safe.

Even if they weren't forcing the issue, I don't know how anyone here could not but view this course of action as firmly within "best practices."

I refuse to create local accounts anymore, because having a Microsoft Account (and with MS Hello Only login OFF) has saved several of my client's bacon because they forget or mislay things.

I am so over the "Microsoft's spying" BS and the insistance on a local account. If you want one after I set up the machine with a Microsoft Account using an email address that you, the client, actually know and use, then I might consent to add one, but I'd still try to dissuade the client. In these days of both Windows As A Service and cloud computing in general, local accounts make very little sense in the big picture.
 
If M$ is going to force you to make an account, then make the damn account, print up a form with the account information and tell them to keep it safe.
They don't force you to "make" an account, they try and force you to use an account and make one if you don't have one. I don't think it's a great idea to just make a new MS account when you setup Windows for a customer. You should be getting the account details from the customer, which is time-consuming and annoying when they can't tell you their password or even the account name.

Many of my customers don't use any Microsoft services that require an account (e.g. 365, OneDrive) so my general rule is to set it up as a local account without password. That way I can do all the updates, drivers, browser install etc. I work on several computers at once in my workshop on my own, and my rates are fairly low (AU$80ph) to suit my regional area of mostly retirees. So for me it's more practical to setup local account most of the time.

If they want a password or 365 setup I help them with that on pickup. I do not burden my customers with an unnecessary additional account if they don't need one. It's hard enough getting their email password.

Many, perhaps most, of my customers end up with a Microsoft account login anyway. But it was their choice to do so, or more often Microsoft's pressure to do so (e.g. Microsoft's intentionally vague prompt to allow 'signing into apps automatically')

Their are pros and cons for both login methods, to me they have similar merits. Some of my customers really want to stay on a local account, others don't care wither way. My customers that make a conscious decision to use MS account login are few and far between.

I give my customers what they want.
 
If they want a password or 365 setup I help them with that on pickup. I do not burden my customers with an unnecessary additional account if they don't need one. It's hard enough getting their email password.
This ^^.
Except that there is now likely a phantom MS account, unreachable, associated with the computer.
And neither I nor the client (an older lady who plays solitaire and sends the occasional email) gives a toss for a MS account.
She has 20 pictures and 5 recipes on the hard drive.
Bitlocker is off so that's not an issue either.
It's easy to get carried away with all the gee-wizery sometimes...
 
Have been getting my first round of new Win11 PCs lately. Luckily I've been able to get to a few before the client has started setting it up. I've just been using fake M$ creds to force a local account when possible. Unfortunately I've had a few clients go a head and use their business accounts and I've had to reverse a lot of that.
 
Very handy to know this, my mother in law is not tech savvy at all and has been struggling with her Microsoft account... almost time for a reload on her computer, ill avoid the Microsoft account this time.
 
I thought I'd posted this method too, maybe I did somewhere else...


This works well, just did it today. Basically interrupt when it asks to connect to network by using Shift + F10 then run taskmgr from the prompt then kill Network Connection Flow.
 
Why MS pressures users into an Online account baffles and annoys me. It is like this is the car, these are your keys you own them. Though yeaa...we need you to be online before we can start your own car, that you purchased from us.

INTERNET.jpg
 
Back
Top