About new install, account requirements, internet requirement

punkncat

Polypheme
Ambassador
In the beginning of W11 you could choose to install the 'Pro' version and it allowed you to install with the "I don't have internet" and also not make you create or sign in to a MS account to finish. This is no longer the case, not sure how long...so, anyway...

I just completed the aspects of a build I have on hand and wanted to check everything out before time was short on returns, if needed. Glad to say that the system booted up just fine, but not so pleased that in spite of selecting the Pro version, the install required me to connect to the internet and also required me to sign on with a Microsoft account in order to move forward.

In the interest of time savings, I signed in with my own account. The new owner doesn't know they are going to be a new owner, so I couldn't spoil it with asking them for credentials. Doing so instantly synced ALL of my bookmarks, favorites, preferences and so forth. Didn't give me the opportunity to turn sync off. I spent the last hour or so going through and returning to "local account" and undoing all the items listed above, plus some.

Is anyone aware of a more streamlined way to do this as a builder? Should I perhaps consider making a shell account that is used for such and has no preferences outside of the default format?

I would be interested in hearing your take on it. I really don't enjoy the extra hour(s) of sitting here fixing things that should not be forced upon the installer.
 
Install with no ethernet cable or WiFi....no internet at all.
When it gets to the part about asking for accounts, stop.

When the new owner powers up, it should then complete the process, asking HIM for all that info.
 

Have you waded through the above, written in April?

Sooner or later, I will be faced with your situation, so I've tried to stay on top of it. I'm still on Win 10 now.

Information re Win 11 seems to be constantly changing. I've saved a lot of info on the topic I've found on the web, but most of it is from 2022.
 
  • Like
Reactions: punkncat
Install with no ethernet cable or WiFi....no internet at all.
When it gets to the part about asking for accounts, stop.

When the new owner powers up, it should then complete the process, asking HIM for all that info.


The issue here is that now, you can't just stop. It gives you no other option than to either connect internet, or it basically quits the install process which is counterproductive to what I am trying to do as a system builder.
 

Have you waded through the above, written in April?

Sooner or later, I will be faced with your situation, so I've tried to stay on top of it. I'm still on Win 10 now.

Information re Win 11 seems to be constantly changing. I've saved a lot of info on the topic I've found on the web, but most of it is from 2022.


Hmm, interesting. I will have to try this on my next install. I can tell you for sure that there is no option for bypassing this within the install console.
 
If you check the link that @Lafong posted, pretty much just after you confirm your region and keyboard settings. At one point there was a bypass by using the accessibility settings, but that did not produce a back door either.
Thats what I thought.

So, just before that, stop.
Power off
Give it to the new owner

Let HIM go through the final setup and "Hi".

The OS is all done, except for the final config.
It no longer needs the install USB.
 
  • Like
Reactions: punkncat
Thats what I thought.

So, just before that, stop.
Power off
Give it to the new owner

Let HIM go through the final setup and "Hi".

The OS is all done, except for the final config.
It no longer needs the install USB.


I follow what you are saying, but it also leaves a lot of questions insofar as system stability and such.

I think what I may do as a middle ground option is to complete all my own testing and such and then do a 'reset' so that they see that startup screen. Not optimal IMO, but workable.
 
I follow what you are saying, but it also leaves a lot of questions insofar as system stability and such.

I think what I may do as a middle ground option is to complete all my own testing and such and then do a 'reset' so that they see that startup screen. Not optimal IMO, but workable.
Right.

If you're also including new build system stability, then you DO want to go through the whole install and test the system.

Possibly then, you do a full wipe and a final install for the end user.
I've never really liked the 'reset' thing.
 

Latest posts