Autopilot issue on device set up "Identifying"

Question

Hello everyone, I'm currently using autopilot to enroll devices into Intune. Up until now, everything has been going smoothly without any changes. However, the last three devices, which are the same models as the ones that previously worked, are encountering an issue during the device setup stage. Specifically, they are getting stuck during the identification process when applying the security policy.

Current set up is:

Any ideas where I am going wrong

Answer 1

@Aran Billen, Thanks for posting in Q&A. From the information you provided, it seems the devices are stuck or having issue when apply security policy. To check this, you can collect Windows Autopilot MDM logs and analyze DeviceManagement-Enterprise-Diagnostic-Provider Event log to see if any related error can be found.

https://learn.microsoft.com/en-us/troubleshoot/mem/intune/device-enrollment/understand-troubleshoot-esp

For such log analysis issue, you can open case to troubleshoot the issue.

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

Hope the above information can help.

---

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.

Answer 2

Yesterday there was complains in Facebook Intune group that Autopilot was stuck. Maybe this was general public problem you had. How about today?

Answer 3

We're you able to locate the issue. Im having the same issue out of nowhere it seems.

Answer 4

I found today the solution and maybe it's still helpful for you:

• Through more or less luck I found out that Intune is stuck on 2FA for the user to whom the device is enrolled to: It's like a not seeable or recognizable 2FA request - neither the user nor someone else can see it
• Press Alt + Ctrl + Entf and log the user out
• Log the user in again
• Suddenly there is PopUp to sign in the user - sign the user in
• You get 2FA request defined for the user - provide it
• Then the device continues and is finished in 5 minutes

Definitely a Microsoft problem

Answer 5

Executive summary

Devices on Windows 11 24H2 failing/partially enrolling to Intune during OOBE were traced to KB5050575 (OOBE/dynamic update). Removing the package before first M365 sign-in restores normal enrolment, policy application, check-ins and M365 access (MFA unaffected).

Proven workaround (OOBE)

1. Shift+F10 at OOBE to open an elevated Command Prompt.
2. Confirm the package::

dism /online /get-packages | findstr /i 5050575

1. Remove using the exact package identity returned (revision may vary):

dism /online /remove-package /packagename:Package_for_KB5050575~31bf3856ad364e35~amd64~~26100.1588.1.0 /quiet /norestart

1. Proceed with M365 sign-in and Intune enrolment. Policies (compliance + configuration) apply as normal and device check-ins succeed.