I guess you clicked your answer to the wrong name.
You guessed wrong, you didn't get my point.
I didn't reply to him but he replied to me criticizing your answer and then you mentioned other websites.
Get it?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Ok, now on Insider builds you can't get it past anymore by killing OOBE Connection Flow. This is just nonsense.
How are we supposed to set up PCs that don't have any Wi-Fi/Ethernet drivers in the first place?
When killing Connection Flow you just get this message:
Here is the solution:
Open cmd with Shift + F10 and type OOBE\BYPASSNRO.
Your computer will restart and now you will have the "I don't have Internet" option.
No need to thank me.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
I guess you clicked your answer to the wrong name.
You guessed wrong, you didn't get my point.
I didn't reply to him but he replied to me criticizing your answer and then you mentioned other websites.
Get it?
I know, I had already tried that, if you check back on the thread in page 6, back in January.
No difference now, the install media is still the same. 😉😎🤷♂️
I know but my reply to you was to address this from theking2
I guess you clicked your answer to the wrong name. 😎😎
theking2 is not even answering simple questions.
I'm done wasting time with this. 🤣🤣🤐🤷♂️
Anyway, the same command oobe\bypassnro works on both Home and Professional editions.
Clearly, he is not following the correct procedure. 🤐
This is the message that shows up if the command is entered before the new system is actually loaded on the disk and booted from:
X:\sources>oobe\bypassnro
The system cannot find the path specified.
X:\sources>
🤣😉🤐
Anyway, the MCT media for windows 11 22H2 is still the same 22621.525, and following the procedure correctly as described in many web sites works fine with that Build. 🤷♂️
Never mind other websites, it works as advertised here in the original post. 😉
I ran the test and the command works with current Windows 11 MCT.
I know, I had already tried that, if you check back on the thread in page 6, back in January.
No difference now, the install media is still the same. 😉😎🤷♂️
Anyway, the MCT media for windows 11 22H2 is still the same 22621.525, and following the procedure correctly as described in many web sites works fine with that Build. 🤷♂️
Never mind other websites, it works as advertised here in the original post. 😉
I ran the test and the command works with current Windows 11 MCT.