This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
@Johnny_55, @Sibro.o,
Assuming there is code for Autopilot in the 25193 builds, the message we get could be a known issue that will be solved on a later build. 😎
We'll see what happens next time around, or the next official MS ISO.
Windows Autopilot resolved issues | Microsoft Docs
* Windows Autopilot reports an AUTOPILOTUPDATE error during OOBE after sysprep, reset, or other variations. This issue typically happens if you reset the OS or used a custom sysprepped image.
Hi Sibro, fg
Appears MS shut this one down. I confirm the same but still got it installed offline local in total clean install in VMware. Have not attempted on a laptop.
When I got the screen you display with autopilot, I briefly connected internet. It opened up screen to name this device. I then disconnected again, it requested the User name and proceeded to finalize install offline. Something along that line.
I tried the long way around by creating a user account using OOBE, it also worked but with some flaws. Have not had time to play with it any further. That was the original example that was given.
Regards,
Hi Johnny,
I confirm that I could also disconnect the network after getting over the "AUTOPILOTUPDATE" message, then the install could proceed with an offline local account.
Still, I needed to connect temporarily to bypass that point. 🤷♂️
As for avoiding using the MSA and using a local account while connected to the network, the method suggested in the link below still works, at least for now. 🤣🤣
Bypass Microsoft Account requirement when setting up Windows 11 with internet - Neowin
Hi Sibro, fg
Appears MS shut this one down. I confirm the same but still got it installed offline local in total clean install in VMware. Have not attempted on a laptop.
When I got the screen you display with autopilot, I briefly connected internet. It opened up screen to name this device. I then disconnected again, it requested the User name and proceeded to finalize install offline. Something along that line.
I tried the long way around by creating a user account using OOBE, it also worked but with some flaws. Have not had time to play with it any further. That was the original example that was given.
Regards,
I'm not sure when this took effect but oobe\bypassnro doesn't work anymore (build 25193)
Instead of the regular options, right away the installer tries to check for updates and this comes up
I could not find a way out. I tried oobe\bypassnro one more time , same result.
Also, I couldn't perform an in-place repair on this clean installation without using a hack. AFAICR, this is the first time this happened to me with a Dev build on this yellow zone laptop.
Hi Sibro,
Confirm, I see the same message with 25193.
I had to connect the ethernet and then hit "Try again" to get over that message "AUTOPILOTUPDATE" and then it continued.
Note that at this point it did not give me the choice for connecting the Wi-Fi either, I just connected the ethernet and hit Try Again. 🤷♂️
It let me connect with Wi-Fi when I did a normal install without using oobe\bypassnro. 🤷♂️
Always some new changes. 🤣
I never heard anything about AUTOPILOTUPDATE. 😎
What's new in Autopilot | Microsoft Docs
As for update in place, in my case, there is no change because I already needed a little hack on appraiserres.dll to get over the TPM and Secure Boot checks. 🤣
I did the upgrade of my red zone laptop from 19044.1949 to 25193.1000 without any new problem. 😉
I'm not sure when this took effect but oobe\bypassnro doesn't work anymore (build 25193)
Instead of the regular options, right away the installer tries to check for updates and this comes up
I could not find a way out. I tried oobe\bypassnro one more time , same result.
Also, I couldn't perform an in-place repair on this clean installation without using a hack. AFAICR, this is the first time this happened to me with a Dev build on this yellow zone laptop.