OOBE not welcoming

Helmut said:

You have to switch off/disable your Wireless Access Point, no Ethernet cable either, when setting up a new Laptop. Then it will have no internet access and gives you the option of continuing with a Local Account.

Of course then there will be no updates, and you just go thru the OOBE.

Later on you can easily change to using a Microsoft Account if you wish.

In the Wireless Access Point of my Router you have to switch off both 2.4 GHz and 5 GHz radios.

Of course the sensible adult way is to give the user options so you can choose, rather than all this palaver.
View attachment 122522

Click to expand...

This no longer works with 24H2. The installer just loops around back to asking for internet.

You have to use a different method like oobe\bypassnro.

Again using a RUFUS modified installer bypasses all this mess. Clean install or In-Place upgrade. I know I said Clean Install earlier but it works for both methods. Local account and all.

BamaInArk said:

Again using a RUFUS modified installer bypasses all this mess. Clean install or In-Place upgrade. I know I said Clean Install earlier but it works for both methods. Local account and all.

Click to expand...

I 100% agree. I don't know why people want to sit there and mess around when you can just RUFUS the whole process and go make a cup of tea while Windows installs.
People have their proffered processes, I can appreciate that.

Once I’d reset it and done oobe in command prompt the second time, it was all very quick and easy - I just hadn’t done it for a long time and forgot I shouldn’t connect to the internet.

Now I’ve done a system image of it as it arrived ,, I’ve clean installed 23H2 without Rufus and that was quick and easy too - once I knew to do the oob thing before connecting to the internet!

Incidentally all those updates it was doing earlier, I suspect it was updating to 24H2 - I thought it funny the touchpad wasn’t workong as the person who sold me the laptop seemed reliable. Now it’s back on 23H2 - the touchpad is working. So that has definitely decided me not to upgrade to 24H2. Although I might try it again after this clean install to see if it was that or some other software glitch in the set up as it came to me.

Hazel123 said:

Incidentally all those updates it was doing earlier, I suspect it was updating to 24H2

Click to expand...

The new normal for a Windows install with 24H2 is that you can start with whatever build of Windows ISO you want, but if you’re connected to the internet, Windows looks for any new updates, so you could very likely end up with a different build once the install is finished, than what you started with.

Hazel123 said:

I suspect it was updating to 24H2

Click to expand...

OH… the install ISO was 23H2? interesting. perhaps it’s just the new norm, period.