Windows Autopilot Troubleshooting Guide

1. Capturing and Registering Hardware Hashes

The foundational requirement for any Autopatch or Autopilot deployment is an accurate hardware hash. When registration fails or devices fall back to standard OOBE login screens, examine the hash export script output.

2. Resolving Enrollment Status Page (ESP) Timeouts

ESP tracking freezes are frequently caused by large Win32 application payloads or hidden dependency loops during the device preparation phase. Always isolate tracking to critical applications rather than forcing all user-assigned software blocks.

• Log Collection: Press Ctrl + Shift + D during ESP execution to gather diagnostic logs.
• Timeout Thresholds: Extend default ESP thresholds if deploying monolithic packages like Office LTSC or full Adobe Creative Suites.
• Strict App Targeting: Limit blocking apps in ESP profiles strictly to security agents (e.g., EDR/MDE) and core identity clients.

3. Common Error Codes & Immediate Fixes

Keep track of standard hex error codes returned during provisioning failures to streamline remediation workflows:

4. Diagnostic Log Extraction & Analysis

When automated triage fails, pull full diagnostics using the built-in diagnostic tool package. Extract logs via command line to a connected USB flash drive or inspect files locally under C:\ProgramData\Microsoft\IntuneManagementExtension\Logs.