Troubleshooting Autopilot Devices Stuck in OOBE Reboot Loop: Reasons and Solutions
- Tek Doyen
- Dec 26, 2025
- 2 min read
Autopilot devices can get stuck in an OOBE reboot loop due to profile misconfiguration, Intune policy conflicts, Hybrid Azure AD join issues, TPM attestation failures, or network connectivity problems. Troubleshooting involves verifying profile assignment, checking Azure AD/Intune sync, reviewing event logs (like Event ID 2800), resetting and re-enrolling the device, testing with a clean network, and updating drivers/firmware.
🚨 Common Reasons for OOBE Reboot Loop
Enrollment profile issues: Corrupt or missing Autopilot profile prevents proper setup.
Hybrid Azure AD Join misconfiguration: Device cannot complete domain join, triggering repeated reboots.
Intune policy conflicts: ESP (Enrollment Status Page) policies force reboots when SYSTEM cannot apply settings.
Network connectivity problems: Device fails to reach Microsoft services during OOBE.
TPM attestation failure: Secure provisioning blocked due to hardware/firmware mismatch.
Driver or firmware bugs: Outdated BIOS or drivers cause instability during provisioning.
🛠️ Troubleshooting Steps
Verify Autopilot profile assignment: Ensure correct profile is applied in Intune.
Check Azure AD/Intune sync: Confirm device object exists and sync is healthy.
Review event logs: Look for Event ID 2800 in DeviceManagement-Enterprise-Diagnostics-Provider.
Reset device and re-enroll: Use systemreset -factoryreset or wipe from Intune.
Test with clean network: Remove proxies, VPNs, or restrictive firewalls.
Update drivers/firmware: Apply latest OEM BIOS and drivers before redeployment.
📊 Comparison Table
Cause | Symptom | Fix |
Profile issues | Device loops before account setup | Reassign profile in Intune |
Hybrid Join misconfig | Stuck at domain join step | Validate AD Connect & GPOs |
Policy conflicts | ESP never completes | Adjust ESP timeout & assignments |
Network problems | Device cannot reach cloud | Test on open Wi-Fi |
TPM failure | Attestation error in logs | Update firmware, clear TPM |
Driver bugs | Random reboot during OOBE | Update BIOS & drivers |
Comments