Autopilot Pre-Provisioning Fails with Error 0x80180005

Question

We are currently facing the following Problem:

While in the Pre-Provisioning Process (White Gloves) we are getting stuck at "Registering your Device for Mobile Management". After 15 Minutes we we get an Error: "We Couldn't finish MDM Enrollment. Error: 0x80180005" The intended Deployment Profile does show up though.

We already collected the Logs and found the following Errors in microsoft-windows-devicemanagement-enterprise-diagnostics-provider-admin:

"MDM Enroll: Server Returned Fault/Code/Subcode/Value=(EnrollmentServer) Fault/Reason/Text=(ZTD Profile was not assigned to ZTD Device)." - Event 52

"MDM Enroll: Failed to receive or parse certificate enroll response." - Event 11

We tried different devies and also a fresh windows Installation...always with the same result.

It Worked before, nothing has changed as far as i know.

One thing I was wondering about was, that we did not have a language select at the beginning of the OOBE, like we normally do.

I would appreciate any suggestion.

Answer 1

@Kurt Blum , Thanks for posting in Q&A. From your description, I know some devices are failed to do Autopilot enrollment with error "ZTD Profile was not assigned to ZTD Device". It seems the devices are failed to get profile.

Please try the following suggestion to see if it can work:

1, Delete all objects including the original Autopilot objects from Intune, AAD and local AD (If it is Hybrid Entra joined):

•Delete from: Intune portal>Device>all devices

•Delete from: Intune portal>Device>Windows>Windows enrollment> Windows Autopilot Deployment Program

•Delete from: Azure portal>Device

•Delete from local AD

2, Re-import device csv file and assign Autopilot profile and Domain Join profile (If it is Hybrid Entra joined).

3, Wait for the profile to be assigned Make sure the profile is assigned in Intune portal

4, Reset the device(make sure chose “Remove everything”) and then do pre-provisioning again to see if it can work.

Please tr the above suggestion and if there's any update, feel free to let us know.

---

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

Make sure that the device is really assigned to Autopilot profile with device hash that matches. Also for pre-provisioning, I think keyboard or regional selection is mandatory, otherwise you will miss the right spot during OOBE to hit 5 x WIN key. So you can't really use automated keyboard selection in Autopilot profile if you are about to utilize Pre-provisoning.