How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

Question

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

John Hallberg 0

Hi,

We have starting to use Autopilot to deploy our windows computer. User-driven is no problem but when we uses Self-deploying the computer sometimes stops in OOBE with the message "Let´s connect you to a network". I noticed that it take a few seconds before Network show up as Connected and it´s causes the deployment to halt. If you click next all works fine but I want "zero touch". We have over 1000 lab computers deployed by using self deployment and we can´t get out to each on of them to click next. It´s have to be automatic. Is there anything I can do to solve this issue? We traditionally used Configuration Manager and Task Sequence and it worked with "zero touch". I think Autopilot also must work with "Zero Touch".

Can you please help with this issue?

All Best

John Hallberg

Jönköping University

2 answers

Your answer

Answer 1

ZhoumingDuan-MSFT 17,260 Microsoft External Staff

@John Hallberg, Thanks for posting in Q&A.

From your description, I know you want to avoid "Let´s connect you to a network" when using Autopilot Self-deployment.

Based as I know, for user-driven and self-deploying model, Autopilot profile can only be downloaded, and the registration process can be completed after the device is connected to the Internet. In your situation, it may be because you are using Wi-Fi, which requires the user to manually choose to connect to the wireless network. It is recommended that you consider using an Ethernet network to solve this problem.

If you cannot ensure that each device can use an Ethernet network, you can consider creating a Wi-Fi configuration profile to ensure that each device automatically connects to Wi-Fi, so that the user does not need to click to connect to the network.

https://www.prajwaldesai.com/create-a-wi-fi-profile-in-intune/

Non-official, just for reference.

Hope above information can help you.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

John Hallberg 0 Reputation points

2025-04-03T06:15:42.8433333+00:00

Thank you for your reply! The computers are connected to our physical network with a cable and they get connected after a few seconds. So my question is why is it halting the process just because it takes a few seconds to get connected?
ZhoumingDuan-MSFT 17,260 Reputation points Microsoft External Staff

2025-04-03T07:09:15.6566667+00:00

@John Hallberg, Thanks for your reply.

After my deep research, only after the device is connected to the network, the Autopilot profile will be downloaded and the Autopilot process will be carried out, so this page cannot be skipped.

Moreover, for Windows 10, this page can be skipped, but for Windows 11, this page cannot be skipped because the behavior of Windows 11.

Hope it can clarify your issue.
John Hallberg 0 Reputation points

2025-04-03T07:36:08.0166667+00:00

It clarify my issue a bit but the strange thing is that sometimes it works without any problems. For example, we bought a new machine and deployed it with autopilot self-deploy without problems. We then needed to replace the hard drive to a bigger one and restored the OS using F11 and using a cloud image from HP. Then Self-deployment started to go wrong. I think you must be able to replace the hard drive without loosing the function of Autopilot. Now Autopilot is less automatic than the old fashion Config Manager. It is getting harder for me to promote Autopilot in our organization now when the job requires manual intervention.
ZhoumingDuan-MSFT 17,260 Reputation points Microsoft External Staff

2025-04-03T07:44:04.4633333+00:00

@John Hallberg, Thanks for your reply.

According to your description, the issue looks like a little strange, due to the limitation of Q&A, it is suggested that you open an online case to get more help.

https://learn.microsoft.com/en-us/mem/get-support

Thanks for your understanding.

Answer 2

John Hallberg 0

Thank you! I open a case and hope to sort this out.

Loïck Dupont 0 Reputation points

2025-07-02T10:09:44.08+00:00

Hi John. Did you ever manage to solve this?
Jake Hartman 0 Reputation points

2025-07-23T20:43:43.76+00:00

@John Hallberg Did you ever get a response from Microsoft support on this? We have the same issue occuring sporadically on our lab systems we want to use zero-touch provisioning via Autopilot for. But it is currently failing on roughly a quarter of them.

Share via

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

2 answers

Your answer