Fix Windows Autopilot Device Preparation Error 0x80180014

Dealing with Windows Autopilot device preparation errors can be frustrating, especially when encountering specific issues like error 0x80180014 related to corporate identifiers, MDM restrictions, and device reuse checks. This guide provides a clear, step-by-step approach to diagnose and resolve this problem, ensuring your devices are correctly prepared for deployment without unnecessary delays. Before starting, ensure you have administrative access to your Azure AD and Microsoft Endpoint Manager (Intune) portals, as well as the necessary device details and credentials. Having a stable internet connection and access to the device in question is also essential.

What You’ll Need

• Administrator access to Microsoft Endpoint Manager (Intune)
• Azure Active Directory administrator privileges
• Device serial number or hardware ID
• Access to device’s UEFI/BIOS settings (if needed)
• Reliable internet connection
• Basic understanding of Autopilot and MDM policies

Step-by-Step

1. Verify Device Reuse Status:
   Start by confirming whether the device has been previously used or registered in Autopilot. Log into the Microsoft Endpoint Manager admin center, navigate to Devices > Windows > Autopilot devices, and search for the device serial number or hardware ID. If the device appears as already registered or marked as reused, note this, as it can cause preparation errors.
2. Remove Existing Autopilot Registration:
   If the device is listed as previously registered or reused, delete its record from Autopilot. Select the device and click Delete. This step ensures the device is cleared of any prior Autopilot configurations, reducing conflicts during re-provisioning.
3. Reset the Device to Factory Settings:
   Perform a full reset to wipe any residual configurations. Turn off the device, then boot into the BIOS/UEFI settings (usually by pressing F2, F12, DEL, or ESC during startup). Ensure Secure Boot is enabled and that the device is set to boot from USB or network if needed. Use a Windows reset option or boot into the Windows recovery environment and choose Reset this PC with Remove everything. This clears previous profiles and prepares the device for fresh enrollment.
4. Register the Device with Autopilot Anew:
   Collect the device’s hardware ID again if it has changed after reset. Use the Get-WindowsAutopilotInfo PowerShell script or the OEM tools to generate a new hardware ID file. Upload this file to the Autopilot service in Microsoft Endpoint Manager by navigating to Devices > Windows > Autopilot devices > Import. This step ensures the device is correctly registered and recognized for deployment.
5. Check MDM and Enrollment Restrictions:
   In the Endpoint Manager portal, navigate to Devices > Enrollment restrictions. Verify that the policies allow device enrollment for the device’s hardware ID, and confirm there are no restrictions blocking the device due to device type, platform, or user group. Adjust policies if necessary to permit the device to enroll without restrictions.
6. Configure Corporate Identifier Settings:
   Ensure that the device’s registration includes correct corporate identifiers. Within Endpoint Manager, check Devices > Autopilot profiles. Confirm the assigned profile matches your organization’s deployment policies, including any restrictions on device reuse or registration. Adjust the profile to remove restrictions related to reuse or corporate identifiers if they conflict with your deployment goals.
7. Reattempt Autopilot Device Preparation:
   Power on the device and initiate the Windows Autopilot provisioning process. Connect to the internet and follow the on-screen prompts. Monitor the process for errors. If the error 0x80180014 persists, verify the device’s registration status in Endpoint Manager and ensure the correct Autopilot profile is assigned.
8. Review and Adjust Policies as Needed:
   If the error continues, revisit your MDM and Autopilot profile settings. Ensure no policies are overly restrictive, such as requiring specific hardware identifiers or corporate credentials that do not match the device. Consider creating a test profile with minimal restrictions to isolate the issue.

Common Mistakes

• Not removing previous Autopilot registration before reusing a device
• Using outdated or incorrect hardware IDs during registration
• Failing to reset the device to factory settings prior to re-enrollment
• Misconfiguring enrollment restrictions or Autopilot profiles
• Attempting to enroll a device with incompatible or restricted hardware
• Ignoring device compliance or restriction policies in Endpoint Manager

Tips

• Always perform a full factory reset before reusing a device for Autopilot deployment
• Use PowerShell scripts like Get-WindowsAutopilotInfo to accurately collect hardware IDs
• Regularly review and update enrollment restrictions to match your device fleet
• Keep your Autopilot profiles aligned with organizational policies to avoid conflicts
• Document device registration steps to troubleshoot issues efficiently in future deployments
• Test new profiles on a single device before mass deployment to catch potential issues early

Troubleshooting

If you encounter persistent errors during device preparation, follow these troubleshooting steps:

1. Check Device Registration Status: Log into Endpoint Manager and verify whether the device is registered, pending registration, or marked as reused. Clear any existing registration if necessary.
2. Review Error Details: Note the exact error code and message. Search the Microsoft documentation or community forums for specific insights related to error 0x80180014.
3. Validate Policies and Restrictions: Ensure your enrollment restrictions and Autopilot profiles do not conflict with the device’s hardware or intended use. Adjust settings accordingly.
4. Perform a Deep Reset: If issues persist, consider performing a more thorough reset, such as a clean installation of Windows using media creation tools, then re-register the device.
5. Update Device Firmware and BIOS: Outdated firmware can cause registration issues. Update BIOS/UEFI to the latest version recommended by the device manufacturer.
6. Contact Microsoft Support: If all else fails, gather logs and contact Microsoft support for advanced troubleshooting assistance.

Frequently Asked Questions

1. What does error 0x80180014 mean in Autopilot?

This error indicates a problem with device registration, often related to corporate identifier restrictions or device reuse conflicts, preventing successful Autopilot provisioning.

2. Can I reuse a device that has previously been registered in Autopilot?

Yes, but you must remove its previous registration and reset it to factory settings before re-enrolling to avoid conflicts and errors.

3. How do I verify if a device is registered in Autopilot?

Login to Microsoft Endpoint Manager, navigate to Autopilot devices, and search using the device’s serial number or hardware ID to check its registration status.

4. Why does my device keep failing during Autopilot provisioning?

Common reasons include registration conflicts, incorrect or restrictive profiles, device hardware incompatibilities, or incomplete resets. Troubleshooting these areas often resolves the issue.

5. How can I prevent this error in future deployments?

Ensure proper device registration, perform factory resets before reuse, keep profiles updated, and regularly review enrollment restrictions to align with your device fleet.

Related

• How to Fix Your Wireless Mouse Not Working on Windows 11
• How to Fix Your Windows 10 Touchscreen Not Working
• How to Fix Your Windows 11 End of Service Warning